Hi Francesco,
Updating a synapse on a regular time grid is fundamentally not supported by the NEST kernel right now, although I should mention that there have been attempts in the past to add this feature (https://github.com/nest/nest-simulator/pull/1160).
However, a better approach might be the following: whenever you need to "read out" or perform computations with your trace value, could you set up this read-out function to, as a first step, update the dynamical state of the synapse to the current time? So in addition to arriving presynaptic spikes triggering a synapse state update, this readout function would be a second way to trigger an update.
With kind regards, Charl
On Fri, Jul 29, 2022, at 02:30, francescojamal.sheiban@polimi.it wrote:
Hello Pooja,
Thanks for the further clarification! We understood that the bug concerned only the timing of the statement execution, not the execution itself.
I’m afraid that the solution you pointed out is already the one we have been exploring: we are indeed running the simulation in smaller chunks
- following the same approach as the tutorial pointed out by Charl -
but, since the eligibility trace value can only decay when spikes are arriving at the synapse and since the network has very few spikes, the trace only take big discrete leaps. The result is that we can retrieve as many trace values as we want, but they are mostly constant between chunks.
Our goal for now is to have an exponential trace that goes to 1 when a pre-synaptic spike arrives at the synapse and then smoothly decreases even in the absence of further spikes. Thus we were wondering if there was any way to execute statements in the NESTML code at each resolution tilmestep (other than the update block) that wouldn't require any network activity.
Best, Francesco _______________________________________________ NEST Users mailing list -- users@nest-simulator.org To unsubscribe send an email to users-leave@nest-simulator.org