I have been having troubles to use the warp fields provided with the second dHCP release. For instance, when using applywarp to register the T1w images to the 40wk GA template image:
I’ve started looking into this from the struct pipeline point of view.
I also see the problem with this example. I’ve tried FSL5, FSL6 and different versions of the atlas, and the origin always ends up in the wrong place (as you say).
I’m currently rerunning the pipeline for this subject so I can see all of the temporary files. Hopefully I can then trace back and see at what point the error occurs.
Just to clarify your previous response:
The functional pipeline’s file sub- ses- from-T2w to-template40wk mode-image.nii.gz is not necessarily the same as the file in the structural pipeline, and they might be different?
And another question about this file:
This transformation (in either functional or structural pipeline) is not a straight transformation from native space to 40W, and it’s equivalent to a transformation from native space to subject’s age_template, followed by a transformation from the subject’s age_template to 40W template. Is that correct?
I will leave the first question to @seanfitz but I can answer the second. Yes, the align_to_template script at @EmmaR’s GitHub here first registers the native subject surface to a local template. Then using wb_command -surface-sphere-project-unproject, the subject surface in local template space is registered to the 40-week template. I should state that this is only for the warps available as part of the third release only.
The warp in the structural pipeline is named xfm/sub-{subid}_ses-{sesid}_from-T2w_to-serag40wk_mode-image.nii.gz and it aligns the native T2w space with the Serag atlas:
The warp in the functional pipeline is named sub-*_ses-*_from-T2w_to-extdhcp40wk_mode-image.nii.gz and it aligns the native T2w space with the extended dHCP volumetric atlas:
