You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up from #914
Aim: Provide more information from MNE's logging (currently set to 'error' by default) in the pipeline's log: implement
a logging system via rich where the user can expand and collapse entire log sections -- in a separate file?
The text was updated successfully, but these errors were encountered:
In principle Python's logging system, which is used by mne, can have arbitrary handlers attached. So one way to do this would be to
Set the logging level to info or whatever
Remove all existing handlers
Add a custom message handler that took whatever message was logged and hook it into our rich logging system
I think in principle this shouldn't be too bad to do. Could be fun for someone interested in experimenting with rich.
Maybe we could start with trying the rich-collapsible support first, and see if that's enough. Then maybe we don't need a file at all (or | tee <whatever> in the terminal could be good enough for logging mne_bids_pipeline calls).
Follow-up from #914
Aim: Provide more information from MNE's logging (currently set to 'error' by default) in the pipeline's log: implement
a logging system via rich where the user can expand and collapse entire log sections -- in a separate file?
The text was updated successfully, but these errors were encountered: