Create fmriprep-GRUHN_v24.1.1.yaml

[duettwe]

No description provided.

[baxpr]

scan_fmri is ERT_1, ERT_2
scan_fmrirpe is topup_GE or whatever it's called
We'll get 2 fmripreps per session.

[duettwe]

Current file is still giving the participant label error, with the 1.6.1 fix...

2025-07-28 08:57:41,653 [ WARNING] WARNING: SOCKS support in urllib3 requires the installation of optional dependencies: specifically, PySocks.  For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#socks-proxies
You are using fMRIPrep-24.1.1, and a newer version of fMRIPrep is available: 25.1.3.
Please check out our documentation about how and when to upgrade:
https://fmriprep.readthedocs.io/en/latest/faq.html#upgrading
Traceback (most recent call last):
  File "/opt/conda/envs/fmriprep/bin/fmriprep", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/opt/conda/envs/fmriprep/lib/python3.11/site-packages/fmriprep/cli/run.py", line 40, in main
    parse_args()
  File "/opt/conda/envs/fmriprep/lib/python3.11/site-packages/fmriprep/cli/parser.py", line 903, in parse_args
    validate_input_dir(
  File "/opt/conda/envs/fmriprep/lib/python3.11/site-packages/fmriprep/utils/bids.py", line 242, in validate_input_dir
    raise RuntimeError(error_msg % ','.join(bad_labels))
RuntimeError: Data for requested participant(s) label(s) not found. Could not find data for participant(s): 1020_4. Please verify the requested participant labels. This error can be caused by the input data not being accessible inside the singularity container. Please make sure all paths are mapped properly (see https://www.sylabs.io/guides/3.0/user-guide/bind_paths_and_mounts.html)
ERROR:missing required output:HTML
ERROR:missing required output:BIDS
JOB_FAILED
DONE!

[baxpr]

Ah - can't use dax's {subject} in the main and post sections, because the subject label gets changed in the pre section. Wasn't there a version you worked on recently where you tweaked things to solve that issue?

[duettwe]

I believe it's this one: #3

Were we supposed to pull that one as well?

[duettwe]

Current version appears to actually be running. So that's something!

[duettwe]

I think this might be the fastest I've ever got a yaml to COMPLETE. Test has completed on v1_261475