FreeDiscovery- Contributing


This section aims to regroup useful information for contributing to FreeDiscovery.


Submitting bugs

Please feel free to open an issue in the GitHub issue tracker at for any problem that you may encounter.

Running the test suite (cf. below) may also help in diagnosing the source of the problem.


Installing the development version

To install a the development version of FreeDiscovery,

  1. If you do not have Miniconda installed, follow this tutorial.
  2. If you haven’t done it before, add conda-forge to the conda channels,
conda config --append channels conda-forge
  1. Download and install the developpement verision of FreeDiscovery,
git clone FreeDiscoveryconda create -n fd-env --file requirements_engine.txt python=3.6source activate fd-envpip install -e .

this will create a virtualenv called fd-env which you can activate with source activate fd-env then start freediscovery with freediscovery run.Note: if you already have the fd-env environement, you may need to delete it first with conda env remove -n fd-env.


This section describes the workflow for creating Pull Requests (PR). For more complex contributions, it may also be useful to create an associated issue.

  1. Fork the FreeDiscovery repository
  2. Clone this fork on your computer and install it
  3. Make the appropriate changes
  4. Make sure that the tests suite (cf. below) does not produce errors
  5. Commit and push the changes to GitHub
  6. Create a Pull Request from your branch to the master branch
  7. If any of the continuous integration services (Travis CI, Appveyor CI, Circle CI) produce an error, review the corresponding output and fix the code if appropriate.
  8. After the PR is merged, this branch can be safely deleted from your fork (and a new one may be created for subsequent contributions).

Test Suite

A two level test suite is implemented in FreeDiscovery, that validates both the algorithms and the REST API,

The tests are located under freediscovery/tests/ and can be run with,

py.test -s .

Building Documentation

1. Sphinx documentation

The html documentation can be built from sources with,

# starting the FreeDiscovery server at localhostcd FreeDiscovery/doc/make html

which requires to install dependencies in build_tools/requirements_extra_pip.txt. This would also run and include examples using sphinx-gallery.

Alternatively make latexpdf generates documentation in .pdf format (requires pdflatex).

2. REST API documentation

The rest API documentation can be generated with,

sudo npm install -g bootprint sudo npm install -g bootprint-openapibootprint openapi openapi_docscp -r openapi_docs/ _build/html/