SpikeInterface / SpikeInterface/spikeinterface
`TdtRecordingExtractor` not reading signal streams correctly for multi-block experiment
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
This experiment from @JBFord has 3 signal streams with mult-block (10 blocks) setup, the reader TdtRawIO can parse the header but TdtRecordingExtractor returns empty list of times and traces, sampling frequency is 1, the data type is int.
The data for one of the blocks look like https://gin.g-node.org/NeuralEnsemble/ephy_testing_data/src/master/tdt/aep_05/Block-1 but also have multiple SEV files like in https://gin.g-node.org/NeuralEnsemble/ephy_testing_data/src/master/tdt/dataset_1_single_block.
@JuliaSprenger have you seen similar before with multiple data streams and multiple block example?
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 TdtRecordingExtractor and TdtRawIO entry points, then reproduce the issue using the linked multi-block experiment and SEV-file examples. Check why a three-stream, ten-block recording produces empty times and traces while reporting sampling frequency 1 and integer data. Done means the extractor returns the expected times and traces for the multi-block, multi-stream data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100