Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistency in current injection initiation in NEST implementation #443

Open
appukuttan-shailesh opened this issue Feb 2, 2017 · 4 comments
Milestone

Comments

@appukuttan-shailesh
Copy link
Contributor

Take a look at the output for this code in NEST:
nest_bad_3sigs
It appears that the DCSource here is activated some time after the intended t_start. But after exploring further it is found that the issue is not with DCSource, but rather with the first instantiation, irrespective of current type. For example, this code shows the same issue for two ACSource's:
nest_bad_ac2same

The delay here is 0.9 ms. That, I believe, doesn't correspond to the simulator's dt. So not sure about its origin.

@appukuttan-shailesh
Copy link
Contributor Author

Interestingly, on rearranging the lines in this file to:

acsource1 = ACSource(start=start, stop=stop, amplitude=mean, offset=0.0, frequency=100.0, phase=0.0)
acsource2 = ACSource(start=start, stop=stop, amplitude=mean, offset=0.0, frequency=100.0, phase=0.0)
cells[0].inject(acsource1)
cells[1].inject(acsource2)

we get:
nest_bad_ac2same_bothdelay
i.e. both the signals now have a delayed activation of 0.9 ms.

@apdavison
Copy link
Member

The bug is related to the default "auto" setting for the min_delay parameter. If you explicitly set min_delay,
using setup(min_delay=1.5) (for example) then the current sources are correctly activated at 50.0 ms

@apdavison apdavison added this to the 0.8.3 milestone Feb 2, 2017
@apdavison apdavison modified the milestones: 0.8.3, 0.8.4 Mar 9, 2017
@apdavison apdavison modified the milestones: 0.9.0, 0.9.1 Apr 11, 2017
@apdavison apdavison modified the milestones: 0.9.1, future Jun 1, 2017
@appukuttan-shailesh
Copy link
Contributor Author

@apdavison : Any thoughts on how to fix this? How should we handle the default "auto" setting?

@apdavison
Copy link
Member

I think the only way to handle it properly is to defer connection of the current sources to the neurons until run() is called.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants