SpikeInterface / SpikeInterface/spikeinterface
unit locations - extreme outliers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Obtaining unit locations via sorting analyzer like this:
analyzer = si.create_sorting_analyzer(
sorting, recording=recording_binary
)
# ...
# estimated unit locations
unit_locations = analyzer.get_extension("unit_locations").get_data()
Running into an issue where some of the unit locations are appearing way outside the probe. See screenshot. Any idea why this is happening and how it could be remedied?
The average waveform for the top outlier does not appear to be especially weird:
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 create_sorting_analyzer call using recording_binary and trace how the unit_locations extension is produced and read via get_extension("unit_locations"). Compare the reported extreme locations with the probe shown in the screenshot and the average waveform for the top outlier. Done means identifying the cause and documenting or implementing a verified remedy.
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
- 25/100