Closed drammock closed 5 days ago
Hello! π Thanks for opening your first issue here! β€οΈ We will try to get back to you soon. π΄π½ββοΈ
OK, more details: this is a test run using just 2 of the ~50 subjects I have. In fact for now I've only written 2 of the subjs into the BIDS folder tree. Here's the tree:
Here's the part of my preparatory script where the Raw data files (and associated ERMs) are written with MNE-BIDS:
As you can see, empty_room
is always passed, and just to be sure I (locally) stuck an assert erm is not None
into that script and re-ran it, and it succeeds.
I checked the *scans.tsv
files to make sure the dates match the sub-emptyroom
folders/files (they do):
Here is the full pipeline log:
the emptyroommatch
files seem to only exist for session a:
$ find bids-data/ -name "*emptyroommatch*"
bids-data/derivatives/mne-bids-pipeline/sub-116/ses-a/meg/sub-116_ses-a_task-AmplitudeModulatedTones_emptyroommatch.json
bids-data/derivatives/mne-bids-pipeline/sub-215/ses-a/meg/sub-215_ses-a_task-AmplitudeModulatedTones_emptyroommatch.json
Here's the config file: https://github.com/ilabsbrainteam/badbaby-redux/blob/main/pipeline/amtone.py
Any ideas what might be going wrong?
forgot to mention: this is with version 1.9.0 (stable) installed on the workstation (not current main
)
still hitting this, though I've found a fix in #976. Meanwhile, contrary to my comment in https://github.com/mne-tools/mne-bids-pipeline/issues/967#issuecomment-2253524228:
when running with an editable install of MBP, the --debug flag does indeed drop me into a postmortem debugger on error. Not sure why that wasn't working with a standard (conda-forge) install of 1.9.0
in fact today with an editable install I'm once again not getting a debug prompt no matter where I stick in an assert False
or raise RuntimeError
, even though I was getting one previously when debugging #967. I'm running editable installs of current main of MNE, MNE-BIDS, and MNE-BIDS-Pipeline. I really have no clue what has changed π
I'm running editable installs of current main of MNE, MNE-BIDS, and MNE-BIDS-Pipeline. I really have no clue what has changed π
Is this in a plain Linux terminal or VSCode terminal? If VSCode I would verify in a plain Linux terminal just to rule out any VSCode-specific stuff
Sorry that this issue is a bit cursory, it's the end of the work week; I'll add more details when I can.
In my config I have
sessions = ["a", "b", "c"]
. Running the pipeline (in debug mode, so n_jobs=1), the init steps run fine and preprocessing 1 (data quality) runs for session a but chokes when it reaches session b --- it fails to find...emptyroommatch.json
. I've seen #740 but either this issue is different or the fix in #742 didn't actually work, not sure yet.If I then run the pipeline again but add
--session b
to the command line, suddenly it runs fine (all the way through data quality and on to head pos, before I quit out of the run).