SpikeInterface / SpikeInterface/spikeinterface
Specification of the dtype for Preprocessors
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
I saw a discussion concerning the dtype of the whitening pre-processors, but I just want to highlight that there is some inconsistencies between the pre-processors: some can specify an output dtype (filtering, whitening), and some can not (CAR, artefacts, ...)
Maybe there should be something more abstract and general such that all pre-processors can control the dtype output?
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
The issue names filtering, whitening, CAR, and artefact preprocessors but no files or tests. Start by locating those preprocessor implementations and comparing how each handles output dtype. Done should mean a decided, consistent dtype-control approach across the preprocessors, with its behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100