SpikeInterface / SpikeInterface/spikeinterface
Error in postprocessing.compute_unit_locations(method = "center_of_mass"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Hello, spikeinterface successfully handles 2D probe information from a MaxWell MEA recording up until I try to find unit locations.
Because of the large data size(~5GB), I computed the SortingAnalyzer and templates with sparse=True.
The array returned by compute_unit_locations is completely flat on the second dimension (all values are 122.5), despite the get_channel_locations() function returning proper geometry.
Additionally, all other methods for unit location return values that don't make sense.
Do you know why I would have this issue?
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 postprocessing.compute_unit_locations and compare its inputs with get_channel_locations() for a MaxWell MEA recording processed through SortingAnalyzer and sparse=True templates. Reproduce the flat second dimension and inspect why the center_of_mass and other methods produce invalid locations; done means unit-location outputs reflect the returned channel geometry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100