mne-tools / mne-tools/mne-python
separate verbose options for compute_psd and joblib
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 1.6k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 100
Description
Describe the new feature or enhancement
Add the option to control the verbosity of joblib without affecting the verbosity of joblib. See discussion here:
https://mne.discourse.group/t/remove-output-from-joblib/7303
Describe your proposed implementation
Proposed by @drammock and @larsoner:
one reasonable approach might be a config value (MNE_JOBLIB_LOGGING_LEVEL or so) that can be set separately from the global logging level.
Sounds good to me. We could add it to set_log_level and use_log_level, and have the default joblib_verbose=None mean “use the verbose level” (which would preserve backward compat)
Copied from:
https://mne.discourse.group/t/remove-output-from-joblib/7303
Describe possible alternatives
N/A
Additional context
No response
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 by reviewing the linked Discourse discussion and the proposed changes to set_log_level and use_log_level. Trace how compute_psd currently controls joblib verbosity and how the global logging level is applied. Done means joblib verbosity can be configured independently while the default joblib_verbose=None preserves backward compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100