neuronunit
neuronunit copied to clipboard
scidash
A package for data-driven validation of neuron and ion channel models using SciUnit
There is an unresolved merge conflict in the requirements.txt file https://github.com/scidash/neuronunit/blob/835235e4ca58545e36d1914571e5adc314d81fef/requirements.txt#L41
The `install_requires` field in `setup.cfg` contains several constraints on the versions of packages which specify specific versions of each of the packages. Likely, neuronunit would work with other versions of...
@rgerkin can you please have a look at the dev tree e.g. this file https://github.com/scidash/neuronunit/blob/dev/neuronunit/models/backends/__init__.py has merge conflicts inside
https://github.com/NeuralEnsemble/libNeuroML/issues/97
@rgerkin I am not sure if the significance of this result was understood. From my perspective it meant that jNeuroML models could not be regarded as a ground truth until...
Duplicated content injected current test protocol/parameter at different levels in test protocol dictionary. This can lead to conflicts in test parameters used.
It could be possible to have a `stimulation_type` key at the same level as other keys. Examples: ```python test.protocol['Stimulation_Type'] = str('ramp') test.protocol['PEAK_AMP'] = 1500*qt.ms test.protocol['DELAY'] = 500*qt.ms test.protocol['DURATION'] = 1000*qt.ms...
Two and a half locations are * `model.set_stop_time()` * `test.protocol` (or `test.params` I can't remember which). * `current['DELAY']; current['DURATION'] model.inject_square_current(current)` * model._backend may also have its own set_stop_time, but its...
Producing such diagrams could help developers understand the unforeseeable consequences of design changes.