-
Notifications
You must be signed in to change notification settings - Fork 230
Add similarity_method param in automerge and fix multi-segment cross-contamination #4201
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
Conversation
|
Looks good! Could you add a multi-segment test to (The current tests are a bit messy, I don't know why we need to keep recomputing analyzers when we have a fixture. Also the default analyzer is pretty long (5mins) so the tests are quite long -- 30s locally) |
|
Why having a CC by segment ? what is the rational behing this ? |
Co-authored-by: Chris Halcrow <57948917+chrishalcrow@users.noreply.github.com>
…into automerge-fixes
|
|
||
| unit_id1 = unit_ids[unit_ind1] | ||
| spike_train1 = np.array(sorting.get_unit_spike_train(unit_id1)) | ||
| for segment_index in range(num_segments): |
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.
instead of doing this, concatenate_sortings
No description provided.