Open Michael-Sun opened 9 months ago
This issue is caused by a prematurely accessed pybids directory which is created by early iterations in a parallelized batch. Better practice would be to pre-create a pybids directory before invoking bidsmreye in parallel.
Is there an existing issue for this?
Expected Behavior
BidsMReye detects the subject and processes it.
Current Behavior
BIDSLayout cannot seem to find the subject SID001641, despite it being present.
Error message
Environment
Branch
No response
Anything else?
No response