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  

|
October 22, 2020 10:54AM
Thanks for sending that info.

The commands in #1 and #2 look fine. Depending on the data, in the 3dDWUncert command having more than 50 iterations might be useful, like having ~300 hundred. The Bootcamp demo uses 50 for speed considerations. It is a question of convergence of the uncertainty distributions (at the cost of speed for more iterations). But that shouldn't be causing the issues here in 3dTrackID.

Re. #3:
The mask looks like a mask, though I can't see it's overlap with the data... What is "3dinfo -history $dtipath/{}/MASK.nii.gz"?

Re. #4:
Interesting, OK. I am not familiar with this process at all with FS; I normally use the aparc+aseg and aparc+aseg2009 ROIs from their outputs. But given the number of steps and mapping, I wonder if the final grid of this dset is mismatched with the others? What did you use for the mapping/alignment process? AFNI tools, and if so, which one(s)? When bringing them to the diffusion space, is the "-master .." dset one of the diffusion ones, so the grid will be correct?

Re. the 3dinfo command:
Well, I was trying to use your file names and paths... but you need to provide the correct name/path for each of your datasets, which appear to be in different places. The paths for 3dDWUncert+orig and 3dDWItoDT_* are not correct, hence the output of NO-DSET for those two items. Can you please run this modified/expanded form, putting in the correct paths for where "[some path]" is written (if you get NO-DSET showing up, then something isn't correct and the path needs to be fixed):
3dinfo \
   -obliquity \
   -same_grid \
   -n4   \
   -ad3 \
   -prefix \
   [some path]/DWUncert+orig.  \
   $dtipath/{}/mri/parc5002dwi.nii.gz  \
   $dtipath/{}/MASK.nii.gz   \
   [some path]/3dDWItoDT_DT*
(though I think the output of even that first command shows that the MASK and parc5002 dsets are on different grids.)

-pt
Subject Author Posted

3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

eji October 12, 2020 08:12AM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

ptaylor October 12, 2020 09:49AM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR Attachments

eji October 21, 2020 06:44AM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

ptaylor October 22, 2020 10:54AM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR Attachments

eji October 26, 2020 03:04PM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

ptaylor October 27, 2020 08:47AM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

eji November 10, 2020 09:35AM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

ptaylor November 10, 2020 10:26AM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

eji November 10, 2020 11:37AM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

ptaylor November 10, 2020 11:59AM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

eji November 10, 2020 12:14PM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

eji November 10, 2020 12:34PM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

ptaylor November 10, 2020 12:50PM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

eji November 10, 2020 04:11PM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

ptaylor November 13, 2020 02:50PM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

eji November 14, 2020 03:23AM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

eji November 24, 2020 11:15AM

Re: 3dTrackID Fatal Signal 11 (SIGSEGV) + FATAL ERROR

ptaylor November 24, 2020 01:02PM