Traceview shows invalid traces for spikes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 430
- Forks
- 187
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 2
Description
Hi all,
I'm using Kilosort2.5 for spike sorting 256 channels (128 + 2*64 probes - they are independent and in Kilosort channel map I set kcoord to 1,2,3). When I load kilosort output into phy, traceview doesn't seem to show me the correct channel map. Also shown traces don't seem to correspond to the mean waveforms in the waveform view. Please check the screenshot. I will appreciate if you could provide info on how to fix this.
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
Reproduce the issue by loading Kilosort2.5 output for the 256-channel setup into phy and compare TraceView with the waveform view. Inspect how the configured channel map and kcoord values are interpreted; done means TraceView uses the correct channel mapping and its traces correspond to the mean waveforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100