Add sorting reader#23
Draft
JoeZiminski wants to merge 8 commits into
Draft
Conversation
07837ca to
5d739c5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a rough prototyping PR to add spikes loaded from kilosort output to the GUI. It is branched from #22. Currently it does not load spikeinterface sorting analyzer, that is reserved for a separate PR.
Since #22 makes it possible to show only a single shank, there are four cases to consider:
Currently the user must input the shank that the sorting is one (
Nonefor all) because I couldn't quickly figure out a way to infer the shank from the sorting output, however it is probably possible.TODO MAJOR:
TODO:
An example script: