Hi,<br><br>Sorry to bother you again, but this morning I noticed one subtle difference between the original inputted DICOM series and the outputted DICOM volume when I view it in 3D Slicer. The outputted volume is not flipped anymore which is good, but now it is translated in the sagittal view. The original inputted series had a sagittal range of -198.4 on the left to 0 on the right as revealed by the slider in 3D Slicer, and the outputted volume has a sagittal range of (almost exactly double), i.e., -396.79 on the left and -198.4 on the right.<br>
<br>I've been trying to fix this but I have had no success yet. <br>Do you have any suggestions please?<br><br>A screen shot of the Slicer views are posted at<br><br><a href="http://www.apmaths.uwo.ca/%7Ejdrozd/SlicerImages.png" target="_blank">http://www.apmaths.uwo.ca/~jdrozd/SlicerImages1.png</a><br>
<br>The inputted series is on the left, and the outputted volume is on the right.<br><br>Below is my code:<br><br>#if defined(_MSC_VER)<br>#pragma warning ( disable : 4786 )<br>#endif<br><br><br>#include "itkImageFileReader.h" <br>
#include "itkImageFileWriter.h"<br>#include "itkOrientedImage.h"<br>#include "itkGDCMImageIO.h"<br>#include "itkGDCMSeriesFileNames.h"<br>#include "itkImageSeriesReader.h"<br>
<br>int main(int argc, char *argv[])<br>{<br> char *paramname;<br> if ( argc < 2 )<br> {<br> std::cout << "Parameter file name missing" << std::endl;<br> std::cout << "Usage: " << argv[0] << " param.file" << " atlas.file" << " subject.file" <<std::endl;<br>
return EXIT_FAILURE;<br> } <br> else <br> { <br> paramname=argv[1]; <br> }<br><br>typedef short InputPixelType;<br> const unsigned int InputDimension = 3;<br><br> typedef itk::Image< InputPixelType, InputDimension > InputImageType;<br>
<br> typedef itk::ImageSeriesReader< InputImageType > ReaderSeriesType;<br><br> ReaderSeriesType::Pointer fixedsubjectfilter = ReaderSeriesType::New();<br><br> typedef itk::GDCMImageIO ImageIOType;<br><br>
ImageIOType::Pointer gdcmImageIO = ImageIOType::New();<br><br>fixedsubjectfilter->SetImageIO( gdcmImageIO );<br><br>typedef itk::GDCMSeriesFileNames NamesGeneratorType;<br> NamesGeneratorType::Pointer nameGenerator = NamesGeneratorType::New();<br>
<br> nameGenerator->SetUseSeriesDetails( true );<br> nameGenerator->AddSeriesRestriction("0008|0021" );<br><br> nameGenerator->SetDirectory( argv[3] );<br><br>try<br> {<br> std::cout << std::endl << "The directory: " << std::endl;<br>
std::cout << std::endl << argv[3] << std::endl << std::endl;<br> std::cout << "Contains the following DICOM Series: ";<br> std::cout << std::endl << std::endl;<br>
<br>typedef std::vector< std::string > SeriesIdContainer;<br> <br> const SeriesIdContainer & seriesUID = nameGenerator->GetSeriesUIDs();<br> <br> //std::cout << seriesUID.begin() << endl;<br>
<br> SeriesIdContainer::const_iterator seriesItr = seriesUID.begin();<br> SeriesIdContainer::const_iterator seriesEnd = seriesUID.end();<br> while( seriesItr != seriesEnd )<br> {<br> std::cout << seriesItr->c_str() << std::endl;<br>
seriesItr++;<br> }<br><br>std::string seriesIdentifier;<br><br> if( argc > 4 ) // If no optional series identifier<br> {<br> seriesIdentifier = argv[3];<br> }<br> else<br> {<br> seriesIdentifier = seriesUID.begin()->c_str();<br>
}<br><br>std::cout << std::endl << std::endl;<br> std::cout << "Now reading series: " << std::endl << std::endl;<br> std::cout << seriesIdentifier << std::endl;<br>
std::cout << std::endl << std::endl;<br><br>typedef std::vector< std::string > FileNamesContainer;<br> FileNamesContainer fileNames;<br><br> fileNames = nameGenerator->GetFileNames( seriesIdentifier );<br>
<br>fixedsubjectfilter->SetFileNames( fileNames );<br><br>try<br> {<br> fixedsubjectfilter->Update();<br> std::cout << "Subject read successfully" << std::endl;<br> }<br> catch (itk::ExceptionObject &ex)<br>
{<br> std::cout << ex << std::endl;<br> return EXIT_FAILURE;<br> }<br><br>typedef itk::ImageFileWriter< InputImageType > WriterSubjectType;<br> <br> WriterSubjectType::Pointer fixedsubjectfilterwriter = WriterSubjectType::New();<br>
<br> <span style="color: rgb(255, 0, 0);">//added these lines to fix the orientation problem</span><br> fixedsubjectfilterwriter->UseInputMetaDataDictionaryOff();<br> fixedsubjectfilterwriter->SetImageIO( gdcmImageIO );<br>
<span style="color: rgb(255, 0, 0);">//end of added code</span><br><br>fixedsubjectfilterwriter->SetFileName( "subjectout.dcm" );<br><br>fixedsubjectfilterwriter->SetInput( fixedsubjectfilter->GetOutput() );<br>
<br><br>try<br> {<br> fixedsubjectfilterwriter->Update();<br> }<br> catch (itk::ExceptionObject &ex)<br> {<br> std::cout << ex << std::endl;<br> return EXIT_FAILURE;<br>
}<br> }<br> catch (itk::ExceptionObject &ex)<br> {<br> std::cout << ex << std::endl;<br> return EXIT_FAILURE;<br> }<br><br><br><br>return EXIT_SUCCESS;<br>}<br><br>Thank you<br><br>john<br>
<br><div class="gmail_quote">On Tue, Oct 6, 2009 at 3:40 PM, Bill Lorensen <span dir="ltr"><<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I acknowledge that it is a bit magical.<br>
<div><div></div><div class="h5"><br>
On Tue, Oct 6, 2009 at 3:38 PM, John Drozd <<a href="mailto:john.drozd@gmail.com">john.drozd@gmail.com</a>> wrote:<br>
> Hi Bill,<br>
><br>
> Thanks. The code you sent steered me in the right direction to fix the<br>
> problem.<br>
><br>
> I added the following lines to my code which fixed the problem:<br>
><br>
> //added these lines to fix the orientation problem<br>
> fixedsubjectfilterwriter->UseInputMetaDataDictionaryOff();<br>
> fixedsubjectfilterwriter->SetImageIO( gdcmImageIO );<br>
> //end of added code<br>
><br>
> I suppose when writing a DICOM series to a DICOM volume, I had to set<br>
> UseInputMetaDataDictionaryOff()<br>
><br>
> Unfortunately, this was not in the example code<br>
> Examples/IO/DicomSeriesReadImageWrite2.cxx<br>
><br>
> But it was in<br>
> Examples/IO/DicomImageReadWrite.cxx<br>
><br>
> Thanks again Bill and Harvey for helping me.<br>
><br>
> Take care,<br>
> john<br>
><br>
><br>
><br>
><br>
> On Tue, Oct 6, 2009 at 11:55 AM, Bill Lorensen <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a>><br>
> wrote:<br>
>><br>
>> John,<br>
>><br>
>> I've attached some code thta passes the metat data dictionary from the<br>
>> input to the output. This example does a resample, bout you should do<br>
>> a similar thing in your program.<br>
>><br>
>> Bill<br>
>><br>
>> On Tue, Oct 6, 2009 at 11:38 AM, John Drozd <<a href="mailto:john.drozd@gmail.com">john.drozd@gmail.com</a>> wrote:<br>
>> > I have attached a screen capture of the Slicer views. The Slicer views<br>
>> > on<br>
>> > the left are the original DICOM series (that are not flipped and fine).<br>
>> > The<br>
>> > Slicer Views on the right are the outputted volume (after reading the<br>
>> > series<br>
>> > from memory) and are flipped. Note the -ve vs +ve values on the<br>
>> > sliders,<br>
>> > indicating the radiologist vs neurologist views.<br>
>> ><br>
>> > John<br>
>> ><br>
>> > On Tue, Oct 6, 2009 at 10:21 AM, John Drozd <<a href="mailto:john.drozd@gmail.com">john.drozd@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> I invoke the program with:<br>
>> >><br>
>> >> ./DeformableRegistration "param.file" "m000-talairach.dcm"<br>
>> >><br>
>> >> "/trumpet/downloads/DeformableRegistration_Plugin/DeformableRegistration/datasubject"<br>
>> >><br>
>> >> where the last item on the list is the name of the directory containing<br>
>> >> the dicom series.<br>
>> >><br>
>> >> john<br>
>> >><br>
>> >> On Tue, Oct 6, 2009 at 10:07 AM, John Drozd <<a href="mailto:john.drozd@gmail.com">john.drozd@gmail.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> Hi Bill,<br>
>> >>><br>
>> >>> Yes, I did read in the original DICOM series into 3D Slicer and the<br>
>> >>> original series was not flipped and fine. I was checking if ITK had<br>
>> >>> read<br>
>> >>> the series correctly into memory, so I wrote it to a volume. I was<br>
>> >>> writing<br>
>> >>> the volume out to see what was in memory and when I viewed the<br>
>> >>> outputted<br>
>> >>> volume in 3D Slicer it was flipped. In this case, I was basing my<br>
>> >>> code on<br>
>> >>> Examples/IO/DicomSeriesReadImageWrite2.cxx<br>
>> >>> I plan to today read in the series and write it to a series (instead<br>
>> >>> of a<br>
>> >>> volume) and see if the outputted series will be flipped (hopefully<br>
>> >>> not) when<br>
>> >>> I view it in 3D Slicer.<br>
>> >>> By the way, as shown in Examples/IO/DicomImageReadWrite.cxx, I did<br>
>> >>> read<br>
>> >>> in a dicom volume (a single file containing the talairach atlas) and<br>
>> >>> wrote<br>
>> >>> it out to another dicom volume and the outputted volume this time was<br>
>> >>> not<br>
>> >>> flipped when I viewed it in 3D Slicer.<br>
>> >>><br>
>> >>> Below is my code that I used for reading a dicom series and writing to<br>
>> >>> a<br>
>> >>> volume:<br>
>> >>> (It is part of a deformable registration program that I am writing<br>
>> >>> based<br>
>> >>> on Examples/Registration/DeformableRegistration1.cxx so there are some<br>
>> >>> header files and code from that)<br>
>> >>> The pertinent reading and writing code is in red. (about 60 lines<br>
>> >>> down)<br>
>> >>><br>
>> >>><br>
>> >>> #if defined(_MSC_VER)<br>
>> >>> #pragma warning ( disable : 4786 )<br>
>> >>> #endif<br>
>> >>><br>
>> >>><br>
>> >>> #include "itkImageFileReader.h"<br>
>> >>> #include "itkImageFileWriter.h"<br>
>> >>><br>
>> >>> #include "itkRescaleIntensityImageFilter.h"<br>
>> >>> #include "itkHistogramMatchingImageFilter.h"<br>
>> >>><br>
>> >>> //Added from DicomImageReadWrite.cxx<br>
>> >>> #include "itkGDCMImageIO.h"<br>
>> >>><br>
>> >>> //Added from DicomSeriesReadImageWrite2.cxx<br>
>> >>> #include "itkOrientedImage.h"<br>
>> >>> #include "itkGDCMImageIO.h"<br>
>> >>> #include "itkGDCMSeriesFileNames.h"<br>
>> >>> #include "itkImageSeriesReader.h"<br>
>> >>><br>
>> >>> #include "itkFEM.h"<br>
>> >>> #include "itkFEMRegistrationFilter.h"<br>
>> >>><br>
>> >>> // Next, we use \code{typedef}s to instantiate all necessary classes.<br>
>> >>> We<br>
>> >>> // define the image and element types we plan to use to solve a<br>
>> >>> // two-dimensional registration problem. We define multiple element<br>
>> >>> // types so that they can be used without recompiling the code.<br>
>> >>> //<br>
>> >>> //<br>
>> >>> // Note that in order to solve a three-dimensional registration<br>
>> >>> // problem, we would simply define 3D image and element types in lieu<br>
>> >>> // of those above. The following declarations could be used for a 3D<br>
>> >>> // problem:<br>
>> >>><br>
>> >>> typedef itk::Image<short, 3> fileImage3DType;<br>
>> >>> typedef itk::Image<short, 3> Image3DType;<br>
>> >>><br>
>> >>> typedef itk::fem::Element3DC0LinearHexahedronMembrane Element3DType;<br>
>> >>> typedef itk::fem::Element3DC0LinearTetrahedronMembrane<br>
>> >>> Element3DType2;<br>
>> >>><br>
>> >>> // Here, we instantiate the load types and explicitly template the<br>
>> >>> // load implementation type. We also define visitors that allow the<br>
>> >>> // elements and loads to communicate with one another.<br>
>> >>><br>
>> >>> typedef<br>
>> >>> itk::fem::FiniteDifferenceFunctionLoad<Image3DType,Image3DType><br>
>> >>> ImageLoadType;<br>
>> >>> template class itk::fem::ImageMetricLoadImplementation<ImageLoadType>;<br>
>> >>><br>
>> >>> typedef Element3DType::LoadImplementationFunctionPointer<br>
>> >>> LoadImpFP;<br>
>> >>> typedef Element3DType::LoadType<br>
>> >>> ElementLoadType;<br>
>> >>><br>
>> >>> typedef Element3DType2::LoadImplementationFunctionPointer<br>
>> >>> LoadImpFP2;<br>
>> >>> typedef Element3DType2::LoadType<br>
>> >>> ElementLoadType2;<br>
>> >>><br>
>> >>> typedef itk::fem::VisitorDispatcher<Element3DType,ElementLoadType,<br>
>> >>> LoadImpFP><br>
>> >>><br>
>> >>> DispatcherType;<br>
>> >>><br>
>> >>> typedef itk::fem::VisitorDispatcher<Element3DType2,ElementLoadType2,<br>
>> >>> LoadImpFP2><br>
>> >>><br>
>> >>> DispatcherType2;<br>
>> >>><br>
>> >>> // Once all the necessary components have been instantiated, we can<br>
>> >>> // instantiate the \doxygen{FEMRegistrationFilter}, which depends on<br>
>> >>> the<br>
>> >>> // image input and output types.<br>
>> >>><br>
>> >>> typedef itk::fem::FEMRegistrationFilter<Image3DType,Image3DType><br>
>> >>> RegistrationType;<br>
>> >>><br>
>> >>> int main(int argc, char *argv[])<br>
>> >>> {<br>
>> >>> char *paramname;<br>
>> >>> if ( argc < 2 )<br>
>> >>> {<br>
>> >>> std::cout << "Parameter file name missing" << std::endl;<br>
>> >>> std::cout << "Usage: " << argv[0] << " param.file" << "<br>
>> >>> atlas.file"<br>
>> >>> << " subject.file" <<std::endl;<br>
>> >>> return EXIT_FAILURE;<br>
>> >>> }<br>
>> >>> else<br>
>> >>> {<br>
>> >>> paramname=argv[1];<br>
>> >>> }<br>
>> >>><br>
>> >>> // The \doxygen{fem::ImageMetricLoad} must be registered before it<br>
>> >>> // can be used correctly with a particular element type. An example<br>
>> >>> // of this is shown below for ElementType. Similar<br>
>> >>> // definitions are required for all other defined element types.<br>
>> >>><br>
>> >>><br>
>> >>> // Register the correct load implementation with the element-typed<br>
>> >>> visitor dispatcher.<br>
>> >>> {<br>
>> >>> // Software Guide : BeginCodeSnippet<br>
>> >>> Element3DType::LoadImplementationFunctionPointer fp =<br>
>> >>><br>
>> >>><br>
>> >>> &itk::fem::ImageMetricLoadImplementation<ImageLoadType>::ImplementImageMetricLoad;<br>
>> >>> DispatcherType::RegisterVisitor((ImageLoadType*)0,fp);<br>
>> >>> // Software Guide : EndCodeSnippet<br>
>> >>> }<br>
>> >>> {<br>
>> >>> Element3DType2::LoadImplementationFunctionPointer fp =<br>
>> >>><br>
>> >>><br>
>> >>> &itk::fem::ImageMetricLoadImplementation<ImageLoadType>::ImplementImageMetricLoad;<br>
>> >>> DispatcherType2::RegisterVisitor((ImageLoadType*)0,fp);<br>
>> >>> }<br>
>> >>><br>
>> >>> // In order to begin the registration, we declare an instance of the<br>
>> >>> // FEMRegistrationFilter. For simplicity, we will call<br>
>> >>> // it \code{registrationFilter}.<br>
>> >>><br>
>> >>> RegistrationType::Pointer registrationFilter =<br>
>> >>> RegistrationType::New();<br>
>> >>><br>
>> >>> typedef short InputPixelType;<br>
>> >>> const unsigned int InputDimension = 3;<br>
>> >>><br>
>> >>> typedef itk::Image< InputPixelType, InputDimension > InputImageType;<br>
>> >>><br>
>> >>> typedef itk::ImageSeriesReader< InputImageType > ReaderSeriesType;<br>
>> >>><br>
>> >>><br>
>> >>> ReaderSeriesType::Pointer fixedsubjectfilter =<br>
>> >>> ReaderSeriesType::New();<br>
>> >>><br>
>> >>> typedef itk::GDCMImageIO ImageIOType;<br>
>> >>><br>
>> >>> ImageIOType::Pointer gdcmImageIO = ImageIOType::New();<br>
>> >>><br>
>> >>> fixedsubjectfilter->SetImageIO( gdcmImageIO );<br>
>> >>><br>
>> >>> typedef itk::GDCMSeriesFileNames NamesGeneratorType;<br>
>> >>> NamesGeneratorType::Pointer nameGenerator =<br>
>> >>> NamesGeneratorType::New();<br>
>> >>><br>
>> >>> nameGenerator->SetUseSeriesDetails( true );<br>
>> >>> nameGenerator->AddSeriesRestriction("0008|0021" );<br>
>> >>><br>
>> >>> nameGenerator->SetDirectory( argv[3] );<br>
>> >>><br>
>> >>> try<br>
>> >>> {<br>
>> >>> std::cout << std::endl << "The directory: " << std::endl;<br>
>> >>> std::cout << std::endl << argv[3] << std::endl << std::endl;<br>
>> >>> std::cout << "Contains the following DICOM Series: ";<br>
>> >>> std::cout << std::endl << std::endl;<br>
>> >>><br>
>> >>> typedef std::vector< std::string > SeriesIdContainer;<br>
>> >>><br>
>> >>> const SeriesIdContainer & seriesUID =<br>
>> >>> nameGenerator->GetSeriesUIDs();<br>
>> >>><br>
>> >>> //std::cout << seriesUID.begin() << endl;<br>
>> >>><br>
>> >>> SeriesIdContainer::const_iterator seriesItr = seriesUID.begin();<br>
>> >>> SeriesIdContainer::const_iterator seriesEnd = seriesUID.end();<br>
>> >>> while( seriesItr != seriesEnd )<br>
>> >>> {<br>
>> >>> std::cout << seriesItr->c_str() << std::endl;<br>
>> >>> seriesItr++;<br>
>> >>> }<br>
>> >>><br>
>> >>> std::string seriesIdentifier;<br>
>> >>><br>
>> >>> if( argc > 4 ) // If no optional series identifier<br>
>> >>> {<br>
>> >>> seriesIdentifier = argv[3];<br>
>> >>> }<br>
>> >>> else<br>
>> >>> {<br>
>> >>> seriesIdentifier = seriesUID.begin()->c_str();<br>
>> >>> }<br>
>> >>><br>
>> >>> std::cout << std::endl << std::endl;<br>
>> >>> std::cout << "Now reading series: " << std::endl << std::endl;<br>
>> >>> std::cout << seriesIdentifier << std::endl;<br>
>> >>> std::cout << std::endl << std::endl;<br>
>> >>><br>
>> >>> typedef std::vector< std::string > FileNamesContainer;<br>
>> >>> FileNamesContainer fileNames;<br>
>> >>><br>
>> >>> fileNames = nameGenerator->GetFileNames( seriesIdentifier );<br>
>> >>><br>
>> >>> fixedsubjectfilter->SetFileNames( fileNames );<br>
>> >>><br>
>> >>> try<br>
>> >>> {<br>
>> >>> fixedsubjectfilter->Update();<br>
>> >>> std::cout << "Subject read successfully" << std::endl;<br>
>> >>> }<br>
>> >>> catch (itk::ExceptionObject &ex)<br>
>> >>> {<br>
>> >>> std::cout << ex << std::endl;<br>
>> >>> return EXIT_FAILURE;<br>
>> >>> }<br>
>> >>><br>
>> >>> typedef itk::ImageFileWriter< InputImageType > WriterSubjectType;<br>
>> >>><br>
>> >>> WriterSubjectType::Pointer fixedsubjectfilterwriter =<br>
>> >>> WriterSubjectType::New();<br>
>> >>><br>
>> >>> fixedsubjectfilterwriter->SetFileName( "subjectout.dcm" );<br>
>> >>><br>
>> >>> fixedsubjectfilterwriter->SetInput( fixedsubjectfilter->GetOutput() );<br>
>> >>><br>
>> >>> try<br>
>> >>> {<br>
>> >>> fixedsubjectfilterwriter->Update();<br>
>> >>> }<br>
>> >>> catch (itk::ExceptionObject &ex)<br>
>> >>> {<br>
>> >>> std::cout << ex << std::endl;<br>
>> >>> return EXIT_FAILURE;<br>
>> >>> }<br>
>> >>> }<br>
>> >>> catch (itk::ExceptionObject &ex)<br>
>> >>> {<br>
>> >>> std::cout << ex << std::endl;<br>
>> >>> return EXIT_FAILURE;<br>
>> >>> }<br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> return EXIT_SUCCESS;<br>
>> >>> }<br>
>> >>><br>
>> >>><br>
>> >>> john<br>
>> >>><br>
>> >>> On Mon, Oct 5, 2009 at 7:09 PM, Bill Lorensen<br>
>> >>> <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a>><br>
>> >>> wrote:<br>
>> >>>><br>
>> >>>> 3D Slicer can read the DICOM directly. It will use the direction<br>
>> >>>> information properly. Why are you reading and writing it? I am<br>
>> >>>> suprised (and concerned) that 3D SLicer would flip the images.<br>
>> >>>><br>
>> >>>> Bill<br>
>> >>>><br>
>> >>>> On Mon, Oct 5, 2009 at 6:13 PM, John Drozd <<a href="mailto:john.drozd@gmail.com">john.drozd@gmail.com</a>><br>
>> >>>> wrote:<br>
>> >>>> > Hello,<br>
>> >>>> ><br>
>> >>>> > I am reading a brain subject in the form of a DICOM series using<br>
>> >>>> > ITK<br>
>> >>>> > and<br>
>> >>>> > writing it out from memory as a volume.<br>
>> >>>> > I used the method shown in<br>
>> >>>> > Examples/IO/DicomSeriesReadImageWrite2.cxx<br>
>> >>>> > I viewed the original DICOM series in 3D Slicer, and also viewed<br>
>> >>>> > the<br>
>> >>>> > outputted volume in 3D Slicer.<br>
>> >>>> > I am using 3D Slicer because I am developing a segmentation module<br>
>> >>>> > for<br>
>> >>>> > 3D<br>
>> >>>> > Slicer using ITK.<br>
>> >>>> > I noticed that the original DICOM series and the outputted volume<br>
>> >>>> > are<br>
>> >>>> > inverted in orientation, such that the original series is the<br>
>> >>>> > radiologist<br>
>> >>>> > view and the outputted volume is the neurosurgean view as per<br>
>> >>>> > <a href="http://www.itk.org/pipermail/insight-users/2009-June/031128.html" target="_blank">http://www.itk.org/pipermail/insight-users/2009-June/031128.html</a><br>
>> >>>> > and<br>
>> >>>> ><br>
>> >>>> ><br>
>> >>>> > <a href="http://www.itk.org/Wiki/Proposals:Orientation#DICOM_LPS_Differences_in_Visualization_presented_to_Radiologist_and_NeuroSurgeons" target="_blank">http://www.itk.org/Wiki/Proposals:Orientation#DICOM_LPS_Differences_in_Visualization_presented_to_Radiologist_and_NeuroSurgeons</a><br>
>> >>>> ><br>
>> >>>> > Does this have something to do with what I read on the internet<br>
>> >>>> > that<br>
>> >>>> > vtk's<br>
>> >>>> > images are flipped vertically from itk's images?<br>
>> >>>> > Is there a way to manipulate the image in memory using ITK so that<br>
>> >>>> > Slicer<br>
>> >>>> > will display the outputted volume in the same radiologist<br>
>> >>>> > orientation<br>
>> >>>> > as the<br>
>> >>>> > original DICOM series?<br>
>> >>>> ><br>
>> >>>> > Thank you.<br>
>> >>>> ><br>
>> >>>> > john<br>
>> >>>> ><br>
>> >>>> > --<br>
>> >>>> > John Drozd<br>
>> >>>> > Postdoctoral Fellow<br>
>> >>>> > Imaging Research Laboratories<br>
>> >>>> > Robarts Research Institute<br>
>> >>>> > Room 1256<br>
>> >>>> > 100 Perth Drive<br>
>> >>>> > London, Ontario, Canada<br>
>> >>>> > N6A 5K8<br>
>> >>>> > (519) 661-2111 ext. 25306<br>
>> >>>> ><br>
>> >>>> > _____________________________________<br>
>> >>>> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> >>>> ><br>
>> >>>> > Visit other Kitware open-source projects at<br>
>> >>>> > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>> >>>> ><br>
>> >>>> > Please keep messages on-topic and check the ITK FAQ at:<br>
>> >>>> > <a href="http://www.itk.org/Wiki/ITK_FAQ" target="_blank">http://www.itk.org/Wiki/ITK_FAQ</a><br>
>> >>>> ><br>
>> >>>> > Follow this link to subscribe/unsubscribe:<br>
>> >>>> > <a href="http://www.itk.org/mailman/listinfo/insight-users" target="_blank">http://www.itk.org/mailman/listinfo/insight-users</a><br>
>> >>>> ><br>
>> >>>> ><br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> --<br>
>> >>> John Drozd<br>
>> >>> Postdoctoral Fellow<br>
>> >>> Imaging Research Laboratories<br>
>> >>> Robarts Research Institute<br>
>> >>> Room 1256<br>
>> >>> 100 Perth Drive<br>
>> >>> London, Ontario, Canada<br>
>> >>> N6A 5K8<br>
>> >>> (519) 661-2111 ext. 25306<br>
>> >><br>
>> >><br>
>> >><br>
>> >> --<br>
>> >> John Drozd<br>
>> >> Postdoctoral Fellow<br>
>> >> Imaging Research Laboratories<br>
>> >> Robarts Research Institute<br>
>> >> Room 1256<br>
>> >> 100 Perth Drive<br>
>> >> London, Ontario, Canada<br>
>> >> N6A 5K8<br>
>> >> (519) 661-2111 ext. 25306<br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > John Drozd<br>
>> > Postdoctoral Fellow<br>
>> > Imaging Research Laboratories<br>
>> > Robarts Research Institute<br>
>> > Room 1256<br>
>> > 100 Perth Drive<br>
>> > London, Ontario, Canada<br>
>> > N6A 5K8<br>
>> > (519) 661-2111 ext. 25306<br>
>> ><br>
><br>
><br>
><br>
> --<br>
> John Drozd<br>
> Postdoctoral Fellow<br>
> Imaging Research Laboratories<br>
> Robarts Research Institute<br>
> Room 1256<br>
> 100 Perth Drive<br>
> London, Ontario, Canada<br>
> N6A 5K8<br>
> (519) 661-2111 ext. 25306<br>
><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>John Drozd<br>Postdoctoral Fellow<br>Imaging Research Laboratories<br>Robarts Research Institute<br>Room 1256<br>100 Perth Drive<br>London, Ontario, Canada<br>
N6A 5K8<br>(519) 661-2111 ext. 25306<br>