Contributing

When contributing to this repository, please first create an issue containing information about the missing feature or the bug that you would like to fix. Here you can discuss the change you want to make with the maintainers of the repository.

Please note we have a code of conduct, please follow it in all your interactions with the project.

Adding a new feature

We really appreciate contributions to the project. If you want to add a new feature, please create an issue first to discuss the feature you would like to add. This way we can make sure that the feature is in line with the goals of the project and that it is not already being worked on by someone else.

Any new feature should be accompanied by tests and an example that should be part of the documentation. The tests should be added to the test suite in the tests folder and the example should be added to the example folder, and added to the _toc.yml file so that it is included in the documentation.

New contributor guide

To get an overview of the project, read the documentation. Here are some resources to help you get started with open source contributions:

• Finding ways to contribute to open source on GitHub

• Set up Git

• GitHub flow

• Collaborating with pull requests

Pull Request Process

Pull Request

• When you’re finished with the changes, create a pull request, also known as a PR. It is also OK to create a draft pull request from the very beginning. Once you are done you can click on the [“Ready for review”] button. You can also request a review from one of the maintainers.

• Don’t forget to link PR to the issue that you opened .

• Enable the checkbox to allow maintainer edits so the branch can be updated for a merge. Once you submit your PR, a team member will review your proposal. We may ask questions or request for additional information.

• We may ask for changes to be made before a PR can be merged, either using suggested changes or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.

• As you update your PR and apply changes, mark each conversation as resolved.

• If you run into any merge issues, checkout this git tutorial to help you resolve merge conflicts and other issues.

• Please make sure that all tests are passing, github pages renders nicely, and code coverage are are not lower than before your contribution. You see the different github action workflows by clicking the “Action” tab in the GitHub repository.

Enforced style guide using pre-commit hooks

We want to have a consistent style on all the contributions to the repository. The way we enforce this is through pre-commit hooks and contributors are encouraged to install the pre-commit hooks locally when developing. You can install the pre commit hooks by first install pre-commit

python3 -m pip install pre-commit

and then install the pre-commit hooks using the command

pre-commit install

at the root of the repository. This will install all the hooks listed in the file called .pre-commit-config.yaml in the root of the repository.

Every time you make a commit to the repository a set of tests will run to make sure that the changes you made are following the style guide. Usually, the hooks will autoformat your code so that you only need to do a git add again and then redo the git commit.

Note that when you make a push to the repo, the pre-commit hooks will be run on all the files in the repository. You can also run the pre-commit hooks on all the files using the command

pre-commit run --all

To learn more about pre-commit you can check out https://pre-commit.com

Test suite

For every new feature of bugfix you should also make sure to not lower the code coverage for the test suite. This means that if you for example add a new function then you should also make sure that the function is properly tested (at a minimum it should be covered by the test suite).

To run the test suite, please install the package with the optional dependencies test, i.e

python3 -m pip install -e ".[all]"

in the root of the repository. To run the tests you can execute the command

python3 -m pytest

Also make to sure to check that the tests also passes with mpiexec by running

mpiexec -n 2 python3 -m pytest

Note that we have a GitHub action that runs the tests on every push and pull request to the main branch of the repository.

You can read more about using pytest in the official documentation of pytest.

Documentation

The documentation is hosted at GitHub pages and created with JupyterBook. Contributions to the documentation is very welcomed.

To build the documentation locally you can installed the docs optional dependencies, i.e

python3 -m pip install -e ".[docs]"

in the root of the repository. Now you can build the documentation by running the command

jupyter-book build .

from the root of the repository. The command should complete without errors or warnings. In particular, you might want to run the command

jupyter-book build -W --keep-going .

which will turn warnings into errors.

For reference, please see the github workflow that is used for building the pages.

Need help?

If something is not working as expected, or you need help please file an issue.