-
Notifications
You must be signed in to change notification settings - Fork 93
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
Bin-Shuffling: reimplemented the continuos time version #397
Bin-Shuffling: reimplemented the continuos time version #397
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're giving quantites a hard time by throwing all the units you have in a mincer to chew them later on.
A bitter example of your attitude
surrogate_spiketrain = \
(surrogate_spiketrain * pq.s).rescale(spiketrain.units)
cries for help.
Instead, quantities require love: do gentle stripping at the entrance, and don't forget to dress them up before you're done.
Yes, sure. I would not consider myself as a friend of quantities. I like to work only on magnitudes, thus fast numpy arrays and only in the very end got back to quantities. |
…le#397) Also, fixed trial-shuffling, copy -> deepcopy Co-authored-by: dizcza <[email protected]>
The continuos time version of bin-shuffling preserves now the number of spikes. That is in contrast to how it was done before, where the spike train was first binned to a bool array.