You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the amplitude times of StepCurrentSource have inconsistent values when they're being set after a call to run(), when using nest as a simulator. For example the following code:
I also don't really understand why the amplitude times equals to 0 are set to 0 + resolution when the biological time is still equal to 0, as nest.biological_time and simulator.state.t are both equal to 0 at this moment.
I have also a question about the different values that nest.biological_time and simulator.state.t output. I understand that in the run() method of the _State class, the simulations last 1 timestep more than wanted to get all the recorded data from Nest. But why does this occur only when self.running is set to False, i.e. when calling run() a second time this additional timestep of simulation won't be added. This doesn't impair at all the gathering of all the recorded data corresponding to the 'second simulation'?
(Sorry for the ugly edit, I posted the issue by mistake while I was still writing it)
The text was updated successfully, but these errors were encountered:
RCagnol
changed the title
Inconsistency in thee
Inconsistency when setting the amplitude times of StepCurrentSource after several simulation runs
Oct 7, 2022
Hi,
I noticed that the amplitude times of StepCurrentSource have inconsistent values when they're being set after a call to run(), when using nest as a simulator. For example the following code:
Outputs the following, with amplitude times lower than the current biological time when they're being set after the first run:
Naively, I'd suppose that the source of this error lies in the _check_step_times() method of the NestStandardCurrentSource class, where
should be replaced by:
I also don't really understand why the amplitude times equals to 0 are set to 0 + resolution when the biological time is still equal to 0, as nest.biological_time and simulator.state.t are both equal to 0 at this moment.
I have also a question about the different values that nest.biological_time and simulator.state.t output. I understand that in the run() method of the _State class, the simulations last 1 timestep more than wanted to get all the recorded data from Nest. But why does this occur only when self.running is set to False, i.e. when calling run() a second time this additional timestep of simulation won't be added. This doesn't impair at all the gathering of all the recorded data corresponding to the 'second simulation'?
(Sorry for the ugly edit, I posted the issue by mistake while I was still writing it)
The text was updated successfully, but these errors were encountered: