SpikeInterface / SpikeInterface/spikeinterface
Zero-lag peak asymmetry in plot_crosscorrelograms
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
When plotting correlograms for a unit pair using plot_crosscorrelograms, one off-diagonal panel shows a strong zero-lag peak (as expected for double detection), but the other off-diagonal looks like an ACG trough (no zero-lag peak).
In Phy, both off-diagonals show the zero-lag peak for the same pair.
Any idea why CCG(A,B) shows a strong zero-lag peak but CCG(B,A) doesn’t, while Phy shows peaks in both for the same pair?
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 by locating the plot_crosscorrelograms entry point and tracing how CCG(A,B) and CCG(B,A) are computed and rendered. Compare the result with the paired unit's Phy correlograms; done means both off-diagonal panels consistently show the expected zero-lag peak for the same double detection.
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
- 35/100