I think the float errors come from NaN’s (not a number), usually generated in Matlab. We filter these to change those values to zero in AFNI with AFNI_FLOATSCAN set to YES. This is the entry that describes that AFNI environment variable in README.environment.
Variable: AFNI_FLOATSCAN (editable)
If this YES/NO variable is set to YES, then floating point bricks
are checked for illegal values (NaN and Infinity) when they are
read into an AFNI program – illegal values will be replaced by
zeros. If a dataset brick contains such illegal values that go
undetected, AFNI programs will probably fail miserably, and have
been known to go into nearly-infinite loops.
Setting this variable implies setting AFNI_NOMMAP to YES, since
only in-memory bricks can be altered (mmap-ed bricks are readonly).
The command line program ‘float_scan’ can be used to check and
patch floating point files.
[14 Sep 1999] The program to3d will scan input float and complex
files for illegal values, and patch illegal input numbers with
zeros in the output dataset. If this behavior is not desired for
some bizarre reason, the ‘-nofloatscan’ command line option to
to3d must be used.
And I have another question about how to use 3dsynthesize.
The warning message I keep getting is(all sub-briks):
*+WARNING: clexp_int+tlrc[0] scale to shorts mean misfit error =12.4% – *caution
*+WARNING: clexp_int+tlrc[1] scale to shorts mean misfit error =10.6% – *caution
…
My script is:
3dsynthesize -matrix X.xmat.1D -cbucket all_betas.clexp+tlrc -select baseline -prefix stuffNo
3dcalc -a all_runs.clexp+tlrc -b stuffNo+tlrc -expr ‘a-b’ -prefix clexp_int
3dcalc -a all_betas.clexp+tlrc’[0]’ -b clexp_int+tlrc’[0-169]’ -expr ‘a+b’ -prefix clexp_all1
3dcalc -a all_betas.clexp+tlrc’[4]’ -b clexp_int+tlrc’[170-339]’ -expr ‘a+b’ -prefix clexp_all2
Thank you very much again!
Xin
The
National Institute of Mental Health (NIMH) is part of the National Institutes of
Health (NIH), a component of the U.S. Department of Health and Human
Services.