On 14 June 2012 22:52, Andy Buckle <andybuc...@gmail.com> wrote: > On 14 June 2012 14:48, Michael Goffioul <michael.goffi...@gmail.com> wrote: >> On Wed, Jun 13, 2012 at 9:34 AM, Andy Buckle <andybuc...@gmail.com> wrote: >>> >>> > Hi >>> > I'm sorry to bother you with such a simple question but I'm not a >>> > sophisticated user and I could use a little help. (I am a physicist). >>> > >>> > I have begun checking whether Octave can serve as an alternative for >>> > Matlab >>> > for my needs (I work for a small MRI company). I am using the compiled >>> > version of Octave 3.6.2 under Windows 7. So far Octave seems to fit the >>> > bill, but I need to find a way of reading Dicom images. I saw that there >>> > is >>> > a package that provides this option. I tried naively installing the >>> > package >>> > but it does not work. Are these packages intended to be used as is on >>> > pre-compiled versions of Octave or are they supposed to be used only >>> > when >>> > you compile the Octave sources on your system? If they can be used with >>> > the >>> > compiled Octave, what am I doing wrong? >>> > >>> > >>> > Details what I tried: >>> > >>> > I downloaded dicom-0.1.1.tag.gz, installed it (I see it in the list of >>> > installed packages), but when I type the Octave command "pkg describe >>> > dicom" >>> > all Isee is >>> > >>> > Package name: >>> > dicom >>> > Version: >>> > 0.1.1 >>> > Short description >>> > Digital commuications in medicine (DICOM) field il. Depends on >>> > Grasssroots DICOM (GDCM). This package is not available repos for all >>> > distros. Controibutors: Judd Storrs, Kris Thielemans >>> > Status: >>> > Loaded >>> > >>> > I cannot use the function dicomread. >>> > >>> > Thanks >>> > >>> > Saul Stokar >>> > www.aspectimaging.com >>> >>> I too am a humble physicist. I have not been able to get the dicom >>> package working under windows. I would like to myself. I have tried >>> various windows builds of octave (mingw, cygwin, maybe msvc (I can't >>> remember). I can get it to compile with no warnings, but then I get a >>> crash whenever I call a dicom* function. >>> >>> The simplest thing would be to use linux, where it should be relatively >>> simple. >> >> >> >> I've submitted an installer for the dicom package for octave-3.6.2/VS2010. >> See [1]. >> >> I'm not a dicom user, so I can't really say whether it's 100% functional. >> What I could test is to download a dicom sample file from the web, load it >> with dicomread and display the image (after some scaling and post-processing >> to be able to use imshow). That worked fine. >> >> Michael. >> >> >> [1] http://sourceforge.net/projects/octave/files/Octave%20Windows%20binaries/Octave%203.6.2%20for%20Windows%20Microsoft%20Visual%20Studio/ > > Thanks Michael, I will try that when I get time. In the repo, there > are some DICOM files for testing (which I exclude from the package). > There is also a Makefile with a target called test[1]. You can also > just do. > test dicominfo.cpp > test dicomdict.cpp > test dicomread.cpp > test dicomlookup.cpp > > Note that dicomwrite is not implemented. > > [1] > http://octave.svn.sourceforge.net/viewvc/octave/trunk/octave-forge/extra/dicom/src/Makefile?revision=9355&view=markup
I got round to testing. I did svn co https://octave.svn.sourceforge.net/svnroot/octave/trunk/octave-forge/extra/dicom/ then from Octave (from extra\dicom\src), I did >test dicomdict.cpp PASSES 1 out of 1 tests >test dicominfo.cpp PASSES 2 out of 2 tests >test dicomlookup.cpp PASSES 2 out of 2 tests >test dicomread.cpp PASSES 1 out of 1 tests Michael - thanks again, a working Windows version will be really handy for me. I do have a few comments. http://sourceforge.net/projects/octave/files/Octave%20Windows%20binaries/Octave%203.6.2%20for%20Windows%20Microsoft%20Visual%20Studio/ The README recommends avoiding whitespace in the path, but then defaults to "C:\Program Files\...". If the user chooses somewhere else, then the dicom package installer fails, (presumably because the dicom package installer is only checking the default location). "pkg rebuild -auto dicom" fails, maybe because I have spaces in the path? I will fall back on adding "pkg load dicom" to my .octaverc. -- /* andy buckle */ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
