-
Notifications
You must be signed in to change notification settings - Fork 67
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 handling of analyze_channels
for EEG data, where some steps (like ERP calculation) would previously fail
#883
Conversation
…e ERP calculation) would previously fail This was reported at https://mne.discourse.group/t/error-when-setting-analyze-channels-using-mne-bids-pipeline
analyze_channels
for EEG data, where some steps (like ERP calculation) would previously failanalyze_channels
for EEG data, where some steps (like ERP calculation) would previously fail
For stuff like this as much as possible I still try to follow TDD and modify an example/test config to show the problem. Maybe one of the
And it looks like
So we should probably add it here. @hoechenberger feel free to try it on |
@larsoner Yes absolutely, I forgot to mention that I was actually planning to add a test case I will do that when I have time; changing to a draft PR now! |
eeg_reference = "average" | ||
# Analyze all EEG channels -- we only specify the channels here for the purpose of | ||
# demonstration | ||
analyze_channels = [ |
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.
test with average reference
eeg_reference = ["P9", "P10"] | ||
# Analyze all EEG channels -- we only specify the channels here for the purpose of | ||
# demonstration | ||
analyze_channels = [ |
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.
test with custom reference
@larsoner Both, N170 and N2pc, fail to run on |
Marking for merge-when-green, thanks @hoechenberger ! |
@larsoner Think we can cut a 1.7 release with this? |
Sure or a 1.6.1 |
@larsoner I tagged a new release but the doc deployment is failing :( https://app.circleci.com/pipelines/github/mne-tools/mne-bids-pipeline/4328/workflows/045c8d95-d657-4020-9ecf-71c00f53e2d9/jobs/60266/parallel-runs/0/steps/0-109 |
Looks like:
one solution is to archive or just remove some old doc versions like 1.0, 1.1, etc. |
@hoechenberger WDYT about deleting 1.0 and 1.1? |
I'm also fine with keeping only the last 2 or 3 releases + dev :) |
FYI to fix things I re-ran the failed step with SSH (though I guess I could have done it locally), then SSH'ed in and did: $ source $BASH_ENV
$ cd project
$ git checkout main # was on gh-pages
$ mike list --config-file docs/mkdocs.yml
Generating option->step mapping: 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████| 56/56 [00:00<00:00, 228.61it/s]
warning: gh-pages is unrelated to origin/gh-pages
dev
1.7 [stable]
1.6
1.5
1.4
1.3
1.2
1.1
1.0
$ mike delete 1.0 --config-file docs/mkdocs.yml --ignore-remote-status
... # same for 1.1, 1.2, 1.3, and 1.4
$ git checkout gh-pages
$ git reset $(git commit-tree HEAD^{tree} -m "Deploy and squash docs [ci skip]")
$ git push origin --force gh-pages
...
Writing objects: 100% (1041/1041), 1.88 GiB | 70.96 MiB/s, done.
...
+ 9988ef4...ad8b0d3 gh-pages -> gh-pages (forced update) and now things look okay: https://mne.tools/mne-bids-pipeline/stable/
Note that we do get this warning in deployment:
So we might have more compression / size reduction to figure out at some point |
This was reported at https://mne.discourse.group/t/error-when-setting-analyze-channels-using-mne-bids-pipeline
Before merging …
docs/source/changes.md
)