-
Notifications
You must be signed in to change notification settings - Fork 98
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
isolate_protocols=True causing NEURON to reset dt #424
Comments
Hello @wthun , Thank you for opening this issue. The error is expected in this case. It happens because you ask both for cvode=True and a specific time step dt of 0.1. These two requirements are incompatible since cvode means varying time step. Therefore if you wish to use cvode you shouldn't pass a dt when initializing the simulator object. The error message is not very explicit. We will work on it. |
Hello, I seem to get the same error when disabling cvode. There is an example attached in the original post, where passing |
Indeed. I am sorry I misunderstood your example. We will fix that. |
No worries and thanks for the help! |
Hi! It looks like this is out of the scope of BluePyOpt, and should be solved at the NEURON level. I'll open an issue there first, and see if we have to change BluePyOpt once they have acted on it. Thanks for raising this issue @wthun |
Yes, but I originally encountered this on Linux. I receive the same error If I run the same example using Ipyparallel and passing lview.map_sync to the optimiser ((like this). In that case, isolate_protocols doesn't seem to help. |
Alright, the latest version of BluePyOpt should work fine with custom |
I'll close this issue. If you still have problems @wthun do not hesitate to re-open it. |
When passing a simulator with a fixed, non-standard time step to ephys.evaluators.CellEvaluator, I receive:
This only happens when setting isolate_protocols to True, so I guess this happens due to the dt value not persisting when NEURON is imported onto new threads (i.e. around line 252 in protocols.py)?
I see the same behaviour in a minimal example.
The text was updated successfully, but these errors were encountered: