On 21 September 2012 10:18, adam aitkenhead <adamaitkenh...@hotmail.com> wrote: > The underlying read function has a different calling syntax from Matlab, as > it reads both the header and the image in one go (I wrote it like that > before I realized there were similar functions in Matlab). However I've > also written functions which call it using the same format as analyze75info > and analyze75read. This does mean that it runs slower than Matlab, but it > shouldn't be difficult to change it to read only the appropriate parts if > needed.
It's ok to do more than the matlab functions, there's plenty of examples where that is the case. It's just not very good to have conflicts with their API. So if your analyze75read works as in "[image, header] = analyze75read (fname)", it's still matlab compatible while being more useful at the same time. It seems to me that matlab also has a analyze75info function, maybe you'd like to make it compatible? I'm planning on making a release of the image package Sunday in case you are interested in having your functions included now. Otherwise they can still be included on the next release. Carnë ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
