Closed jdkent closed 6 years ago
At first glance, your data configuration file appears to be correct and appears to match the file structure you listed. To quickly make BIDS work with CPAC, we store the session information in the "unique_id" field of the data configuration dictionary. I am extremely confused about the '+fmriprep' being added to your subject name. I think that it is something to do with the '--participant_label' flag, which may be one of the least tested aspects of that code. Would you try using '--participant_index' instead with either 0 or 1?
BTW, I know that it is not well advertised, but you can download the latest version of the cpac bids app singularity image from here: https://fcp-indi.s3.amazonaws.com/resources/singularity_images/bids_cpac/bids_cpac_latest.img
on further thought, i don't know how the --participant_label flag could result in the error you are seeing, i will check it more in depth and see if I can figure out what is happening.
Thank you! I tried the singularity container you provided and got further in the analysis, when I find time I will dig into what the differences between our singularity containers are and hopefully pin down this issue. Now I'm having another issue, but it's much more tractable. I'll open that one separately.
Thanks for adding this BIDS-App, we are excited to get it working.
BACKGROUND I'm trying to get this working on our cluster which has singularity (v2.2.1) installed. I've built the singularity image today (after 3/4 of the commits applied today to this repository), and it appears to start running okay, but after an hour or so errors out.
QUESTION Why does CPAC think my subject label is fmriprep+controlGE140 when it's actually controlGE140 and my session label is 1 when it's actually "pre" or "post"?
This is the test-job script for our SGE cluster:
This is stdout (minus the bids-validation):
This is the stderr:
This is data config yml that was generated
This is the pipeline config that was generated:
and this is how the example subject is organized:
There are a couple top level json files too in the BIDS directory:
fieldmap.json
task-flanker_bold.json
task-rest_bold.json
POSSIBLY RELEVANT I see that the session variable gets defined in bids_utils.py, but I can't readily parse how f_dict you pull bids session information.