-
Notifications
You must be signed in to change notification settings - Fork 231
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
Tutorial 4: Synaptic neuron not matching expected results #320
Comments
I also confirmed that there was a problem. The output of Synaptic Conductance-based Neuron Model With Input Spikes is strange. If you modify the hyperparameters alpha and beta defined in Markdown 1.2, you can get the spike values. I'm working on translating the SNN Torch tutorials into Korean, and would appreciate it if anyone could let me know here if this issue is resolved. |
Hi, I am also having the same issue with Tutorial 4. When I manually implement the synaptic LIF model as described in the tutorial it works as expected. But when I try to reproduce the same simulation with snn.Synaptic, the membrane voltage for some reason goes to infinity. I also noticed that the input spikes are not converted into synaptic current. Are there any updates regarding this issue? Thank you! snntorch version: 0.9.1 Here are the two versions of my code and the simulation results:
|
I have the same issue while making tutorial 4. The problem is in this call: It has a bug in the first sentence of the forward function of the Synaptic neuron, it overrides the
Nevertheless, I think the correct way to use Synaptic is to instantiate the neuron: |
I think just change to " if not syn == None: self.syn = syn" this will be fine !! By the way, thanks for sharing! |
Discussed in #319
Originally posted by prntechnologies April 25, 2024
I've been going through all of the tutorials and I'm having an issue with Tutorial #4. It seems that I'm not getting the same results using the Synaptic neural model as what is described in the tutorial?
Anyone else having issues following along, or is it just me?
The text was updated successfully, but these errors were encountered: