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 12, 2020 09:49AM
Howdy-

This seems to point to the main problem:
** FATAL ERROR: Input datasets do not match in number of voxels!
'-netrois' volume has 1081344 vox,
'-uncert' volume has 1750656 vox,
'-inset' volume has 1750656 vox,
** Program compile date = May 4 2020
Namely, in the input datasets don't have the same grid.

A secondary problem *might* be having obliquity in the data-- probably that is only a problem if there there is *differing* obliquity across the datasets (in a way that things don't align properly).

These are the main input files:
DWUncert+orig. 
$dtipath/{}/mri/parc5002dwi.nii.gz
$dtipath/{}/MASK.nii.gz 
3dDWItoDT_*
... and it looks like the network of ROIs one is on the different grid: $dtipath/{}/mri/parc5002dwi.nii.gz.

Can I ask what processing went into the main files (3dDWItoDT_*, DWUncert+orig and $dtipath/{}/MASK.nii.gz), and what wen into $dtipath/{}/mri/parc5002dwi.nii.gz?

Also, what is the output of
3dinfo \
   -obliquity \
   -same_grid \
   -prefix \
   DWUncert+orig.  \
   $dtipath/{}/mri/parc5002dwi.nii.gz  \
   $dtipath/{}/MASK.nii.gz   \
   3dDWItoDT_*
?

--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