-
Notifications
You must be signed in to change notification settings - Fork 262
BIAP3
Matthew Brett edited this page Mar 26, 2011
·
4 revisions
DICOM files in particular have a lot of information in them that we might want to carry with the image.
One obvious place to store this information in in a nifti header extension. See adding nifti extensions for more detail.
There is currently a DICOM type extension - code 2. I (MB) can't find any evidence that it's being used in the wild. It's not even quite clear what format the data should be in see this nifti thread. In any case, we probably don't want to have to store the entire DICOM header inside the nifti, and DICOM is a painful format if we need to add custom fields.
Other extension types (from adding nifti extensions):
- 0 = NIFTI_ECODE_IGNORE = unknown private format (not recommended!)
- 2 = NIFTI_ECODE_DICOM = DICOM format (i.e., attribute tags and values): http://medical.nema.org/
- 4 = NIFTI_ECODE_AFNI = AFNI header attributes: The format of the AFNI extension in the NIfTI-1.1 format is described at http://nifti.nimh.nih.gov/nifti-1/AFNIextension1/
- 6 = NIFTI_ECODE_COMMENT = comment: arbitrary non-NUL ASCII text, with no additional structure implied
- 8 = NIFTI_ECODE_XCEDE = XCEDE metadata: http://www.nbirn.net/Resources/Users/Applications/xcede/index.htm
- 10 = NIFTI_ECODE_JIMDIMINFO = Dimensional information for the JIM software (XML format); contact info is Dr Mark A Horsfield: mah5*AT*leicester.ac.uk.
- 12 = NIFTI_ECODE_WORKFLOW_FWDS = Fiswidget XML pipeline descriptions; documented at http://kraepelin.wpic.pitt.edu/~fissell/NIFTI_ECODE_WORKFLOW_FWDS/NIFTI_ECODE_WORKFLOW_FWDS.html ; contact info is Kate Fissell: fissell+*AT*pitt.edu.