These functions extract the contents of a NIfTI-1 or ANALYZE-7.5 header, closely approximating how it is (or would be) stored on disk. Defaults will be used where information is missing, but no processing is performed on the metadata.
1 2 3 4 5 6 7 8 9
An image, in any acceptable form (see
The NIfTI-1 standard was originally formulated as a roughly backwards- compatible improvement on the ANALYZE format. Both formats use a binary header structure of 348 bytes, but the field names and their interpretation is often non-equivalent. These functions dump these fields, without regard to whether or not the result makes proper sense.
dumpNifti is an alias of
niftiHeader, but the former is now
niftiHeader, a list of class
named components corresponding to the elements in a raw NIfTI-1 header.
analyzeHeader, the equivalent for ANALYZE-7.5.
Several medical image analysis packages, such as SPM and FSL, use the
originator field to store a coordinate origin. This
interpretation is also returned, in the
Both of these functions call
asNifti on their arguments to
coerce it to NIfTI, except in one specific circumstance: when
analyzeHeader is called with a single-element character-mode
argument that is not an
"internalImage" object. In this case the
string is taken to be a path and the header is reported as stored on disk.
This is because otherwise the header may be changed by the process of
converting it to NIfTI and back.
Jon Clayden <email@example.com>
The NIfTI-1 standard (https://www.nitrc.org/docman/view.php/26/64/nifti1.h).
1 2 3 4
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.