Accuracy problem about spyketorch HOT 4 CLOSED

Hi,
SpykeTorch's implementation of the paper is slightly different than the original C++/CUDA implementation. We also acknowledged this performance drop in SpykeTorch's paper (https://www.frontiersin.org/articles/10.3389/fnins.2019.00625/full).
I guess with a little bit of parameters tuning in SpykeTorch's implementation, one can achieve better performance.

from spyketorch.

@meltingCat You can try to increase timesteps a little, for example, timesteps = 30 can achieve an accuracy of 97.2%.

from spyketorch.

@wusaifei Thanks, I will try.

from spyketorch.

@wusaifei Increasing timesteps to 30 wasn't work.

Current Train: [0.9836 0.0164 0.    ]
   Best Train: [9.8415e-01 1.5850e-02 0.0000e+00 6.4500e+02]
 Current Test: [0.9635 0.0365 0.    ]
    Best Test: [9.662e-01 3.380e-02 0.000e+00 5.200e+02]
time elapsed: 99914.84 seconds
time elapsed: 99914.83597874641 seconds

from spyketorch.