Hi Emmette,
I'm a little confused about your statements about "wrapping". As a
best guess, it seems reasonable that you need to byte-swap your
data. If the endian of the dataset does not match your machine, you
might consider running '2swap' on the BRIK file, along with doing a
'3drefit -byteorder' afterwards.
For example, if the output of "3dinfo dset+orig" shows a line:
Byte Order: MSB_FIRST
which stands for "most significant byte first", but you are working
on a little endian machine, then executing:
2swap dset+orig.BRIK
3drefit -byteorder LSB_FIRST dset+orig
will change the byte order on the dataset, but still allow AFNI to
interpret it correctly.
The 2swap command actually swaps bytes, and the 3drefit command
sets the new byte order in the HEAD file.
---
As for the difference between "internal" values and "scaled" values,
note that a short dataset will be stored as values in [-32768, 32767].
But AFNI datasets often have a scale factor stored in the HEAD
file, allowing the same 16-bit resolution on the numbers, but providing
basically arbitrary range. Please see the following discussion for
more details on that:
[
afni.nimh.nih.gov]
Hopefully I'm answering your questions...
- rick
