forked from terrapower/armi
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'terrapower/main' into drewj-usnctech/gr…
…id-refactor-pre-1278 * terrapower/main: Move max assembly number out of global scope (terrapower#1383) Ensuring we throw an error on bad YAML files (terrapower#1358) Removing unused settings (terrapower#1393) Fixing some miscellaneous TODOs (terrapower#1392) Removing global plugin flags (terrapower#1388) Update reactivity coefficient parameters (terrapower#1355) Fixing ruff formatting of doc gallery examples (terrapower#1389) Fixing broken link (terrapower#1390) Removing unreachable code block (terrapower#1391) Removing unnecessary f-strings (terrapower#1387) Updating documentation dependencies for Python 3.11 (terrapower#1378) Adding a little code coverage to the CLIs (terrapower#1371) Remove coveragepy-lcov dependency during CI. (terrapower#1382) Reconnect logger after disconnecting in test. (terrapower#1381) Add Python 3.11 to GH Actions (terrapower#1341) Removing global variable from runLog.py (terrapower#1370) Moving the First-Time Contributors guide to the docs (terrapower#1368)
- Loading branch information
Showing
93 changed files
with
717 additions
and
516 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,19 +8,16 @@ on: | |
|
||
jobs: | ||
build: | ||
|
||
runs-on: ubuntu-22.04 | ||
|
||
env: | ||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
COVERALLS_REPO_TOKEN: ${{ secrets.COVERALLS_REPO_TOKEN }} | ||
|
||
steps: | ||
- uses: actions/checkout@v2 | ||
- name: Setup Python | ||
uses: actions/setup-python@v2 | ||
with: | ||
python-version: '3.10' | ||
python-version: '3.11' | ||
- name: Update package index | ||
run: sudo apt-get update | ||
- name: Install mpi libs | ||
|
@@ -31,17 +28,8 @@ jobs: | |
run: tox -e cov1 || true | ||
- name: Run Coverage Part 2 | ||
run: tox -e cov2 | ||
- name: Convert Coverage Results | ||
env: | ||
COVERALLS_REPO_TOKEN: ${{ secrets.COVERALLS_REPO_TOKEN }} | ||
run: | | ||
pip install click==8.1.3 | ||
pip install coverage==6.5.0 | ||
pip install coveragepy-lcov==0.1.2 | ||
coveragepy-lcov --data_file_path coverage_results.cov --output_file_path lcov.txt | ||
- name: Publish to coveralls.io | ||
uses: coverallsapp/[email protected] | ||
with: | ||
github-token: ${{ secrets.GITHUB_TOKEN }} | ||
path-to-lcov: lcov.txt | ||
|
||
path-to-lcov: coverage.lcov |
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
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 |
---|---|---|
@@ -1,77 +1,3 @@ | ||
# How to contribute | ||
# How to Contribute | ||
|
||
The ARMI framework project strongly encourages developers to help contribute to the codebase. | ||
|
||
The ARMI framework code is open source, and your contributions will become open source. | ||
Although fewer laws apply to open source materials because they are publicly-available, you still | ||
must comply with all applicable laws and regulations. | ||
|
||
## Help Wanted | ||
|
||
There are a lot of things we need help with right off the bat, to get your feet wet: | ||
|
||
* Many more type annotations are desired. Type issues cause lots of bugs. | ||
* Fewer Pylint warnings | ||
* Better documentation | ||
* Better test coverage | ||
* Targeted speedups (e.g. informed by a profiler) | ||
* Additional relevance to thermal reactors | ||
|
||
Naturally, we encourage other kinds of contributions as well. | ||
|
||
## Testing | ||
|
||
Any contribution must pass all included unit tests. The tests are built and run with the | ||
`pytest` system. Please add new tests if you add new functionality. You can generally just run | ||
`tox` to build the testing environment and execute all the tests and ruff checks. | ||
|
||
## Submitting changes | ||
|
||
Please send a [GitHub Pull Request to the ARMI main branch](https://github.com/terrapower/armi/pull/new/main) with a clear | ||
list of what you've done (read more about [pull requests](http://help.github.com/pull-requests/)). Please follow our | ||
coding conventions (below) and make sure all of your commits are atomic (one feature per commit). | ||
|
||
Please write a clear log messages for your commits. One-liners are OK for small changes, but bigger changes should include more: | ||
|
||
$ git commit -m "A brief summary of the commit | ||
> | ||
> A paragraph describing what changed and its impact." | ||
|
||
Note that a bot will require that you sign [our Contributor License | ||
Agreement](https://gist.github.com/youngmit/8654abcf93f309771ae9296abebe9d4a) | ||
before we can accept a pull request from you. | ||
|
||
## Coding conventions | ||
|
||
We use the [Black](https://black.readthedocs.io/en/stable/) code formatter so we don't have to argue or worry about trivial | ||
whitespacing conventions during code review. You should always run `black` before submitting a pull request. | ||
|
||
We really like Robert C Martin's [Clean Code](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882) book | ||
and at least nominally try to follow some of the advice in there. | ||
|
||
* Consider contacting some ARMI developers before embarking on a major new feature or development on the framework. | ||
We may prefer to keep various physics or design-specific developments in modular plugins (which can also be | ||
open source, of course!). The framework should be focused on frameworky stuff (broad, sharable stuff). | ||
As the Framework matures, we hope it will stabilize, though we recognize we need work before then. | ||
* We believe that comments can increase maintenance burdens and should only be used when one fails to explain | ||
the entire situation with the code itself. In practice, we fail to do this all the time, and need comments | ||
to help guide future readers of the code. | ||
* Names //really// matter. | ||
* Your PR will be reviewed and probably need some iteration. We aren't trying to be a pain or discourage you, | ||
we just want to make sure the code is optimal. | ||
|
||
## Licensing of Tools | ||
|
||
Be careful when including any dependency in ARMI (say in a requirements.txt file) not | ||
to include anything with a license that superceeds our Apache license. For instance, | ||
any third-party Python library included in ARMI with a GPL license will make the whole | ||
project fall under the GPL license. But a lot of potential users of ARMI will want to | ||
keep some of their work private, so we can't allow any GPL tools. | ||
|
||
For that reason, it is generally considered best-practice in the ARMI ecosystem to | ||
only use third-party Python libraries that have MIT or BSD licenses. | ||
|
||
## Documentation | ||
|
||
We use Sphinx for our documentation, and numpydoc to parse docstrings into the API docs section of our documentation. | ||
Thus, all docstrings are officially part of the technical documentation and should be written as such. | ||
For information on how to contribute to ARMI, see [our official documenation](https://terrapower.github.io/armi/developer/first_time_contributors.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
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
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
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
Oops, something went wrong.