AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

|
February 01, 2005 01:35PM
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
Subject Author Posted

Can I force a BRICK_STATS update?

Randy Notestine February 01, 2005 01:35PM

Re: Can I force a BRICK_STATS update?

Robert Cox February 01, 2005 02:08PM

Re: Can I force a BRICK_STATS update?

Robert Cox February 01, 2005 04:45PM

Re: Can I force a BRICK_STATS update?

Randy Notestine February 01, 2005 05:35PM

Re: Can I force a BRICK_STATS update?

Robert Cox February 02, 2005 09:17AM