-
Notifications
You must be signed in to change notification settings - Fork 0
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
Issue when setting delay=0 to NetCon and multiple cores #17
Comments
Yes, a higher default would be better. It may even be best to make it a required argument without a default at all? Or default value |
In the case of a transmitter sending to multiple receivers |
Hmm, indeed ... but that would mean that if you have a connection from section A to B and section A to C that they can not have different delays. That seems like an impossible restriction for NEURON, especially when you know that in NEURON 99.9% of users have strictly 1 NetCon on the soma of each cell. There must/might be a workaround. Maybe:
Otherwise, ask the NEURON devs how to deal with the situation where 2 different delayed spike signals need to be emitted from the same Once you know more, it will become clear what the best solution is :) |
https://github.com/dbbs-lab/bsb-neuron/blob/fc35e97006692c2e3aa1a570ce49b01c28d29b6d/bsb_neuron/connection.py#L30C5-L30C49
I think this overwrites the default values that were initialized here https://github.com/dbbs-lab/patch/blob/4d7442f726a556d28a7b72629baf3d427fac6568/patch/interpreter.py#L134 placing the NetCon.
A delay by default equals to 0 will give this NEURON error: usable mindelay is 0 (or less than dt for fixed step method) when running in parallel.
Probably better to keep the same default values as in patch/interpreter.py ?
The text was updated successfully, but these errors were encountered: