-
Notifications
You must be signed in to change notification settings - Fork 298
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
Error with select_tpl workflow step in fmriprep_20.2.6 #2683
Comments
hi @switt4, sorry for the delay - can you post the contents of the crashfile located at |
Hi, Below is the contents of the crashfile related to the
|
Looks like a bug in the resource monitor. I'd suggest removing |
I'll give that a go later this week. Our CLI for fMRIPrep is fixed for the HCP system I am running on, so I'll need to create a new test one. Thanks! |
I just wanted to post an update that removing |
Similar issue with fmriprep_20.2.7 which also goes away with removing of --resource-monitor from the CLI. However, in future I would like to use --resource-monitor. So I thought I would add it here. Several crash files log this error: Crash file in: output/fmriprep/logs/crash-20220218-175632-nikhil-fsdir_run_20220218_175403_305f94ca_22b3_4da7_8001_1947608913a2-2d4563fa-6d2a-4720-9a5b-0539232c31b3.txt
|
What happened?
Hi,
I posted this to neurostars, but I've not received any response, so I'll try here.
We recently downloaded fmrirep_20.2.6 and cannot get it to run due to an error early on with the select_tpl workflow step. From the traceback error it appears as if the command is expecting one value but is being given two.
The input dataset was collected on a 7T using the UMinn single-echo multiplex EPI sequence.
We do not get this error with fmriprep_20.2.5. Has something changed with template flow that we missed and need to update on our end?
Thanks,
Suzanne
What command did you use?
What version of fMRIPrep are you running?
fmriprep_20.2.6
How are you running fMRIPrep?
Singularity
Is your data BIDS valid?
Yes
Are you reusing any previously computed results?
No
Please copy and paste any relevant log output.
Additional information / screenshots
We on running on a HPC system that uses SLURM, so apologies for the somewhat convoluted command.
The text was updated successfully, but these errors were encountered: