AFNI typically stores the min and max voxel values for each sub-brick in the BRICK_STATS attribute within the HEAD file when the data set is originally written. If you are like me, and sometimes "muck" around with the voxel values outside of AFNI, you can clear these values with "3drefit -clear_bstat", when they are no longer correct. But is there a way to force AFNI to determine the curent min/max values and update BRICK_STATS (or recreate it, if it has been cleared)?
- Randy Notestine
Software Engineer
Laboratory of Cognitive Imaging
UCSD & VA San Diego Healthcare System