Comment on page

Chapter 3

Chapter 3: Contributing Guidelines

3. Contributing Guidelines

Table of Contents

3.1 Introduction

Epispot is built on open-source contributions and we're glad that you want to contribute. First things first, if you want to contribute you will need the link to the GitHub source: All contributions to epispot should be submitted as pull requests on GitHub which we can then merge. In order to facilitate this review process, epispot has created a set of contributing guidelines which you can view here. The goal of this page in the manual is to further expand on some of the principles touched on in that document and make it easier to contribute to epispot. Continue reading to learn how to start.

3.2 Installation

The installation process for development is just a bit different from the standard installation process. This will make it easier to do testing and code coverage analysis locally, which will be described later. However, you can always perform these on GitHub if you prefer and just install epispot-nightly instead with:
pip install epispot-nightly
In this case, you can skip all but the first section of this chapter. However, it will be worth it to build epispot from the source as it is easier to run tests and debug your code locally.

3.2.1 Cloning from VCS

If you don't have git already, you can install it here: Epispot uses git as its de-facto version control system, so it'll help to get familiar with the fundamentals of git. After you have, make sure to learn the basics of GitHub so that you understand how to submit your pull request when it's time. The first step will be to fork the GitHub repository by clicking the "Fork" button and creating a copy under your username. Next, clone your local copy with git by providing the GitHub URL to your fork like this:
# replace username with your GitHub username
git clone
This should create a folder containing the epispot codebase. Run the following commands from inside the folder to initialize the repository properly and get it up-to-date:
git checkout master
git pull
Finally, create a new branch to work on locally with:
git branch name # replace name with branch name
Choose a name that clearly states, in one or two words, what the purpose of the branch is and what it does. Good branch names are short, concise, and descriptive. Here are a few good examples:
git branch super-coverage # increases code coverage
git branch pdoc-mako # adds mako templates to pdoc
git branch docs-overhaul # recreates documentation
If you are working on fixing an issue, use a branch name that specifies the issue number that you are fixing after the patch label like this:
git branch patch-num # replace num with issue #
Now checkout your branch and you're ready to go! The next section will cover how to get ready to install epispot after you've cloned the repo.

3.2.2 Environment Setup

The next thing you'll want to do after cloning the repository is set up a Python virtual environment. This will allow you to set up epispot's dependencies in a separate environment from your standard Python installation. The steps to create the virtual environment are listed below for pip and conda systems:
python -m venv epispot
source tutorial-env/bin/activate
# If the last command returns an error on Windows, run:
# tutorial-env\Scripts\activate.bat
conda create -n epispot anaconda
source activate epispot
# When installing packages, use the below script
# to ensure that they are installed to the `epispot`
# virtual environment:
# conda install -n yourenvname [package]
Please note that epispot is designed for Python 3, and it is ideal that you use a Python version greater than or equal to 3.6 when creating these virtual environments.
Now, type python into your shell and you should see an interactive shell similar to the one shown below pop up.
(epispot) $ python
Python 3.7.2 (default, May 6 2016, 10:59:36)
Make sure that the Python installation is greater than or equal to Python 3.6 and that the (epispot) virtual environment indicator shows up. Next, you're ready to build epispot from the source.

3.2.3 Building from Source

First off, you'll need to install all package dependencies into your virtual environment. If you are using pip, just navigate to the root repository directory and type:
pip install -r requirements.txt # Install package dependencies
pip install -r bin/requirements.txt # Install CLI dependencies
This will install numpy, matplotlib, and fire for the CLI. Finally, you can build epispot from the source file with:
python develop
This will create a symbolic link to the package that will prevent you from constantly re-installing epispot. However, if you would like to reinstall epispot every time a change is made and keep a stable epispot installation on your computer, you can run:
python install
each time you make a change. And that's all! Fire up a shell from anywhere within the repository and import epispot with:
$ python
Python 3.7.2 (default, May 6 2016, 10:59:36)
>>> import epispot
>>> print(epispot.version)
✨🍰✨ Congratulations!

3.3 Structure

Understanding any repository and package's structure is key to being able to effectively contribute to it. Luckily, epispot's structure (both internally and on a repository-scale) is quite simple and easy-to-learn.

3.3.1 Repository Structure

This is probably the easiest structural element in epispot. As you can see from your local copy, epispot is divided into five directories plus the root directory. First, let's go over the root directory (where all the dotfiles are located).
In the root directory, you'll find the following dotfiles:
  • .codecov.yml
  • .coveragerc
  • .deepsource.toml
  • .travis.yml
  • .gitignore
The first two are for code coverage configuration. .coveragerc tells, epispot's code coverage analyzer tool, which directories to search and which to ignore. .codecov.yml tells CodeCov, epispot's external code coverage reporting tool, when to fail depending on the percentage by which code coverage has decreased. The next two are for code analysis. .deepsource.toml tells DeepSource, epispot's code quality analyzer, where the source files are. .travis.yml configures a Travis CI routine to run on push to any branch. Lastly, we make it to the .gitignore. This is a pretty standard Python .gitignore which will ignore the usual cache directories.
Apart from these dotfiles, epispot's root contains a few markdown documents, mainly intended for specific types of contributions that we'll cover in this document. It also contains a and where the latter is used for the nightly package. The same suffix is used in, too, where it indicates a different package version.
Finally, epispot's root directory contains the basic packaging documents, like, requirements.txt, pyproject.toml, and various others.
The next directory is the .github directory which contains a collection of GitHub-related tools and files designed to optimize the repository. These contain automated workflow scripts that run (e.g. to create documentation), issue and pull request templates, and a CODEOWNERS file which is used to determine the owner of each part of the epispot codebase. This will be discussed later.
The bin/ and epispot/ directories are where the source code is stored. bin/ is used for the CLI and epispot/ for the package itself. Lastly, we have the tests/ directory which contains epispot's testing suite and the explorables/ directory which contains a multitude of explorable examples.

3.3.2 Package Structure

epispot's internal structure is quite simple. Each unit of code has its own file and each subunit its own class. The main files are,,,, and The last, of course, initializes the package. The source code runs a relatively simple routine:
  • Defines dependency check
  • Imports built-in packages
  • Runs dependency check
  • Imports dependencies
  • Imports modules
  • Defines sanity check
  • Defines global variables
  • Runs sanity check
This routine runs every time epispot is initialized or imported. The next module we'll look at is the file. This will show you how to use the docstrings to understand what is going on inside the package. Epispot's code is well-documented and is optimized for additions, deletions, and modifications because it is self-explanatory. For example, if we open up the Models.get_deriv method, we can see its source code is simple and well-explained:
def get_deriv(self, time, system):
Return list of derivatives from each layer.
Used by `integrate()` for evaluating model predictions.
- time: Time to take derivative at
- system: System of state values (S, I, R, etc.) --> e.g [973, 12, 15]
- return: List of derivatives in the order that layers were added
derivatives = []
for layer in range(len(self.layers)):
derivatives.append(self.layers[layer].get_deriv(time, system))
return derivatives
From this, you can see how epispot forms links between various classes and modules. If you prefer, you can also view these docstrings with their corresponding source code online.
Last modified 2yr ago