nifti2_data_format > RE: NIFTI-2 proposal
Feb 28, 2011  05:02 PM | Jochen Weber
RE: NIFTI-2 proposal
Copy that :) changes seem reasonable and straight forward.

I was just
wondering ... is there a particular reason to keep any of the unused fields (see char data_type[10] or db_name[18] from http://nifti.nimh.nih.gov/pub/dist/src/n... for instance)? I would think it's easy enough to set these to default values as part of an output filter that saves a NIFTI-2 struct/image as a NIFTI-1 or Analyze 7.5 header stream to disk; in that case, maybe a total header size (incl. a null-extension) of 512 could be achieved, which might make mapping into a compound object (where actual image data is located in the same file on disk) a little more efficient, given that accessing data slice-by-slice on harddisks still makes it more likely to hit a block boundary for raw images with a 64x64 or 128x128 matrix...

/jochen

Threaded View

TitleAuthorDate
Mark Jenkinson Feb 28, 2011
Mark Jenkinson Mar 15, 2011
Cinly Ooi Mar 15, 2011
Cinly Ooi Mar 2, 2011
Ged Ridgway Mar 7, 2011
Jon Clayden Mar 5, 2011
Cinly Ooi Mar 1, 2011
Andrew Janke Mar 1, 2011
Cinly Ooi Mar 2, 2011
Satrajit Ghosh Mar 5, 2011
Cinly Ooi Mar 1, 2011
Cinly Ooi Mar 1, 2011
Cinly Ooi Mar 1, 2011
Cinly Ooi Mar 1, 2011
Denis Rivière Feb 28, 2011
Cinly Ooi Mar 1, 2011
Brandon Whitcher Mar 1, 2011
Satrajit Ghosh Feb 28, 2011
Jonas Larsson Mar 1, 2011
Mark Horsfield Mar 1, 2011
Andrew Janke Mar 1, 2011
RE: NIFTI-2 proposal
Jochen Weber Feb 28, 2011
Randall Frank Mar 1, 2011
Michael Martinez Feb 28, 2011
Cinly Ooi Feb 28, 2011
Chris Rorden Feb 28, 2011