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  

|
eji
November 14, 2020 03:23AM
Hi pt,

The .annot parcellation was actually sent to us by another group, and is based on the fs_average template, which is why I executed a series of commands to transpose the parcellation onto each individual's surface and then convert to nifti. Am I understanding correctly that your suggestion re @SUMA_Make_Spec_FS should replace mri_aparc2aseg in our pipeline? (to clarify, I never previously used @SUMA_Make_Spec_FS, so I'm trying to figure out what it adds and where it would fit in)

3dAllineate was used to correct for eddy distortions. However, it sounds like it shouldn't be used for that and I should remove it entirely.

Also, new, relevant information: I got in touch with the people involved in data acquisition. They confirmed that there were obliquity issues for all subjects who were scanned on the Siemens scanners, which are the same set of subjects I had trouble with (where 3dInfo showed mismatched grid). They mentioned: "we have now preprocessed derivatives for both T1w and diffusion that we are happier with" and fixed it "by re-orienting the image and rotating the bvecs using the align.py script from pnlNipype (https://github.com/pnlbwh/pnlNipype/blob/master/scripts/align.py). This was done at the beginning before any further pre-processing"
-- This is not something I am familiar with. Does it sound like this should solve my issue of within-subject data being on different grids?

Thank you and have a nice weekend.
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