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  

|
January 26, 2015 04:12PM
It looks like 3dcopy reads the .HEAD file into a header struct, changes the ID and writes it back out, but just copies the .BRIK file. Presumably the new header is incorporating the setting of AFNI_BYTEORDER, but this change isn't getting incorporated into the new .BRIK file. THD_write_datablock contains this comment:
/*---------------------------------------------------------------------*/
/*! Write an AFNI datablock to disk in the .HEAD/.BRIK format:
     - Returns True if OK, False if an error.
     - See also AFNI_refashion_dataset.
     - All attributes must now be set prior to calling this,
       via function THD_set_dataset_attributes().
     - The one exception to the above rule is the BYTEORDER attribute.
-----------------------------------------------------------------------*/

Maybe write_brick needs to be checked earlier in this function?
Subject Author Posted

Byte-swap issue

rbirn January 26, 2015 01:52PM

Re: Byte-swap issue

Daniel Glen January 26, 2015 04:01PM

Re: Byte-swap issue

Isaac Schwabacher January 26, 2015 04:12PM

Re: Byte-swap issue

Daniel Glen January 26, 2015 04:57PM

Re: Byte-swap issue

Isaac Schwabacher January 27, 2015 12:08PM

Re: Byte-swap issue

Daniel Glen January 27, 2015 02:18PM