I'd appreciate an explanation of how afni programs, specifically 3dcalc, decide what to set BRICK_FLOAT_FACS to, and/or how to force such a program to not use it.
Currently we have a process that uses:
3dcalc -a somefile -prefix $someprefix -expr 'astep(a,0)'
... which instead of producing a file of 0's and 1's, produces a file with 0's and 0x7FFF's, with a BRICK_FLOAT_FACS = 3.051851e-05.
Needless to say, not what the subsequent stage expected, though other AFNI programs are just fine with this.
Thanks,
Graham