Extracting recording from multiwell
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Start with the read_biocam extractor and the stream_id handling described in the issue, checking how well_A1 is selected and whether another well can be selected. Then trace the BrainWave6 scale-factor conversion and probe geometry passed to the SpikeInterface GUI. Done means multiwell recordings, analog values, and channel positions are represented correctly.
Written by the indexing model from the issue text.
Description
Hi,
I'm currently working with a 3Brain multiwell and I noticed that biocamraw is not compatible with the multiwell system. Whenever I use the extractor read_biocam, only the well_A1 is selected.
I tried to modify the script and now I can extract multiwell recordings by specifying the well name as the stream_id (stream_id = well_A2).
On the other hand, I'm not sure about the code line responsible for converting the digital value to the analog one, since in the BrainWave6 output file there is no more the possibility to extract the scale factor (to my knowledge).
Together with this, the probe geometry is not correctly represented when represented in spikeInterface GUI. In particular, channels are not correctly located in the virtual representation of the probe.
Since I'm a beginner with coding I would greatly appreciate if some of you could help me in improving the script.
Thank you for your help.
Best regards,
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
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.
More from SpikeInterface/spikeinterface
-
testing
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
SpikeInterface/spikeinterface#4756 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
SpikeInterface/spikeinterface#4745 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SpikeInterface/spikeinterface#4510 · 2 comments ·
-
performance
Difficulty 4/5 3-5 days Newbie friendliness 55/100
SpikeInterface/spikeinterface#4787 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
SpikeInterface/spikeinterface#4781 · 1 comment ·
All issues in SpikeInterface/spikeinterface
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
zostera/django-bootstrap4#894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3276 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zilliztech/memsearch#759 ·