-
Hi, After adding What is the correct way to deal with such discontinuities that occur at time of activations? Edit: The functionality of My version of the file is:
I have this added to the The code I set up to check my implementation is:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Hmm, this may be a non issue and a waste of time. The |
Beta Was this translation helpful? Give feedback.
-
The limitation in Arbor mechanisms (as they currently are defined) is that we don't explicitly expose time as a parameter for use in BREAKPOINT. One can work around this though by adding a state variable
We don't support Exact timing can be recovered though by removing While the description in terms of the exponential function will work, a more natural definition of the alpha model though would be to use the differential form. The provided exp2syn synapse is close, as you noted, but doesn't apply in the case where the two time constants are equal. But t*exp(-t) is a solution to the second order differential equation y'' +2y' + y = 0, so we should be able to model it with a first order ODE with two state variables. I haven't verified the following, but I think this should be the equivalent to the exp2syn with equal time constants:
This is the event-based version, where the connection weight plays the role of gmax, and the effect of successive events is accumulative. |
Beta Was this translation helpful? Give feedback.
The limitation in Arbor mechanisms (as they currently are defined) is that we don't explicitly expose time as a parameter for use in BREAKPOINT. One can work around this though by adding a state variable
u
say which has derivative 1, e.g.We don't support
at_time
; NEURON uses it to indicate to a variable time step solver that there is a discontinuity at a particular point in time but we only have a solver that respects the specified max dt in the simulation, and outside of event handling, we don't account for discontinuiti…