-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Documentation and readme updates * forgot something...
- Loading branch information
Showing
8 changed files
with
210 additions
and
82 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,62 @@ | ||
.. _contributing: | ||
|
||
Contributing | ||
============ | ||
|
||
Thank you for wanting to contribute to this library! We will try to make this | ||
an easy process for you. If you are looking to contribute code, we recommended that you read | ||
the :ref:`development<development>` page. | ||
Checking that your PR passes the tests before submission will speed up | ||
the acceptance of your PR. | ||
|
||
Issues and bug reporting | ||
------------------------ | ||
|
||
To report issues or bugs please create a new issue on | ||
the `pyrocs issues page <https://github.com/sandialabs/pyrocs/issues>`_. | ||
Before submitting your bug report, please perform a cursory search | ||
to see if the problem has been already reported. If it has been reported, | ||
and the issue is still open, add a comment to the existing issue instead of opening a new issue. | ||
|
||
Guidelines for effective bug reporting | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
- Use a clear descriptive title for the issue. | ||
|
||
- Describe the steps to reproduce the problem, | ||
the behavior you observed after following the steps, and the expected behavior. | ||
|
||
- If possible, provide a simple example of the bug using pyrocs example data. | ||
|
||
- When relevant, provide information on your computing environment | ||
(operating system, python version, pyrocs version or commit). | ||
|
||
- For runtime errors, provide a function call stack. | ||
|
||
Contributing code | ||
----------------- | ||
|
||
Software developers, within the core development team and external collaborators, | ||
are expected to follow standard practices to document and test new code. | ||
Software developers interested in contributing to the project are encouraged | ||
to create a Fork of the project and submit a Pull Request (PR) using GitHub. | ||
Pull requests will be reviewed by the core development team. | ||
Create a PR or help with other PRs which are in the library | ||
by referencing `pyrocs PR page <https://github.com/sandialabs/pyrocs/pulls>`_. | ||
|
||
Guidelines for preparing and submitting pull-requests | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
- Use a clear descriptive title for your pull-requests | ||
|
||
- Describe if your submission is a bugfix, documentation update, or a feature | ||
enhancement. Provide a concise description of your proposed changes. | ||
|
||
- Provide references to open issues, if applicable, to provide the necessary | ||
context to understand your pull request | ||
|
||
- Make sure that your pull-request merges cleanly with the `main` branch of | ||
pyrocs. When working on a feature, always create your feature branch off of | ||
the latest `main` commit | ||
|
||
- Ensure that appropriate documentation and tests accompany any added features. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
.. _development: | ||
|
||
Development | ||
===================== | ||
|
||
Installation | ||
------------ | ||
To maintain a local installation, developers should use the following commands:: | ||
git clone https://github.com/sandialabs/pyrocs.git | ||
cd pyrocs | ||
pip install -e . | ||
|
||
Testing | ||
------- | ||
To test locally, run:: | ||
|
||
pytest pyrocs | ||
|
||
at the root of the repository. Note that this requires the installation | ||
of pytest. | ||
|
||
Documentation | ||
------------------ | ||
|
||
Building docs | ||
^^^^^^^^^^^^^^^ | ||
To build docs locally, navigate to ``pyrocs/docs`` and run:: | ||
|
||
make html | ||
|
||
After building, the static html files can be found in ``_build/html``. | ||
|
||
Docstrings | ||
^^^^^^^^^^^ | ||
The pyrocs documentation adheres to the Google style for docstrings. Not only does this | ||
help to keep a consistent style, but it is also necessary for the API documentation | ||
to be parsed and displayed correctly. Examples can be found in the | ||
`sphinx documentation <https://www.sphinx-doc.org/en/master/usage/extensions/example_google.html>`_. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
.. _installation: | ||
|
||
Installation | ||
=============== | ||
|
||
We recommend using a virtual environment when installing pyrocs. | ||
`Conda<https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html>` is a popular option for | ||
virtual environment management. | ||
Regular tests are run for pyrocs on Python versions 3.9, 3.10, and 3.11 so we recommend installing | ||
the package alongside one of these Python versions, although pyrocs may work with other versions as well. | ||
|
||
The latest release of pyrocs is accessible via PYPI using the following | ||
command line prompt:: | ||
|
||
$ pip install pyrocs | ||
|
||
Alternatively, the package can be installed using github:: | ||
|
||
$ git clone https://github.com/sandialabs/pyrocs.git | ||
$ cd pyrocs | ||
$ pip install . | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,5 @@ | ||
.. _references: | ||
|
||
References | ||
========== | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters