[Pkg-exppsy-pynifti] [Nipy-devel] Image, design, usecases

[Alexis Roche]

Hi,

> ... so let me propose a potentially over-simplistic interface of
> scipy.io.vimages:

Yes, it looks good, scipy end-users won't expect vimages to return
home-made python objects. Also, by decoupling things you gain
flexibility, and can better address the potential disadvantage of
having pynifti dependent on the destiny of nipy (although an actual
dependency can be avoided, and probably should be).

This said, I don't see myself using directly scipy.io.vimages in the
future -- or, if that happens, it will probably be because we screwed
up nipy pretty badly. As a nipy user and developer, all that matters
to me is to be able to type:

import nipy
img = nipy.load('file.nii')

and have img.get_data, img.get_affine,... right in front of my nose.

Alexis

-- 
Alexis Roche, PhD
Researcher, CEA, Neurospin, Paris, France
Academic Guest, ETHZ, Computer Vision Lab, Zurich, Switzerland
http://alexis.roche.googlepages.com