For recordings with frame > (2 ** 31 - 1), data type of two variables in in prepare_spikesortingview_data need to change from np.int32 to np.int64. #229
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For recordings with frame > 2**31 - 1 (about 29.8h recording with Fs=20000),
num_frames
should be innp.int64
and
spike_train
should have elements innp.int64
.I changed these variables to have data type of
np.int64
only whenrecording.get_num_frames() > (2 ** 31 - 1)
.I tested this version for two 2.64 days recordings one sorted with scheme3 with
block_size = a day
, and the other one with scheme2.