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
|
Jim Eliassen
December 18, 2003 10:20AM
Hi,

We are using 4swap to convert some data from a Varian Inova system (Solaris) to Linux (Intel, running Linux 2.4.21-0.13mdkenterprise, i686). We are byte-swapping a floating point dataset, an mdeft3d (high-res T1 weighted).

I notice different behavior when we use 4swap in the command line vs. through the to3d GUI (AFNI. Version 2.55g of 21 Oct 2003 [[Precompiled binary linux_gcc32: Oct 27 2003]]). The GUI gives us occasional black specs distributed throughout the brain (I don't know about outside the brain) in the viewer as well as in the output dataset. Using the command line version of 4swap, these specs do not appear in either the viewer or output dataset.

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