AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

|
July 02, 2021 04:19PM
Hi AFNI Experts,
I am using 3dQwarp and for most subjects it runs fine but I had a handful that would fail. Below is the error I am seeing. My guess is that the start and stop cost are close enough for the patch that it triggers a fail but that is just my hypothesis. This error is on AFNI_21.1.20 and 20.0.18

3dQwarp -prefix ./anat.rw.qw.nii -workhard:0:1 \
-penfac 1 \
-maxlev 4 \
-pblur 0.01 0.01 \
-plusminus \
-pmBASE \
-iniwarp ./anat.rw.qw_MINUS_WARP.nii \
-base ./base.rw.nii -source ./anat.rw.nii
++ OpenMP thread count = 15
++ 3dQwarp: AFNI version=AFNI_21.1.20 (Jun 28 2021) [64-bit]
++ Authored by: Zhark the (Hermite) Cubically Warped
++ Dataset final zero-pad: xbot=3 xtop=3 ybot=3 ytop=3 zbot=19 ztop=14 voxels
+ Extended/padded iniwarp to match base volume: 3 3 3 3 7 7 voxels
++ Weightizing the base image: FWHM = 3 (vox)

++ +++++++++++ Begin warp optimization: base=base.rw.nii
source=anat.rw.nii
++ AFNI warpomatic start: 262 x 262 x 177 volume ; autobbox = 72..198 53..220 23..153
lev=0 57..213 33..240 7..169: [first cost=-0.74783] ...... done [cost=-0.76237]
lev=1 patch=117x155x123: :[cost=-0.76237]:[first cost=-0.75333]
Fatal Signal 11 (SIGSEGV) received
IW3D_improve_warp
IW3D_warpomatic_plusminus
IW3D_warp_s2bim_plusminus
3dQwarp
Bottom of Debug Stack


Any insights would be helpful. If there cost function stopping criteria is the issue is there a way to gracefully exit without the error? Can you let me know what the value is for the criteria for stopping if this is indeed the issue. I think on 3dAllineate there is an option :

-conv mmm = Convergence test is set to 'mmm' millimeters.
This doesn't mean that the results will be accurate
to 'mmm' millimeters! It just means that the program
stops trying to improve the alignment when the optimizer
(NEWUOA) reports it has narrowed the search radius
down to this level.
* To set this value to the smallest allowable, use '-conv 0'.
* A coarser value for 'quick-and-dirty' alignment is 0.05.


Best,
Ajay



Edited 2 time(s). Last edit at 07/07/2021 03:31PM by AjaySK.
Subject Author Posted

3dQwarp crash (stopping criteria? )

AjaySK July 02, 2021 04:19PM

Re: 3dQwarp crash (stopping criteria? )

AjaySK July 07, 2021 03:30PM

Re: 3dQwarp crash (stopping criteria? )

RWCox July 09, 2021 11:23AM

Re: 3dQwarp crash (stopping criteria? )

AjaySK July 14, 2021 12:46AM

Re: 3dQwarp crash (stopping criteria? )

RWCox July 16, 2021 03:12PM