-
Notifications
You must be signed in to change notification settings - Fork 7
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
GPU weird bug in NewState #234
Comments
rcoreilly
added a commit
that referenced
this issue
Jun 3, 2023
Important: when switching back to NewState on GPU, need to update to use proper logic for |
rcoreilly
added a commit
that referenced
this issue
Jun 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is a very strange bug in GPU NewState:
layerparams.go:
This works fine in CPU mode, and is clearly free of an actual coding error, but the GPU version returns 0 for those
NrnV
access calls of theBurst
andCaSpkD
variables. It sets the new values just fine, including setting Burst etc, but reading these values just plain fails for reasons that are entirely unclear.Originally this code was being called from a Pool level dispatch, but changing it to neuron-level did not fix the problem (but is more performant).
There is some kind of read cache breakage here that we need to figure out. Meanwhile, using a temporary solution of just doing the NewState on CPU -- not a big deal performance-wise.
The text was updated successfully, but these errors were encountered: