We fixed Carl's problem, too, and I wanted to mention it here for
anyone else who runs into it--the Analyze reading code
currently defaults to using one of the header fields as a scaling
factor if the data is an integer type. When that scaling field just
contains junk, you may end up having a file scaled from 0 to
1E-37, which can confuse many viewing and processing programs.
The solution is, if this field is not being used in your files, to set
AFNI_ANALYZE_SCALE to NO when reading or processing these
files.
rich