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

Add notes about common cuBIDS errors we run into and what they mean #261

Open
LuciMoore opened this issue Dec 9, 2024 · 0 comments
Open

Comments

@LuciMoore
Copy link
Contributor

Here are just a few quick notes, they could use polish and checks for accuracy:

  • BOLD_NOT_4D and NIFTI_PIXDIM4 (usually same subject lists)- for func runs - likely means the func run only has 1 volume. these aren't usable and should be removed from the BIDS inputs
  • INCONSISTENT_PARAMETERS - func runs - sometimes this just means that not all the func runs have the same number of frames for example, which isn't unusual and can be ignored
  • INTENDED_FOR - could mean that the json is missing, the IF field is blank, the file path in the IF field isn't accurate (I believe it should be formatted as ses-XXX/func/run1.nii.gz for example starting at session level), etc
  • PHASE_ENCODING_DIRECTION_MUST_DEFINE & TOTAL_READOUT_TIME_MUST_DEFINE - could either mean that these fields are missing or blank in the jsons, or that the json files themselves are missing
  • VOLUME_COUNT_MISMATCH - I don't remember this one off the top of my head. might mean something is wrong with dwi file and it should be discarded similar to BOLD_NOT_4D for func runs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant