You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain BIDS Apps (Such as FreeSurfer and ANTs, for example) run into errors when executed with BABS.
For these two apps (and most of the others listed on the BIDS Apps website) the parameter is --participant_label rather than --participant-label, which I think is producing an error:
'run.py: error: unrecognized arguments: --participant-label sub-01'
Additionally, as far as I can tell from the logs, BABS generates the singularity commands using the --participant-label parameter in the format sub-ID (e.g., sub-01 in our test case), but these two BIDS Apps (and many of the others) state in their GitHub repository README's that this parameter should not include the sub- prefix. The containers won't run if it is included, producing errors, for example
ANTs: 'Exception: No T1w files found for participant sub-01',
FreeSurfer: 'No T1w nii files found for subject sub-01. Skipping subject.'.
I went through the documentation but couldn’t find a way to specify these parameter variations in BABS. It’s totally possible that I’m just overlooking something—maybe this isn’t a bug at all, and is just me being clueless! :)
Let me know if I should be asking this somewhere else instead.
Thanks for your help!!
Additional details
BABS version (pip show babs): 0.0.8
DataLad version (datalad --version): 1.1.5
Git version (git --version): 2.40.1
git-annex version (git-annex version; pasting the first printed line is sufficient): 10.20230926-g44a7b4c9734adfda5912dd82c1aa97c615689f57
datalad-container version (datalad containers-add --version): 1.2.5
Singularity version (singularity --version): apptainer version 1.3.5
Please copy and paste the printed messages from babs-check-setup:
Will check setups of BABS project located at: /home/jacobsr/scratch/other_reruns/babs/my_BABS_project
Did not request `--job-test`; will not submit a test job.
Below is the configuration information saved during `babs-init` in file 'analysis/code/babs_proj_config.yaml':
type_session: single-ses
type_system: slurm
input_ds:
$INPUT_DATASET_#1:
name: dsONtest
path_in: /home/jacobsr/scratch/other_reruns/babs/test_dataset/ds005072
path_data_rel: inputs/data/dsONtest
is_zipped: false
container:
name: antscontainer
path_in: /home/jacobsr/scratch/other_reruns/babs/ANTScont
Checking the BABS project itself...
✓ All good!
Check status of 'analysis' DataLad dataset...
nothing to save, working tree clean
✓ All good!
Checking input dataset(s)...
✓ All good!
Checking container datalad dataset...
✓ All good!
Checking `analysis/code/` folder...
✓ All good!
Checking input and output RIA...
Datalad dataset `analysis`'s siblings:
.: here(+) [git]
.: output(-) [/home/jacobsr/scratch/other_reruns/babs/my_BABS_project/output_ria/f5f/14ebc-c4ee-49b8-a312-a8be0416d7b4 (git)]
.: input(-) [/home/jacobsr/scratch/other_reruns/babs/my_BABS_project/input_ria/f5f/14ebc-c4ee-49b8-a312-a8be0416d7b4 (git)]
.: output-storage(+) [ora]
✓ All good!
Not to submit a test job as it's not requested. We recommend running a test job with `--job-test` if you haven't done so; It will gather setup information in the designated environment and make sure future BABS jobs with current setups will be able to finish successfully.
`babs-check-setup` was successful!
What were you trying to do?
Runs the two aforementioned BIDS Apps on the OpenNeuro dataset ds005072
What did you expect to happen?
I followed the documentation walkthrough steps but instead of the defaults, used the aforementioned OpenNeuro dataset and BIDS App images.
I initialized the project successfully, and successfully launched the jobs on a SLURM HPC (All as expected).
Summary
Certain BIDS Apps (Such as FreeSurfer and ANTs, for example) run into errors when executed with BABS.
For these two apps (and most of the others listed on the BIDS Apps website) the parameter is --participant_label rather than --participant-label, which I think is producing an error:
'run.py: error: unrecognized arguments: --participant-label sub-01'
Additionally, as far as I can tell from the logs, BABS generates the singularity commands using the --participant-label parameter in the format sub-ID (e.g., sub-01 in our test case), but these two BIDS Apps (and many of the others) state in their GitHub repository README's that this parameter should not include the sub- prefix. The containers won't run if it is included, producing errors, for example
ANTs: 'Exception: No T1w files found for participant sub-01',
FreeSurfer: 'No T1w nii files found for subject sub-01. Skipping subject.'.
I went through the documentation but couldn’t find a way to specify these parameter variations in BABS. It’s totally possible that I’m just overlooking something—maybe this isn’t a bug at all, and is just me being clueless! :)
Let me know if I should be asking this somewhere else instead.
Thanks for your help!!
Additional details
pip show babs
): 0.0.8datalad --version
): 1.1.5git --version
): 2.40.1git-annex
version (git-annex version
; pasting the first printed line is sufficient): 10.20230926-g44a7b4c9734adfda5912dd82c1aa97c615689f57datalad-container
version (datalad containers-add --version
): 1.2.5singularity --version
): apptainer version 1.3.5babs-check-setup
:What were you trying to do?
Runs the two aforementioned BIDS Apps on the OpenNeuro dataset ds005072
What did you expect to happen?
I followed the documentation walkthrough steps but instead of the defaults, used the aforementioned OpenNeuro dataset and BIDS App images.
I initialized the project successfully, and successfully launched the jobs on a SLURM HPC (All as expected).
babs-init --where_project ${PWD} --project_name my_BABS_project --input dsONtest /home/jacobsr/scratch/other_reruns/babs/test_dataset/ds005072 --container_ds ${PWD}/ANTScont --container_name antscontainer --container_config_yaml_file ${PWD}/config_antsbidsapp.yaml --type_session single-ses --type_system slurm
The HPC submissions fail after launching (not expected until I saw the participant label mismatches).
What actually happened?
During job execution (babs-submit --project-root $PWD) it fails as described above. Relevant logs from analysis/logs/ant_sub-01.e40202214:
Reproducing the bug
The text was updated successfully, but these errors were encountered: