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  

Previous Message Next Message
Message List New Topic Print View
|
bob cox
December 18, 2003 11:08AM
The problem is probably that when you read the data into to3d directly as floats but before byte swapping, the program will still check the values for being legal floating point numbers (not all 32 bit patterns are legal IEEE floating point values). Those that fail are set to 0. Then when you byte swap them in the GUI, they will still be 0 -- they aren't re-read from disk.

The solutions are (1) since you know you have to byte swap the files, do so with 4swap prior to to3d, or (2) use the -nofloatscan option on the to3d command line, or (3) fix to3d's behavior. However, we are so busy here with other urgent changes now that we won't do (3) for quite a while.

bob cox
Reply Quote
RSS
Subject Author Posted

different GUI vs. command-line 4swap behavior

Jim Eliassen December 18, 2003 10:20AM

Re: different GUI vs. command-line 4swap behavior

bob cox December 18, 2003 11:08AM