SpikeInterface / SpikeInterface/spikeinterface
detect_peaks method returns peaks in neighboring channels when set to 'locally_exclusive'
@JoeZiminski is already working on this.
Since Jun 21, 2024.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
I am currently using SpikeInterface's peak detection module to detect peaks from an NWB recording that I have.
detect_peaks(recording,
method='locally_exclusive',
peak_sign='neg',
detect_threshold=6,
exclude_sweep_ms=0.1,
**job_kwargs
)
This returns peaks which occur at the same sample_ind and neighboring channels (353 and 354). Channel 353 (48, 3520) and Channel 354 (0, 3540) are 52 um apart. This is less than 100 um, which is the default exclusion radius specified.
This seems abnormal. Do you know why this might be?
cc @rly
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.
Assessment
This issue has not been assessed yet.