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
BUG: Reference run not guaranteed to be processed before noise runs #759
Comments
One solution that should work for this would be something like:
where changing to |
Actually I thought this shouldn't happen, as we're injecting the reference run's bass into the empty-room recording: mne-bids-pipeline/mne_bids_pipeline/_import_data.py Lines 458 to 485 in ccbac54
|
I think the error message might be misleading/wrong here. This happens when processing run 01 when the ref run is 03, at least assuming @allermat is on the latest MNE-BIDS-Pipeline as of a week or so ago when I split the individual runs out from the empty-room ones. @allermat can you make sure you're on the latest dev version and double check? Either way I think we should add this Also separately we it looks like the Epochs we create will inherit the mne-bids-pipeline/mne_bids_pipeline/steps/preprocessing/_05_make_epochs.py Lines 287 to 295 in ccbac54
The first run's |
@larsoner I ran this with a slightly older dev version: 1.4.0.dev3+gb0cf4a0. I'll re-run it with the latest and let you know. |
@allermat FYI you might need to clear your cache or |
Thanks, I always delete the derivatives and start from scratch whenever I re-run the pipeline |
Ok, so with the latest dev version (1.5.0.dev3+gccbac54) maxfilter ran without an issue on the subject I had trouble with. I'll re-run this on the whole dataset and report if I have any issues. |
I couldn't test this on all my subjects, but maxfilter seems to run fine now on other subjects as well (at least when I run the pipeline in series, so Whilst testing this I kept getting a weird missing file error whenever I ran the pipeline with The error message is:
|
I think I get it. We assume when processing empty-room and We probably need to fix this by changing the parallelization to be over all non-rest runs, then process the empty room and rest runs (if applicable) afterward. So to summarize I think two changes are needed:
I'll re-title this issue for point (1) and then try to quickly fix the bug. Then I'll open a new issue for (2). |
This has been discussed on the MNE Forum here.
I received an error when running the Maxwell filter step in the MNE-BIDS-Pipeline, saying that the rank of the data in the reference rune does not match the empty room data rank, see below:
This occurred only with a specific subject in the dataset and it has to do with which run I set as reference. If I set mf_reference_run = '03', I get the error, however, if I set mf_reference_run = '01', then the Maxwell filter step runs fine without an error.
The text was updated successfully, but these errors were encountered: