-
Notifications
You must be signed in to change notification settings - Fork 60
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #317 from elfi-dev/dev
Release v. 0.7.5 - Improved the appearance of figures produced by `plot_gp` and added the option to draw true parameter indicators on the subplots using the optional input `true_params` - Modified DCC model by taking into account that subject can't infect herself - Added ability to set minimizer constrains for BOLFI - Enable bolfi.fit using only pre-generated initial evidence points - Fixed a bug causing random seed number to be deterministic - Updated requirements-dev.txt with pytest>=4.4 - Minor changes to documentation and refactoring - Added `make test-notslow` alternative
- Loading branch information
Showing
27 changed files
with
243 additions
and
117 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
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 |
---|---|---|
|
@@ -54,61 +54,76 @@ If you are proposing a feature: | |
* Remember that this is a volunteer-driven project, and that contributions | ||
are welcome :) | ||
|
||
|
||
Get Started! | ||
------------ | ||
|
||
`ELFI` is a project with dozens of collaborators, so organization is key to making our contributions effective and avoid reword. Thus, in addition to the recommendations below we strongly recommend reading our `Wiki <https://github.com/elfi-dev/elfi/wiki>`_ to see what is the suggested git workflow procedure for your type of contribution. | ||
|
||
Ready to contribute? Here's how to set up `ELFI` for local development. | ||
|
||
1. Fork the `elfi` repo on GitHub. | ||
2. Clone your fork locally:: | ||
|
||
$ git clone [email protected]:your_name_here/elfi.git | ||
|
||
3. Install your local copy and the development requirements into a conda environment:: | ||
3. Make sure you have `Python 3 <https://www.python.org/>`_ and | ||
`Anaconda Distribution <https://www.anaconda.com/>`_ installed on your | ||
machine. Check your conda and Python versions:: | ||
|
||
$ conda -V | ||
$ python -V | ||
|
||
4. Install your local copy and the development requirements into a conda | ||
environment. You may need to replace "3.5" in the first line with the python | ||
version printed in the previous step:: | ||
|
||
$ conda create -n elfi python=3.5 numpy | ||
$ source activate elfi | ||
$ cd elfi | ||
$ make dev | ||
|
||
4. Create a branch for local development:: | ||
5. Create a branch for local development:: | ||
|
||
$ git checkout -b name-of-your-bugfix-or-feature | ||
|
||
Now you can make your changes locally. | ||
5. Follow the `Style Guidelines`_ | ||
|
||
6. When you're done making changes, check that your changes pass flake8 and the tests:: | ||
6. Follow the `Style Guidelines`_ | ||
|
||
7. When you're done making changes, check that your changes pass flake8 and the tests:: | ||
|
||
$ make lint | ||
$ make test | ||
|
||
You may run `make test-notslow` instead of `make test` *as long as your proposed changes are unrelated to BOLFI*. | ||
|
||
Also make sure that the docstrings of your code are formatted properly:: | ||
|
||
$ make docs | ||
|
||
7. Commit your changes and push your branch to GitHub:: | ||
8. Commit your changes and push your branch to GitHub:: | ||
|
||
$ git add . | ||
$ git commit -m "Your detailed description of your changes." | ||
$ git push origin name-of-your-bugfix-or-feature | ||
|
||
8. Submit a pull request through the GitHub website. | ||
9. Submit a pull request through the GitHub website. | ||
|
||
Style Guidelines | ||
---------------- | ||
|
||
The Python code in ELFI mostly follows `PEP8 <http://pep8.org/>`_, which is considered the de-facto code style guide for Python. Lines should not exceed 100 characters. | ||
|
||
Docstrings follow the `NumPy style <http://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_numpy.html>`_. | ||
|
||
Pull Request Guidelines | ||
----------------------- | ||
|
||
Before you submit a pull request, check that it meets these guidelines: | ||
|
||
1. The pull request should include tests that will be run automatically using Travis-CI. | ||
1. The pull request should include tests that will be run automatically using | ||
Travis-CI. | ||
2. If the pull request adds functionality, the docs should be updated. Put | ||
your new functionality into a function with a docstring, and add the | ||
feature to the list in README.rst. | ||
|
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,4 +1,3 @@ | ||
|
||
Quickstart | ||
========== | ||
|
||
|
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 |
---|---|---|
|
@@ -26,4 +26,4 @@ | |
__email__ = '[email protected]' | ||
|
||
# make sure __version_ is on the last non-empty line (read by setup.py) | ||
__version__ = '0.7.4' | ||
__version__ = '0.7.5' |
Oops, something went wrong.