API: mne.preprocessing.mark_flat --> mne.preprocessing.annotate_flat ?
See original GitHub issueWith the relatively new Annotations in MNE, there are now (at least) two functions that work on raw data and return annotations:
There is an older function operating in a similar style: mne.preprocessing.mark_flat
Would it make sense to change this to mne.preprocessing.anotate_flat
to have a set of functions with a consistent API working on raw data and providing annotations?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:23 (23 by maintainers)
Top Results From Across the Web
mne.preprocessing.annotate_movement - MNE-Python
Detects segments periods further from rotation_velocity_limit, translation_velocity_limit and mean_distance_limit. It returns an annotation with ...
Read more >mne.preprocessing.compute_current_source_density returns ...
MNE version: 1.1.1 Hi, I've just converted some monopolar EEG data (in Volts) to CSD using mne.preprocessing.compute_current_source_density, ...
Read more >Import and export data to and from MNE-Python
We cannot assure that the API in MNE-Python will remain the same in the ... use this preprocessed data to create ERP (ft_datatype_timelock)....
Read more >Artifact Correction with ICA - | notebook.community
Epochs object around blink or heartbeat events. ICA is implemented in MNE using the :class: mne.preprocessing.ICA class, which we will review here.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
(if someone calls
mark_flat
in 0.21 it should do the same thing as in 0.20 but give dep warning,annotate_flat
should do whatever we wantannotate_*
functions to do)Agreed; I think that was part of @sappelhoff’s original proposal.