Afni3dAttribute

Currently, there is no postscript documentation for this program.

To read the help documentation generated from the command line go here.

To learn about afni data types follow this link.

Invocation

java Afni3dAttribute

Afni3dAttribute window

Information to be entered

• Input dataset
  This is where you select your Afni Dataset. You can select a file of type .HEAD or .BRIK, or you can just select the file without the .HEAD. It will then attempt to find the .HEAD file and read information from it.
• View attribute
  This box allows selection of the attribute you would like to see from the dataset. Note that not all attributes are present in all datasets. For more details on attributes, see here.
  • ALL
    This selection will print all available attributes in the dataset.
  • BRICK_FLOAT_FACS
    There should be nvals=DATASET_RANK[1] values here. For the p-th sub-brick, if f=BRICK_FLOAT_FACS[p] is positive, then the values in the .BRIK should be scaled by f to give their "true" values.
  • BRICK_KEYWORDS
    List of keywords for each sub-brick of the dataset. By convention, separate keywords for the same sub-brick would be separated by " ; " within the sub-brick's keyword string.
  • BRICK_LABS
    These are labels for the sub-bricks, and are used in the choosers for sub-brick display when the dataset is a bucket type.
  • BRICK_STATAUX
    This stores auxiliary statistical information about sub-bricks that contain statistical parameters.
  • BRICK_STATS
    BRICK_STATS[2*p] is the minimum value stored in the brick, and BRICK_STATS[2*p+1] is the maximum value stored in the brick.
  • BRICK_TYPES
    BRICK_TYPES[p] is a code that tells the type of data stored in the .BRIK file for that sub-brick.
  • BYTEORDER_STRING
    This attribute describes the byte-ordering of the data in the .BRIK file. Its value must be one of the strings "LSB_FIRST" or "MSB_FIRST".
  • DATASET_DIMENSIONS
    This attribute contains three values that determine the size of each spatial axis of the dataset: the number of voxels along the x-axis (nx), the number of voxels along the y-axis, and the number of voxels along the z-axis (nz).
  • DATASET_KEYWORDS
    List of keywords for this dataset. By convention, keywords are separated by " ; ".
  • DATASET_NAME
    A longer name describing the dataset contents.
  • DATASET_RANK
    This attribute contains two values that determine the dimensionality of the dataset: the number of spatial dimensions (must be 3) and the number of sub-bricks in the dataset.
  • DELTA
    This attribute contains three numbers giving the (x,y,z) voxel sizes, in the same order as ORIENT_SPECIFIC.
  • HISTORY_NOTE
    A multi-line string giving the history of the dataset.
  • IDCODE_ANAT_PARENT
    ID code for the "anatomy parent" of this dataset.
  • IDCODE_DATE
    Gives the creation date for the dataset.
  • IDCODE_STRING
    15 character string (plus NUL) giving a unique identifier for the dataset, independent of the filename assigned by the user. If this attribute is not present, the input routine will make one up for the dataset. ID codes are used to provide links between datasets.
  • IDCODE_WARP_PARENT
    ID code for the "warp parent" of this dataset.
  • LABEL_1
    A short label describing the dataset.
  • LABEL_2
    Another short label describing the dataset.
  • MARKS_XYZ
    30 values giving the xyz-coordinates (Dicom order) of the markers for this dataset.
  • MARKS_LAB
    200 characters giving the labels for the markers. A marker whose string is empty (all NUL characters) will not be defined or shown by AFNI.
  • MARKS_HELP
    2560 characters giving the help strings for the markers.
  • MARKS_FLAGS
    Type of markers.
  • NOTES_COUNT
    The number of auxiliary notes attached to the dataset(from 0 to 999).
  • NOTE_NUMBER_001
    The first auxiliary note attached to the dataset.
  • ORIENT_SPECIFIC
    This attribute contains one of three integer codes describing the spatial orientation of the dataset axes: [0] for the x-axis, [1] for the y-axis, and [2] for the z-axis.
  • ORIGIN
    This attribute contains three numbers giving the xyz-coordinates of the center of the (0,0,0) voxel in the dataset.
  • SCENE_DATA
    This attribute contains one of three integer codes describing the dataset type: the view type, the func type or Anat type.
  • STAT_AUX
    This attribute is for the Func type datasets of the following types: fico = FUNC_COR_TYPE, fitt = FUNC_TT_TYPE, fift = FUNC_FT_TYPE, fict = FUNC_CT_TYPE, fibt = FUNC_BT_TYPE, fibn = FUNC_BN_TYPE, figt = FUNC_GT_TYPE and fipt = FUNC_PT_TYPE.
  • TAGALIGN_MATVEC
    12 numbers giving the 3x3 matrix and 3-vector of the transformation derived in 3dTagalign.
  • TAXIS_FLOATS
    This attribute contains the following: [0] = Time origin, [1] = Time step (TR), [2] = Duration of acquisition, [3] = z-axis offset for the slice-dependent time offsets, [4] = z-axis step for the slice-dependent time offsets.
  • TAXIS_NUMS
    This attribute contains the following: [0] = Number of points in time, [1] = Number of slices with time offsets, and [2] = Units codes for TAXIS_FLOATS[1].
  • TAXIS_OFFSETS
    This array gives the time offsets of the slices defined by TAXIS_FLOATS[3..4]. If TAXIS_NUMS[1] == 0, then this attribute is not used.
  • TO3D_ZPAD
    3 integers specifying how much zero-padding to3d applied when it created the dataset (x,y,z axes).
  • TYPESTRING
    This attribute determines if the dataset is of Anat or Func type.
  • VOLREG_BASE_IDCODE
    In the 3dvolreg output dataset header, this tells which dataset was the base for registration.
  • VOLREG_BASE_NAME
    The .HEAD filename of the 3dvolreg base dataset.
  • VOLREG_CENTER_OLD
    The xyz-coordinates (Dicom order) of the center of the input dataset to 3dvolreg; this is written to 3dvolreg's output dataset, and is used by the -rotparent options to 3dvolreg and 3drotate.
  • VOLREG_CENTER_BASE
    The xyz-coordinates (Dicom order) of the center of the base dataset to 3dvolreg; this is written to 3dvolreg's output dataset, and is used by the -rotparent options to 3dvolreg and 3drotate.
  • VOLREG_GRIDPARENT_IDCODE
    Similar to the above, but for a 3dvolreg output dataset that was created using a -gridparent option.
  • VOLREG_GRIDPARENT_NAME
    The .HEAD filename of the -gridparent.
  • VOLREG_INPUT_IDCODE
    In the 3dvolreg output dataset header, this tells which dataset was the input to 3dvolreg.
  • VOLREG_INPUT_NAME
    The .HEAD filename of the 3dvolreg input dataset.
  • VOLREG_ROTCOM_NUM
    The single value in here tells how many sub-bricks were registered by 3dvolreg.
  • VOLREG_ROTPARENT_IDCODE
    If a 3dvolreg run uses the -rotparent option, then this value in the header of the output dataset tells which dataset was the rotparent.
  • VOLREG_ROTPARENT_NAME
    The .HEAD filename of the -rotparent.
  • WARP_TYPE
    This attribute is the integer code describing the type of warp.
  • WARP_DATA
    Data that define the transformation from the warp parent to the current dataset.
• Enter your own attribute
  If checked, type in the name of a custom attribute to view. If it does not exist, a dialog box will appear indicating error.
• Include attribute name in printout
  This option will toggle printing of the attribute name along with attribute information. If 'ALL' is selected above, this is a default selection.

• Menubar
• Toolbar
• Output window