Hi Andy > > I had another look at the 'transpose or not' issue. Contrary to what I > > thought, it seems that we're reading the data transposed compared to > > matlab, for both my PET and CT data. This is rather strange, as as far as I > > know, matlab just reads the data as-is, and stores it in the usual > > column-first fashion. As far as I can see, you're doing the same (i.e. just > > calling gdcm::Bitmap::GetBuffer). This puzzles me. Is there anything > obvious > > that I'm missing? How would we transpose the image (we could call > permute of > > course). > > > > Kris > > I think intNDArray::transpose(). Not sure what to do with 3D data, in > the light of your new information about transposing. I have just added > a dcm_examples directory, with a multiframe image (RTDose). > > Sorry, I don't know why the transpose is happening. I convinced myself > it was correct as it was, > > -- > /* andy buckle */
I've incorporated a call to permute() in dicomread.cpp (transpose would probably only work for 2D images). A few more tests confirm correct behaviour, but I still don't have matlab. I've committed it nevertheless (WARNING: this change is obviously not backwards compatible). We probably would have to change dicomwrite accordingly. Kris ------------------------------------------------------------------------------ Cloud Services Checklist: Pricing and Packaging Optimization This white paper is intended to serve as a reference, checklist and point of discussion for anyone considering optimizing the pricing and packaging model of a cloud services business. Read Now! http://www.accelacomm.com/jaw/sfnl/114/51491232/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
