Options

General

• Verbose mode
• If checked, this option displays some header information during conversion.
• Default filename prefix
• This field allows users to specify their own prefix when selecting or generating files in a directory.
• Range of volumes
• This field allows users to specify a subset of the dataset to be converted. The range is given by a regular expression subset. For example [1,4,2] means first, fourth , and second volume in a given order. While [1..5(2)] means volumes from 1 to 5 with step 2. Indexing of the range specifier is one based.
• Range of slices
• This field allows the user to enter the slices that need to be used. For example: [3-9] means from 3rd to 9th slices will be used, while [3,9] means only the 3rd and 9th slice.

Increments could also be used, for example [3-9(3)] would include the 3rd, 6th and 9th slices.
• Swap bytes on input/output
This field swaps bytes of input dataset before the conversion occurs or on the output after the conversion. Byte flipping is useful for going between different endian machines.

Input

Output

• Merge header
• Usually during conversion some data in the header file is lost. For example, Analyze has a small subset of information stored inside its header file, while in Pittsburgh header anything can be stored. When converting from Analyze to Pgh 1.0, a Pittsburgh header cannot get information that the Analyze format does not have. The solution is to specify an external Pgh header to merge with output header. This is the only way to stuff extra information, such as the mmTRz fields, into the PGH header during the conversion.
• Blocking factor
• This allows creation of multiple files having specified number of volumes in each file. For example, if you want to convert 1000 Analyze images into 10 Pgh files, you can specify a blocking factor of 100.
• Scale factor
• Scale the output dataset by this number. This option works as follows: read in the data, convert it to float64 datatype, scale it by given scale factor, write out the scaled data converted to proper output datatype.
• WARNING: Some scaled data values might not fit into output datatype, in this case the value is truncated to fit into the bounds of that datatype. When this occurs the warning is displayed.
• Datatype
• This specifies the output datatype. This is useful whenever you want to change the type of data. For example, you can convert Analyze int16 data to Pgh float32. Native datatype means that the datatype of the output will be the same as the datatype of the input.
• WARNING: During the conversion from floats to ints, shorts, or bytes, the precision of information can be lost.
• Swap bytes (currently only Afni and Pgh formats)
• This features sets the flag in the Afni and Pgh header file that tells Afni or Pgh applications to swap bytes on input. NOTE: It doesn't actually swap bytes on a dataset itself.
• Specify auxiliary header information
• If checked, this option allows the user to enter format specific information not covered by global fields. For most of the formats it is a simple list of key=value pairs. For afni it allows you to setup some essential parameters with pull-down menus and radio buttons, but internally converts them to key=value pairs.