Contribute to SEFEA#

There are many ways to contribute to SEFEA: reporting bugs, adding new functions, improving the documentation, etc…

If you like SEFEA, you can also consider buying the developers a headband from HNNK!

Code guidelines#

Before starting new code, we highly recommend opening an issue on GitHub to discuss potential changes.

Please use standard pep8 and flake8 Python style guidelines. To test that your code complies with those, you can run:
```
$ flake8
```
Use NumPy style for docstrings. Follow existing examples for simplest guidance.
When adding new functions, make sure that they are generalizable to various situations.
Changes must be accompanied by updated documentation and examples.
After making changes, ensure all tests pass. This can be done by running:
```
$ pytest
```

Checking and building documentation#

SSS’s documentation (including docstring in code) uses ReStructuredText format, see Sphinx documentation to learn more about editing them. The code follows the Pydata-Sphinx-Theme.

All changes to the codebase must be properly documented. To ensure that documentation is rendered correctly, the best bet is to follow the existing examples for function docstrings. If you want to test the documentation locally, you will need to install the following packages:

$ pip install --upgrade sphinx pydata-sphinx-theme

and then within the scut_eeg_feature/docs directory do:

$ make html