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  

|
June 19, 2018 10:05AM
A follow-up, it definitely appears to be an identifier code issue. I used 3dCalc to 'convert' the filtered_data to AFNI BRIK format (-a data -expr 'a') and this altered the identifier code. I was then able to run InstaCorr with no issues.

I'm still relatively new to AFNI, is there somewhere it would give a warning that multiple 'identical' datasets were detected? It did provide warnings that the files had "dimensions altered since AFNI extension was added" but I wasn't certain what to make of that.
Subject Author Posted

InstaCorr not using selected dataset, strange behavior

dowdlelt June 19, 2018 09:39AM

Re: InstaCorr not using selected dataset, strange behavior

dowdlelt June 19, 2018 10:05AM

Re: InstaCorr not using selected dataset, strange behavior

rick reynolds June 21, 2018 09:31AM