-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix report section on original raw data (didn't contain bad channels and subject or experimenter name) #931
Fix report section on original raw data (didn't contain bad channels and subject or experimenter name) #931
Conversation
…and subject or experimenter name) Fixes mne-tools#930
@larsoner This seems to fix my problem I only have one question Should we only set the pre-existing bads when generating the HTML repr for the original data, or should we set the pre-existing bads + all bads from the data quality checks? Either approach seems to have its up- and downsides. |
@@ -848,9 +848,9 @@ def _add_raw( | |||
cfg: SimpleNamespace, | |||
report: mne.report.Report, | |||
bids_path_in: BIDSPath, | |||
raw: BaseRaw, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change should avoid the problem we saw here, as it now forces us to provide pre-loaded raw data (with hopefully the correct metadata set). previously this was optional. see also the changes below
Circle fails for ds000246 due to outdated cache |
I'll fix the caches in #929 |
Thank you! |
To me the optimal thing to do here I think is to have two report entries:
To me it's okay for brevity to have (1) have all the nice raw data plots, and have (2) maybe have less -- like just a list of channels removed or something? I think we're already kind of close to this organization: But from that data quality plot it's not immediately clear which channels were added as bad, if any. Even just a HTML entry that lists the bads (when bad enabled) and flats (when flat enabled) would be a nice help |
... and organizationally I think it might make sense to call that section in the sidebar |
Thanks for sharing your ideas, they resonate well with me! I believe then at least the bits of code that this PR touches should be good! And the rest could be addressed in future PRs I will add a changelog entry and once CI passes, we should be good to go. |
I merged |
Thanks @larsoner, I pushed changelog entries and enabled auto-merge |
Fixes #930
Before merging …
docs/source/changes.md
)