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

--skip-bids-validation not skipping all bids validation #342

Open
caugolm opened this issue Nov 9, 2023 · 5 comments
Open

--skip-bids-validation not skipping all bids validation #342

caugolm opened this issue Nov 9, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@caugolm
Copy link

caugolm commented Nov 9, 2023

Summary

ASLPrep is exiting with a BIDS validation error even when using the "--skip_bids_validation" or "--skip-bids-validation" options at submission.

Additional details

  • ASLPrep version: 0.6.0rc1
  • Singularity version: 3.8.3

What were you trying to do?

I had a bunch of pCASL data processed using ASLPrep 0.2.8 that had "ok" results. I updated to 0.6.0rc1 to try reprocessing some data to see if I saw any improvements. I wanted to use the same command to best compare across versions.

What did you expect to happen?

I expected similar results, with likely some improvements.

What actually happened?

No output, just logs with error messages about BIDS validation.

Reproducing the bug

# LSBATCH: User input
singularity run -e -B /input/gfapprelim/:/whatever/gfapprelim/,/input/templateflow-d259ce39a/:/templateflow /input/pmacsPreps-0.2.3/containers/aslprep-0.6.0rc1.simg /whatever/gfapprelim//squids /whatever/gfapprelim//squids_aslprepout-0.6.0rc1 participant --participant_label sub01xxses01 --nprocs 2 --mem 40GB -w /whatever/gfapprelim//squids_wrkdir-0.6.0rc1 --skip-bids-validation --basil --scorescrub --output-spaces T1w asl MNI152NLin2009cAsym:res-2

Traceback (most recent call last):
File "/usr/local/miniconda/bin/aslprep", line 8, in
sys.exit(main())
File "/usr/local/miniconda/lib/python3.9/site-packages/aslprep/cli/run.py", line 18, in main
parse_args()
File "/usr/local/miniconda/lib/python3.9/site-packages/aslprep/cli/parser.py", line 509, in parse_args
config.from_dict(vars(opts))
File "/usr/local/miniconda/lib/python3.9/site-packages/aslprep/config.py", line 566, in from_dict
execution.load(settings)
File "/usr/local/miniconda/lib/python3.9/site-packages/aslprep/config.py", line 187, in load
cls.init()
File "/usr/local/miniconda/lib/python3.9/site-packages/aslprep/config.py", line 409, in init
cls._layout = BIDSLayout(
File "/usr/local/miniconda/lib/python3.9/site-packages/bids/layout/layout.py", line 135, in init
root, description = validate_root(root, validate)
File "/usr/local/miniconda/lib/python3.9/site-packages/bids/layout/validation.py", line 75, in validate_root
raise BIDSValidationError(
bids.exceptions.BIDSValidationError: 'dataset_description.json' is missing from project root. Every valid BIDS dataset must have this file.
Example contents of 'dataset_description.json':
{"Name": "Example dataset", "BIDSVersion": "1.0.2"}

@caugolm caugolm added the bug Something isn't working label Nov 9, 2023
@tsalo
Copy link
Member

tsalo commented Nov 9, 2023

Can you share the tree for your dataset?

@caugolm
Copy link
Author

caugolm commented Nov 9, 2023

I had to make a "pseudo-BIDS" directory to get my data processed correctly using 0.2.8, and with the "--skip-bids-validation" flag I had not needed the dataset_description.json at all. With the 0.6.0rc1 it looks like it checks for the dataset_description.json regardless of the flag. But, I just created a dummy dataset_description.json file that contained the example contents ( {"Name": "Example dataset", "BIDSVersion": "1.0.2"} ) in my "pseudo-BIDS" directory ("/input/gfapprelim/squids/", in my command above) and things seem to be running now!

@tsalo
Copy link
Member

tsalo commented Nov 9, 2023

That's good to hear. It appears that pybids has some requirements, even when validation is disabled.

@caugolm
Copy link
Author

caugolm commented Nov 9, 2023

Fair enough. Feel free to close unless you have any reason to look into this further

@tsalo
Copy link
Member

tsalo commented Nov 14, 2023

I think it's worth at least improving the documentation a bit, so I'll keep this open until I've had a chance to update that.

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