SpikeInterface / SpikeInterface/spikeinterface
Kilosort output for sorting analyzer
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
As mentioned in the KS (2.5/4) documentation, part of the sorting output prepared for curation is a number of npy files containing templates, similar templates, PC's, ... which are also calculated using a sorting analyzer for a number of metrics.
Could these features somehow be reused, or are they incompatible with sorting analyzer way of working?
Furthermore, what would be the advice when analyzing a recording processed by Kilosort: use the original recording or use the temp_wh.dat file produced by KS which contains already preprocessed (car, whitening, highpass filtered) data?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Kilosort export_files documentation and the sorting analyzer's existing metric inputs. Compare the exported npy files with the original recording and Kilosort's temp_wh.dat, then establish whether the features are compatible and which recording should be analyzed. Done means a clear compatibility result and preprocessing recommendation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100