Some typing in optimization_management and model classes.
6 meaningful Unit tests running over continuous integration that work:
Two of the unit tests simply checks if optimization effectively brings down the error (or brings up the fitness) of known multispiking model problems (for adexp and izhikevich models).
the other unit test checks for jithub model integration with NU, and BPO optimization frameworks.
reconciled jithub models with NU optimization workflow.
An allenapi directory in NU.
cleaned out unit_test trash. Assuming 90% of files where mine and are now depreciated.
Flaws:
Uses my own branches of sciunit@dev that has observation, unit validation turned off via code comments. Can't find a more graceful way to turn it off.
Both a strength and a weakness, depends specifically on my: efel branch, my BPO branch, my sciunit branch, my jithub branch.
NB: i do not have access to travis-ci testing, however, .circleci/config.yml is very similar to .travis.yml and one can easily cherry pick build statements and move from one to the other.
They are both free and compatible, so they can both readily co-exist.
@rgerkin Features:
Some typing in optimization_management and model classes.
6 meaningful Unit tests running over continuous integration that work:
Two of the unit tests simply checks if optimization effectively brings down the error (or brings up the fitness) of known multispiking model problems (for adexp and izhikevich models).
the other unit test checks for jithub model integration with NU, and BPO optimization frameworks.
reconciled jithub models with NU optimization workflow.
An allenapi directory in NU.
cleaned out unit_test trash. Assuming 90% of files where mine and are now depreciated. Flaws:
Uses my own branches of sciunit@dev that has observation, unit validation turned off via code comments. Can't find a more graceful way to turn it off.
Both a strength and a weakness, depends specifically on my: efel branch, my BPO branch, my sciunit branch, my jithub branch.
NB: i do not have access to travis-ci testing, however, .circleci/config.yml is very similar to .travis.yml and one can easily cherry pick build statements and move from one to the other.
They are both free and compatible, so they can both readily co-exist.