mne-tools / mne-tools/mne-python
How to handle untested file versions with read raw body?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 1.6k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 100
Description
On the discourse forum a user has tried to load data with the read_raw_boxy function using a version of data that we haven't tested.
https://mne.discourse.group/t/error-using-mne-for-fnirs-boxy-data/3247
Currently this throws an error. Should we change this to a warning? And ask users to report to us if it's working correctly and maybe contribute test data?
I'm happy to make the change if that's what we should do.
Contributor guide
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 read_raw_boxy entry point and review the linked Discourse report to understand the failure for untested file versions. Decide and document the intended behavior, then add or update coverage for that behavior; the issue names no specific source file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100