Sam Yates
Sam Yates
This could be a good solution! Would you be modifying the recipe interface? (e.g. to inherit from a connection-set-specifying interface which captures connections_on and maybe gap_junctions_on?)
I think I'll make voltage clamps a new, separate issue!
As part of #1262 work, current stimuli are being moved out of mechanisms. The current WIP implementation supports piece-wise linear stimulus currents defined by an envelope, or a fixed frequency...
Stimuli as mentioned above have been moved library-side in PR #1407 — if the functionality there is insufficient to cover the cases currently implemented in NMODL, we'll have to look...
The alternative is to make two unit test runs: the runner sets some state or flag that determines the cpu or gpu execution context. Each specific test then runs with...
Just for reference, afaik NEURON deals with this via gap junctions.
Random NEURON forum post: https://www.neuron.yale.edu/phpBB/viewtopic.php?t=1949
Proposal: we find a real example that we can verify works in Arbor — or doesn't work in Arbor, and then we fix it.
In terms of how we treat it, is it better to: * pin the voltage as part of the model, that is, effectively change the maths so that the voltage...
Thanks, @espenhgn! Implementing something like `svclmp` would be straightforward, I believe, within the library proper (i.e. not as a mechanism). Perhaps this should be our first target, to be expanded...