Developer Guide

Building the documentation

We use the same process as nengo to build the documentation.

Development workflow

Development happens on Github. Feel free to fork any of our repositories and send a pull request! However, note that we ask contributors to sign a copyright assignment agreement.

Code style

For python code, we use the same conventions as nengo: PEP8, flake8 for checking, and numpydoc For docstrings. See the nengo code style guide.

For C++ code, we roughly adhere to Google’s style guide.

Unit testing

We use PyTest to run our unit tests on Travis-CI. We run nengo’s full test-suite using nengo_mpi as a back-end. We also have a number of tests to explicitly ensure that results obtained using nengo_mpi are the same as those obtained using Nengo to a high-degree of accuracy. Tests are run using the invocation:

py.test