Public Attributes | |
short int | dim [8] |
char | vox_units [4] |
char | cal_units [8] |
short int | unused1 |
short int | datatype |
short int | bitpix |
short int | dim_un0 |
float | pixdim [8] |
float | vox_offset |
float | roi_scale |
float | funused1 |
float | funused2 |
float | cal_max |
float | cal_min |
int | compressed |
int | verified |
int | glmax |
int | glmin |
|
Bits per pixel. This field must agree with the datatype and data_type fields.
|
|
The parameters 'cal_max' and 'cal_min' provided a mechanism for rescaling the voxel values into a different range of value representation. This string allowed whatever the range of value representation was to be expressed with these string characters. Never really used in a robust manner. |
|
|
|
Specifies the name of the calibration unit, valid values are "mm","cm" and "in". NOTE: if no match is found, "mm" is assumed. |
|
Valid values are only 0 and 1. A 0 value indicates that the file is uncompressed. A 1 value indicates that the *.img file has been compress with the standard Unix 'compress' utility.
|
|
A short int that defines the type of data being stored. NOTE: THIS MUST BE FILLED IN. This is the field that most applications use to determine the data storage type. Valid values are defined by DataTypeKeyValues.
|
|
Array of image dimensions
|
|
Unused value for future expansion. |
|
Unused, for future expansion |
|
Unused, for future expansion |
|
This is the global max/min for the entire volume image (or sets of volume images if there are multiple volumes in this file). The cal_max/min are used only if the desired representation range of the data is different from the true range of the data. For example, CT data may be stored in signed shorts with a range from 0 - 2000, but an appropriate representation range for these values in in Hounsfield units from -1000 to 1000. Any reported values in Analyze were scaled via this value scaling function. UNSIGNED INT and COMPLEX were really not supported under ANALYZE 7.5., so these should be avoided in the Analyze 7.5 file format. The max/min for FLOATs was the nearest integer to the floating point values. |
|
|
|
Parallel array to dim giving voxel dimensions NOTE: pixdim[0] is ignored, and the number of dims are taken from dims[0], and pixdim[1..7] are the actual pixdims.
|
|
The "ROI Scale Factor" was really added in by the developers of SPM. This is used as a multiplicative factor to scale all values measured in the ROI module by this multiplicative factor. This really shouldn't be set by any other application outside of Analyze and SPM. |
|
Unused field for future expansion. |
|
This was only used internally by Pre 1995 versions of analyze. |
|
Byte offset in the .img file at which voxels start. If value is negative specifies that the absolute value is applied for every image in the file. |
|
Specifies the spatial units of measure for a voxel, valid values are "mm","cm" and "in". NOTE: if no match is found, "mm" is assumed. |