Hi Luis,<br><br>1 - I'm using PNG format to save.<br>2 - I'm using QImage from Qt (and I don't have other option by some project issues). For more details: I'm just extracting the slice and creating a QImage with the width and height that's are achieved from the GetLargestPossibleRegion().GetSize() on the extracted slice. After that, I'm using an image iterator to access the pixels populates the QImage.
<br><br>B) You are using an image viewer that does not take pixel<br> spacing into account.<br> Yes, this image viewer or the approach aren't taking pixel spacing in account. But, if I'm using VTK ( vtkImageReslice ) to extract slices, I can set the output spacing and the interpolation algorithm that's will be used. I think that's are a visualization task, but think that's are more safe if I'll use an algorithm or approach from the toolkit, and not just "stretch" the image by Qt ways. Then, have some approach using filters inside the toolkit (like VTK does) that's take in account the spacing values and returns to me an image that's I don't be care about spacing values? Of course, this image will be used only for visualization, and the original image will be intact to other processing tasks, like segmentation or registration.
<br><br>Thank's in advance,<br><br>Wagner Sales<br><br><div><span class="gmail_quote">2007/12/13, Luis Ibanez <<a href="mailto:luis.ibanez@kitware.com">luis.ibanez@kitware.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Hi Wagner,<br><br>Two Questions:<br><br><br>1) What fileformat did you used for saving the slice images ?<br><br>2) What image viewer (software) are you using to display these<br> resulting slice image files ?<br><br>
<br><br>It is very likely that:<br><br><br>A) you choose to save the image in a file format that does not<br> support pixel spacing (e.g. PNG, JPEG...)<br><br>and/or<br><br>B) You are using an image viewer that does not take pixel
<br> spacing into account.<br><br><br>As a verification, in your slice extraction code you can<br>add the call:<br><br><br> extractFilter->Update();<br> std::cout << "Input volume characteristics" << std::endl;
<br> extractFilter->GetInput()->Print( std::cout );<br> std::cout << "Output slice characteristics" << std::endl;<br> extractFilter->GetOutput()->Print( std::cout );<br><br><br>and with this output you should be able to verify if the
<br>original spacing of the image was respected on every slice.<br><br><br>Please let us know your answers to questions (1) and (2).<br><br><br> Thanks<br><br><br> Luis<br><br>------------------<br>Wagner Sales wrote:
<br>> Hi all,<br>><br>> I'm extracting slices from DICOM datasets em multiple axis (X, Y, Z) by<br>> using the ExtractImageFilter.<br>> The code are really simple, and based on the example provided in ITK
<br>> Software Guide.<br>> The slices in Z orientation (transversal) are fine, but the other axis (<br>> X and Y ) appears to be not ok. This axis have an aspect little bit<br>> compressed.<br>> I was saved this images by using the ImageWriter to be sure that's not a
<br>> problem in visualization, and the problems occurs too.<br>> I'm attaching a screen shot of the tree axis to illustrate this.<br>> Can anyone helps me?<br>><br>> Thks in advance,<br>><br>> Wagner Sales
<br>> ------------------------------------------------------------------------<br>><br>><br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________
<br>> Insight-users mailing list<br>> <a href="mailto:Insight-users@itk.org">Insight-users@itk.org</a><br>> <a href="http://www.itk.org/mailman/listinfo/insight-users">http://www.itk.org/mailman/listinfo/insight-users
</a><br></blockquote></div><br>