nest-simulator icon indicating copy to clipboard operation
nest-simulator copied to clipboard

Consistent behavior of sampling time for multimeters and spike_recorders for co-simulation

Open dionperd opened this issue 3 years ago • 1 comments

In the context of tvb-multiscale cosimulation, it is possible to perform a NEST -> TVB update either

  • via a population spike trains -> mean population rate conversion, or
  • via a population membrane potentials -> mean population membrane potential averaging,

after a fixed interval of cosimulation equal to a number of TVB simulation steps, after which the two simulators have to synchronize by exchanging data.

Spike recorders, used for the first interface, will send spike times within the full proper interval, i.e., within the times [interval_start + resolution, interval_stop].

Instead, multimeters, used for the second kind of interface, need to be simulated for an extra NEST resolution step or NEST min delay step, for the values to be recorded by the multimeter, i.e., one has to simulate until interval_stop + resolution/min_delay, in order to get the value with time stamp "interval_stop".

I am not sure if there is a solution for this problem, but I would still like to raise an issue!

dionperd avatar Jan 18 '22 17:01 dionperd

Issue automatically marked stale!

github-actions[bot] avatar Mar 30 '22 08:03 github-actions[bot]

This would likely require significant changes, but we keep it in the backlog.

heplesser avatar Nov 25 '22 14:11 heplesser

Issue automatically marked stale!

github-actions[bot] avatar Jan 26 '23 08:01 github-actions[bot]