Because of the pandas update, some of the subsetting of dataframes got broken. This PR also removes a lot of commented out code that has been hanging around and shouldn't be
[x] Is it mergable?
[x] Did it pass the tests?
[x] If it introduces new functionality in is it tested?
Check for code coverage. To run code coverage on only the file you changed,
for example flotilla/compute/splicing.py, use this command:
coverage run --source flotilla --omit=test --module py.test flotilla/test/compute/test_splicing.py
which will show you which lines aren't covered by the tests.
[x] Do the new functions have descriptive
numpydoc
style docstrings?
[x] If it adds a new feature, is it documented as an IPython Notebook in
examples/, and is that notebook added to doc/tutorial.rst?
[x] If it adds a new plot, is it documented in the gallery, as a .py file
in examples/?
[x] Is it well formatted? Look at the output of make lint.
[ ] Is it documented in the doc/releases/?
[x] Was a spellchecker run on the source code and documentation after
changes were made?
Because of the pandas update, some of the subsetting of dataframes got broken. This PR also removes a lot of commented out code that has been hanging around and shouldn't be
flotilla/compute/splicing.py, use this command:coverage run --source flotilla --omit=test --module py.test flotilla/test/compute/test_splicing.pywhich will show you which lines aren't covered by the tests.examples/, and is that notebook added todoc/tutorial.rst?.pyfile inexamples/?make lint.