Fmriprep No BOLD images found for participant

oesteban · August 14, 2018, 7:35pm

Thanks, that clarifies that fMRIPrep is misreading the BIDS query. I have opened https://github.com/poldracklab/fmriprep/issues/1251. Please follow up there.

hjung · August 14, 2018, 7:44pm

Thank you! Appreciate all your help.

hjung · August 27, 2018, 9:49pm

Would it be a problem to use fmriprep 1.0.4 in the meantime while the bug is fixed? Or should I wait and use the most latest version?
(Just in case, below are the additional options that I’m using in fmriprep)
–use-aroma
–write-graph
–ignore fieldmaps
–fs-no-reconall

effigies · November 7, 2018, 10:01pm

Hi, sorry about the delay. I looked into this. The problem is that your dataset path has an special name in it (sourcedata) that is excluded from indexing. We can look into the best way to improve the exclusion rules, but renaming your directory would be the quickest fix.

dae · November 17, 2018, 5:01am

Thanks for clarifying this. It had me hung up too. The BIDS spec led me to believe that I should have the input nifti in a directory named sourcedata (and that file structure wasn’t an issue in earlier versions of fmriprep). Throwing a warning might help other people.

effigies · November 17, 2018, 2:17pm

No. sourcedata is for files you used to generate your BIDS directory, for example, the raw DICOM files off of your scanner, or subject recordings that you turn into reaction time or response categorical variables for events.tsv, or similar. The BIDS directory itself has no particular requirements to its path. So strictly speaking it’s not wrong to have sourcedata in your path, but right now fMRIPrep can’t handle it.

Incidentally, you can make wording suggestions to the BIDS specification to help us make this clearer:

github.com

bids-standard/bids-specification/blob/b519a65e878c9484c9a93b5372fe638e462dc6a9/src/02-common-principles.md#sourcevs-raw-vs-derived-data

# Common principles

## Definitions

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in [[RFC2119](https://www.ietf.org/rfc/rfc2119.txt)].

Throughout this protocol we use a list of terms. To avoid misunderstanding we
clarify them here.

1.  Dataset - a set of neuroimaging and behavioural data acquired for a purpose
    of a particular study. A dataset consists of data acquired from one or more
    subjects, possibly from multiple sessions.

1.  Subject - a person or animal participating in the study.

1.  Session - a logical grouping of neuroimaging and behavioural data consistent
    across subjects. Session can (but doesn't have to) be synonymous to a visit
    in a longitudinal study. In general, subjects will stay in the scanner

This file has been truncated. show original

This change was in response to other issues, where people put their derivatives directly into <bids_dir>/derivatives, which then led to derivatives being indexed as normal; because <bids_dir>/derivatives/ and <bids_dir>/sourcedata/. While these are valid directories, they’re not where files to be preprocessed should be placed, so we ignored them. Unfortunately, that uses a regular expression, which is hard to make more specific. The next release of pybids should have this feature built in, and I’ve added tests to ensure that it won’t be affected by your path.