Skip to content
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

cubids apply renaming variants bug #425

Open
B-Sevchik opened this issue Feb 5, 2025 · 1 comment
Open

cubids apply renaming variants bug #425

B-Sevchik opened this issue Feb 5, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@B-Sevchik
Copy link
Contributor

B-Sevchik commented Feb 5, 2025

Summary

Running cubids apply is not re-naming variants explicitly for the fmap variants.
Case where cubids failed:
original name of entity set: acquisition-dwi_datatype-fmap_direction-AP_fmap-epi_run-01_suffix-epi; acquisition-dwi_datatype-fmap_direction-PA_fmap-epi_run-01_suffix-epi; acquisition-fmri_datatype-fmap_direction-AP_fmap-epi_run-01_suffix-epi; acquisition-fmri_datatype-fmap_direction-PA_fmap-epi_run-01_suffix-epi
suggested new name entity set: acquisition-dwiVARIANTObliquity_datatype-fmap_direction-AP_fmap-epi_run-01_suffix-epi; acquisition-dwiVARIANTObliquity_datatype-fmap_direction-PA_fmap-epi_run-01_suffix-epi; acquisition-fmriVARIANTObliquity_datatype-fmap_direction-AP_fmap-epi_run-01_suffix-epi; acquisition-fmriVARIANTObliquity_datatype-fmap_direction-PA_fmap-epi_run-01_suffix-epi
original name of file example: /sub-20812/ses-3/fmap/sub-20812_ses-3_acq-dwi_dir-AP_run-01_epi.nii.gz
suggested rename of file example: /sub-20812/ses-3/fmap/sub-20812_ses-3_acq-VARIANTObliquity_dwi_dir-AP_run-01_epi.nii.gz

Additional details

  • CuBIDS version: 1.1.1.dev137+g89792af
  • Datalad version: datalad 1.1.5

What were you trying to do?

I was trying to re-name the fmap variants according to the suggested rename in the summary tsv file.

What did you expect to happen?

I expected that running cubids apply would successfully re-name the fmap variants, and the new summary tsv file that would be produced would not have any suggested renames, but rather the variant re-name would show up successfully in the new KeyParamGroup and EntitySet columns.

What actually happened?

Running cubids apply did not change the names of the fmap scans, and the suggested rename is still in RenameEntitySet column.

Reproducing the bug

cd /cbica/projects/executive_function/data/bids/
/cbica/projects/executive_function/miniforge3/envs/cubids/bin/cubids apply /cbica/projects/executive_function/data/bids/EF_bids_data_DataLad /cbica/projects/executive_function/data/bids/EF_bids_data_DataLad/code/CuBIDS/v24_edited_summary.tsv /cbica/projects/executive_function/data/bids/EF_bids_data_DataLad/code/CuBIDS/v24_files.tsv v25 

command above is from cubids_apply.sh, the script that submits cubids apply to be run as a job on cubic

@B-Sevchik B-Sevchik added the bug Something isn't working label Feb 5, 2025
@tsalo
Copy link
Member

tsalo commented Feb 5, 2025

Under "Reproducing the bug", can you replace your script with the cubids apply command in the script?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants