-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent handling of "integration_method" in simulation config #275
Comments
Thanks for the report. It looks like the snap version (ie: However, I'm not sure why it's a string, considering it's numeric data. |
There is a mismatch between the spec and the implementation in the libsonata parser. I can update the spec to use the int values 0/1/2, if that's fine for you. |
I guess being an integer was done to be consistent with NEURON secondorder |
Hi!
I'm seeing inconsistent handling of the "integration_method" variable as either an integer or a string.
When using an integer (0), I get:
and when using a string ("0"), I get:
I'm using
py-bluepysnap/3.0.1
module from BB5.The text was updated successfully, but these errors were encountered: