3dNwarpApply fatal signal 11 (SIGSEGV)

AFNI Message Board
1

Hello AFNI gurus,

I am running afni_proc.py on a remote server, and it exited before finishing with the following error:


3dNwarpApply -source s160427_NTD015_2_T1_MEMPRAGE+orig -master anat_final.s160427_NTD015_2+tlrc -ainterp wsinc5 -nwarp anat.un.aff.qw_WARP.nii anat.un.aff.Xat.1D s160427_NTD015_2_T1_MEMPRAGE_al_keep_mat.aff12.1D -prefix anat_w_skull_warped
++ 3dNwarpApply: AFNI version=AFNI_17.0.18 (Mar 29 2017) [64-bit]
++ Authored by: Zhark the Warped
e[7m*+ WARNING:e[0m   If you are performing spatial transformations on an oblique dset, 
  such as ./s160427_NTD015_2_T1_MEMPRAGE+orig.BRIK,
  or viewing/combining it with volumes of differing obliquity,
  you should consider running: 
     3dWarp -deoblique 
  on this and  other oblique datasets in the same session.
 See 3dWarp -help for details.
++ Oblique dataset:./s160427_NTD015_2_T1_MEMPRAGE+orig.BRIK is 15.402659 degrees from plumb.
++ opened source dataset 's160427_NTD015_2_T1_MEMPRAGE+orig'
++ -master dataset is 'anat_final.s160427_NTD015_2+tlrc'
++ Processing -nwarp 
Fatal Signal 11 (SIGSEGV) received
       THD_open_nifti
      THD_open_one_dataset
     THD_open_dataset
    CW_read_dataset_warp
   IW3D_read_nwarp_catlist
  3dNwarpApply
 Bottom of Debug Stack
** Command line was:
3dNwarpApply -source s160427_NTD015_2_T1_MEMPRAGE+orig -master anat_final.s160427_NTD015_2+tlrc -ainterp wsinc5 -nwarp anat.un.aff.qw_WARP.nii anat.un.aff.Xat.1D s160427_NTD015_2_T1_MEMPRAGE_al_keep_mat.aff12.1D -prefix anat_w_skull_warped
** AFNI version = AFNI_17.0.18  Compile date = Mar 29 2017
** [[Precompiled binary linux_openmp_64: Mar 29 2017]]
** Program Death **

I ran the exact same afni_proc.py script on this exact dataset on my own iMAC, and it ran successfully and didn’t throw this error - so I don’t believe it is something with the data itself, but I could be wrong.

Thank you for your time and help!
Best,
Lauren

2

Hi Lauran,

Thank you for the test data!

Yes, this was just a bug in allocating memory for file name (of warps).
So the program would either work fine or crash, depending on the system
and actual file names. It should not have led to erroneous results.

This has been fixed (as of version AFNI_17.2.05), and the binaries
have been updated on the web site.

Thanks again,

  • rick