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  

|
September 11, 2019 04:28PM
Hi,

I have question about running 3dTrackID. I have used this command for several data, but some data gave me the error message. I followed AFNI FATCAT pipeline for DTI processing.

Here is my command


3dTrackID \
-mode PROB \
-dti_in dt \
-netrois sel_indt_aparc.a2009s+aseg_REN_gm_GMI.nii.gz \
-uncert dt_UNC.nii.gz \
-prefix o.pr00 \
-nifti \
-no_indipair_out \
-dump_rois AFNI \
-alg_Thresh_FA 0.2 \
-alg_Thresh_Frac 0.1 \
-alg_Nseed_Vox 5 \
-alg_Nmonte 1000 \
-echo_edu \
-overwrite



and I got the error message as following,

+++ Command Echo:
3dTrackID -mode PROB -dti_in dt -netrois sel_indt_aparc.a2009s+aseg_REN_gm_GMI.nii.gz -uncert dt_UNC.nii.gz -prefix o.pr00 -nifti -no_indipair_out -dump_rois AFNI -alg_Thresh_FA 0.2 -alg_Thresh_Frac 0.1 -alg_Nseed_Vox 5 -alg_Nmonte 1000 -overwrite

++ Tracking mode: PROB

++ Number of ROIs in netw[0] = 167
++ Have labeltable for naming things.
*+ WARNING: file dt_UNC.nii.gz: corrected 7 float errors
++ SEARCHING for vector files with prefix 'dt*':
FINDING: 'V1' 'V2' 'V3'
++ SEARCHING for scalar files with prefix 'dt*':
FINDING: not:'CHI' not:'DT' 'FA' 'L1' not:'L2' not:'L3' 'MD' 'RD' *+ WARNING: file dt_UNC.nii.gz: corrected 7 float errors
not:'UNC' not:'cwts' not:'debugbriks'
++ Done with scalar search, found: 4 parameters
--> so will have 15 output data matrices.
++ Minor note: there is a tiny (magn < 0.1) vector in the 0-th direction set.
--> Will exclude that voxel from walkable mask-- recommend checking model fit.
++ Minor note: there is a tiny (magn < 0.1) vector in the 0-th direction set.
--> Will exclude that voxel from walkable mask-- recommend checking model fit.
++ Minor note: there is a tiny (magn < 0.1) vector in the 0-th direction set.
--> Will exclude that voxel from walkable mask-- recommend checking model fit.
++ Minor note: there is a tiny (magn < 0.1) vector in the 0-th direction set.
--> Will exclude that voxel from walkable mask-- recommend checking model fit.
++ Minor note: there is a tiny (magn < 0.1) vector in the 0-th direction set.
--> Will exclude that voxel from walkable mask-- recommend checking model fit.
++ Minor note: there is a tiny (magn < 0.1) vector in the 0-th direction set.
--> Will exclude that voxel from walkable mask-- recommend checking model fit.
++ Minor note: there is a tiny (magn < 0.1) vector in the 0-th direction set.
--> Will exclude that voxel from walkable mask-- recommend checking model fit.
++ Minor note: there is a tiny (magn < 0.1) vector in the 0-th direction set.
--> Will exclude that voxel from walkable mask-- recommend checking model fit.
++ Effective Monte iterations: 5000. Fraction threshold set: 0.10000
--> Ntrack voxel threshold: 500.

Fatal Signal 11 (SIGSEGV) received
Bottom of Debug Stack
** AFNI version = AFNI_18.2.16 Compile date = Sep 12 2018
** [[Precompiled binary linux_openmp_64: Sep 12 2018]]
** Program Death **
** If you report this crash to the AFNI message board,
** please copy the error messages EXACTLY, and give
** the command line you used to run the program, and
** any other information needed to repeat the problem.
** You may later be asked to upload data to help debug.
** Crash log is appended to file /home/jung/.afni.crashlog

Could you give me some idea about this issue?

Thanks

Jung
Subject Author Posted

3dTrackID error issue

chaj September 11, 2019 04:28PM

Re: 3dTrackID error issue

ptaylor September 12, 2019 09:24AM