help > RE: The order of "slice-timing-correction".
Oct 11, 2022  09:10 PM | Alfonso Nieto-Castanon - Boston University
RE: The order of "slice-timing-correction".
Hi

You are right the order of slice-timing correction (vs. realignment) is a debated topic. In general the recommendation is to apply first the one that you believe might have affected the data the most (e.g. for very long TRs perhaps you would apply slice-timing correction first, while for high-motion cases perhaps you would apply realignment first). The order of the default pipeline in CONN is simply trying to capture perhaps the most common scenario for connectivity analyses, where motion may be a higher concern than intra-scan timing differences, but of course you are encouraged to check and change if necessary the order of the elements in the pipeline (e.g using the "move up/down" buttons) to better match your dataset characteristics before running preprocessing

Hope this helps
Alfonso
Originally posted by tomoki kaneko:
Hi, there.

We use Siemens Prisma (3T).
In the default processing pipeline, the slice-timing-correction is next process to the realignment. As for the interleaved sequence, I think that slice-timing should be done first so as not to contain the variable time information in resliced image. Or, does conn change the order depending on the slice order ?

Sincerely

Threaded View

TitleAuthorDate
tomoki kaneko Oct 10, 2022
RE: The order of "slice-timing-correction".
Alfonso Nieto-Castanon Oct 11, 2022
tomoki kaneko Oct 12, 2022