Dear AFNI nation,
I realize that 3dNWarpApply can consume large amounts of memory (70GB before a long beach volleyball stint) when there little overlap between source and grid datasets.
If I understand correctly, the problem can be remedied by centering the volumes before computing the warp, which means rerunning a whole lot of alignments. Is there a way to account for the shifts
after the warps have been estimated?
Specifically for my case, I have 4 spaces I am working with A, B, B
MNI, and C. I have an affine transform from B to A, and a NL transform from B to C. Origins of A and B can vary wildly.
My 3dNwarpApply command strings together B
MNI2C_NL, B2B
MNI_affine, and INV(B2A_affine) to take A data into C space. I suspect the answer is no, but can you think of any tricks I can do to already computed transforms to enable warping of A to C without a lot of memory use and without having to rerun 3dQwarp?
Cheers,
Z
