[Pkg-exppsy-pynifti] [Nipy-devel] Image, design, usecases
Matthew Brett
matthew.brett at gmail.com
Wed May 13 19:46:12 UTC 2009
Hi,
> The only real essentials are:
> - basic file handling: open, seek, read, write, close
> - proper handling of the header : some validation is nice. I don't
> really care about the extensible part of the header.
>
> Memory mapping mapping as an numpy array would be great, but not a
> requirement. Only supporting uncompressed versions is fine too.
> Anything that restricts you to 4D is bad from my perspective.
Um - at the moment, you never see file handling. I mean that, if you
have some data, and want to put it into and image and save it, it
goes:
img = Nifti1Image(data, affine)
img.to_filespec('somefile.nii')
The current readers, writers support complex data, 64 and 128 bit.
There's some header validation on load with output to stderr or
arbitrary logging location. We do memory mapping when we can
(uncompressed float read). The readers and writers do compression /
uncompression automatically. There's no restriction on number of
dimensions structurally, but I haven't tested it with more than 4D...
See you,
Matthew
More information about the Pkg-exppsy-pynifti
mailing list