Open suxpert opened 2 weeks ago
Hi @suxpert, thanks for reaching out.
C-PAC correctly applied slice timing correction and go without further issue
It looks like your data data has the slice-timing info in the sidecar, but it’s either missing from the header or on a different axis than expected. Since fmriprep gets the slicetiming from the sidecar and you already have it in the sidecar, you can
FROM: preproc
functional_preproc:
slice_timing_correction:
tpattern: path/to/that/tpattern/file.txt
C-PAC accept turning off slice timing correction from command line rather than edit the terrified pipeline config files (which is hard for me because it is too complex for beginners and without detailed documents)
A pipeline config like this should run the preproc preconfig minus slice timing correction:
FROM: preproc
functional_preproc:
slice_timing_correction:
run: Off
There is documentation here for making small changes to a configuration and here for slice-timing settings. Looking at the slice-timing docs, it looks like instead of putting the tpattern file in the pipeline config, you could make that file and put its path in the “Acquisition” column of your scan_parameters.csv
or scan_parameters_multiscan.csv
file.
Note: Scan parameter information specified for slice timing correction will override the settings specified in the pipeline configuration YAML.
Hopefully some of this helps with the issue you are having. It would also be helpful for us to know know what your expectations are for the CLI and documentation here, specifically. Any additional information helps us make improvements to C-PAC!
slice-timing correction
turned off (as a workaround).3dTshift
is number mismatch, where I have only 66 slices but it requires 96, i.e, on a different axis than expected
.
** FATAL ERROR: tpattern file /..../tpattern.txt has 66 values but have 96 slices
I regard the config file as terrified
since it:
toml
et al., since yaml
use indent for hierarchy, but too many levels;nested
according to the document), such a tree (or forest) makes me easily lost.Web-based Graphics UI
, I entered here, clicked at the duplicate
, then view/edit
, then the only things that I can do is to rename the duplicated config, or modify the from
tab by entering new text, all other tabs are empty.Hi @suxpert,
Thank you for the update. If specifying the tpattern in the following ways has not resolved this issue, we can replicate on our end and get back to you with some more information. Specifying your intended use case, if you are able, will also help us do this!
in config file
FROM: preproc
functional_preproc:
slice_timing_correction:
tpattern: path/to/that/tpattern/file.txt
make that file and put its path in the “Acquisition” column of your scan_parameters.csv
or scan_parameters_multiscan.csv
file
Here is some additional information relating to C-PAC configuration:
FROM: /path/to/pipeline.yml
in your pipeline configuration file.
Describe the bug
I have some functional data which covers only half of the brain, and with slice setting to almost perpendicular to
anterior-posterior
, i.e., coronal slices.fmriprep
works fine for this data, and because I failed runC-PAC
on top of fmriprep's result, I tried with the raw data in BIDS. Still without any lucky,C-PAC
failed with following errors:1700 might be the same issue, but 2 years have passed without further update.
To reproduce
No response
Preconfig
Custom pipeline configuration
No response
Run command
Expected behavior
I would expect the preproc pipeline be able to run successfully since this is very simple BIDS dataset that has been validated via
bida-validator
and is nothing wrong forfmriprep
.Acceptance criteria
Screenshots
Here are crash and log files:
C-PAC version
v1.8.7
Container platform
Docker
Docker and/or Singularity version(s)
Docker version 26.1.5-ce
Additional context