From: Kris T. <kri...@gm...> - 2012-09-20 08:03:53
|
> From: Andy Buckle > Sent: 19 September 2012 19:01 > > > > From adamaitkenhead > > Also on a different note, I've written functions which read/write the > > Analyze format, giving functions equivalent to Matlab's analyze75info and > > analyze75read. Would you rather keep the Dicom toolbox purely for the > Dicom > > format, or are you interested in expanding it to become a general Medical > > File Format toolbox? No worries if not, just thought I'd see what you > > thought before I see where else they could fit into Octave-forge. > > > > Adam > > I have not used analyze75. If it is just m-files, then the image > package is probably a good place. The main reason dicom is on its own > is that it has burdensome dependencies. > I'd keep it out of the dicom package as well. Note that there's a number of packages out there to read nifti files (which is a superset of analyze75, see http://nifti.nimh.nih.gov/nifti-1/), not all with very clear license though. One that seems ok is http://www.nitrc.org/projects/cbinifti/, but I haven't used it (it might rely on unix pipes) . Then there's http://niftilib.sourceforge.net/ which also provides matlab support, but as it's the IO basis for SPM, and a lot of SPM works on Octave, it might work. Of course, there's still a place for analyze75info etc compatible functions. I have no idea if that already exists somewhere else. Kris |