Document (or align) which clean_rawdata steps mutate their input
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation
Research direction
Read the docstrings for clean_drifts, clean_flatlines, clean_channels, clean_channels_nolocs, and clean_windows; the issue reports their input mutation and copy behavior. Check whether the existing documentation already states what happens to the input, then update each docstring to describe the observed behavior. Done when callers can tell from each docstring whether the input is mutated or copied.
Written by the indexing model from the issue text.
Description
Measured on eegprep 0.5.0 by comparing a hash of the data and the keys of etc before and after each call:
| function | behaviour |
|---|---|
clean_drifts |
mutates its input in place (data and etc) and returns the same object |
clean_flatlines |
returns the same object when nothing is removed, a new one otherwise |
clean_channels, clean_channels_nolocs |
same as clean_flatlines |
clean_windows |
deep-copies and leaves its input untouched |
pop_eegfiltnew, pop_select |
copy |
A caller that keeps the original around must know this.
Expected: state it in each docstring, ideally copy consistently.
- Dominant language
- Python
- Stars
- 38
- Forks
- 7
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 65
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from sccn/eegprep
-
fuzz fuzz-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
clean_channels: raise on degenerate channel locations instead of returning a meaningless resultOpen
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
sccn/eegprep#539 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
sccn/eegprep#533 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Remove the `pull_request_target` workflow before GitHub blocks itPossibly taken @jat255 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
IBM/mcp-context-forge#7483 ·
Maintainers usually reply within 2 days
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
[Bug Report]: OpenAI 辅助 API 连通性测试因输出上限仅 1 token 误报“未知错误”Possibly taken @fjfanjian claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Project-N-E-K-O/N.E.K.O#3640 ·
Maintainers usually reply within 1 day
-
author-page correction
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
acl-org/acl-anthology#10808 · 1 comment ·
Maintainers usually reply within 1 day