SpikeInterface / SpikeInterface/spikeinterface
Incoherence between recording times and sorting/analyzer times
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Recording segments seem to be aware of non zero start times. However, when in an analyzer or sorting, times always assume the recording starts at time 0. This can be checked in the GUI for example.
I believe this does not create any main issue as the analyzer seems consistent with itself. However, this is very unintuitive and maybe not expected ?
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 reproducing the non-zero recording start-time behavior in the GUI, comparing recording segments with the times shown by an analyzer or sorting. Read the relevant recording, analyzer, and sorting entry points discovered from that reproduction. Done means the intended time convention is established and the displayed times are consistent or the discrepancy is documented.
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