History of AFNI updates  

|
June 04, 2019 12:00PM
Hi AFNI Experts,
I'm using AFNI's latest linux_openmp64 binary (19.1.08 'Caligula'). I ran a warp field at minpatch 11 and later used that warp field as an iniwarp parameter in 3dQwarp (via auto_warp.py by specifying options). My commands are registered and the output notes reflect all parameters were passed without issue.

3dQwarp -prefix anat.rw.qw ./anat.rw.qw.nii -inilev 9 -minpatch 7 -iniwarp /home/projects/TEST/test001/anat.rw.qw_WARP.nii -base ./base.rw.nii -source ./anat.rw.nii

It ran Lev9 - minpatch 13x17x13 Start cost 3.0602 -->End cost 1.0543
Then Lev10 - minpatch 11x11x11 Start cost 1.0543 --> .46729


The warp stops here and saves out even though it did not get to 7mm patch. Is there a minimum cost function value that supercedes going to the next level (ie if .46729 is low enough it autostops short of the patch size) or is there something else potentially wrong or is the problem that if I use an initial warp field that it cannot optimize that more than the level the initial warp was created on?


I also tried inilev 10 and 11 and no difference...still stops early. Any help would be much appreciated.


Thanks,
Ajay
Subject Author Posted

3dQwarp -minpatch stops short of value

AjaySK June 04, 2019 12:00PM

Re: 3dQwarp -minpatch stops short of value

AjaySK June 04, 2019 05:57PM

Re: 3dQwarp -minpatch stops short of value

RWCox June 05, 2019 04:51AM

Re: 3dQwarp -minpatch stops short of value

RWCox June 05, 2019 09:31AM

Re: 3dQwarp -minpatch stops short of value

AjaySK June 05, 2019 12:36PM

Re: 3dQwarp -minpatch stops short of value

ptaylor June 06, 2019 02:43AM