draft implementation for timing cluster deploy. no chance yet to test this
modify as a cluster testing script. cluster testing script runs properly and setup.py changed to include it
print name of host where client is executed
make client print out running time in seconds on last line
add missing newline
add package method that does entire analysis without multiprocessing package
add tests for number of critical fragments generated for smaller systems
increase verbosity of test runner
Merge remote-tracking branch 'origin/develop' into develop
python setup.py install runs all tests already. do not repeat them
python setup.py test necessary to run tests
modify version bookkeeping to comply with PEP8
move install to install section
test that multiplicity of species and reactions in subgraphs conform with fragment
stop python setup.py test from running tests twice
distutils / setuptools test.suite seems to discover tests automatically,
importing test submodules at the top of gratelpy.tests.__init__ runs them twice
moved those imports into test.runtests() so that bin/gratelpy_test can still
invoke runtests() properly
Add minimal gratelpy_test call to travis testing
After a weird problem on my computer with calling gratelpy_test
I decided to add an option to call runtests for a minimal, quick
set of unit tests that can easily be called from gratelpy_test when
run on Travis CI. By default gratelpy_test still runs the full set
improve pep8 conformity of setup.py
Add helper functions to reduce reliance on format choice
Early on in development I decided to call species and reactions in certain ways,
choose certain data types and formats for fragments, edges, etc.
These helper functions are intended as a first step towards making the code less
reliant on these early decisions.
Add fragment duplicate and notation tests
Duplicate: make certain that each fragment is generated exactly once,
notation: make certain that the fragment notation reflects the edges structure
of the graph, i.e. species and reaction are aligned as edges,
there is exactly that one edge saved in the subgraph components dictionary,
the edge exists in both, digraph G and matrix alpha.
change version to 0.2.0-dev