| Problem with IDLffDicomEx::SetPixelData [message #77077] |
Mon, 01 August 2011 07:24  |
Vivek
Messages: 6
Registered: July 2011
|
Junior Member |
|
|
Hello,
I am facing issues with IDLffDicomEx::SetPixelData when it comes to
assigning pixel intensity values to the DICOM file. While it works
fine in assigning it basically, it's not faithfully reproducing the
image correctly, and is sort of distorting/thresholding the image. I
am having to convert the image to uint type or fix type before storing
it, as it does not allow me to store float values.
When I try and store the float type, I get an error saying that the
input pixel data array is not equal to the total number of frames in
the image, but when I convert the same to uint or fix type, it works
fine, albeit distorting/thresholding the image. Any suggestions on how
to correct this?
Vivek
|
|
|
|
| Re: Problem with IDLffDicomEx::SetPixelData [message #77154 is a reply to message #77077] |
Tue, 02 August 2011 13:02  |
rtk
Messages: 22
Registered: September 2008
|
Junior Member |
|
|
On Aug 1, 8:24 am, Vivek <vivek.rajshek...@gmail.com> wrote:
> Hello,
>
> I am facing issues with IDLffDicomEx::SetPixelData when it comes to
> assigning pixel intensity values to the DICOM file. While it works
> fine in assigning it basically, it's not faithfully reproducing the
> image correctly, and is sort of distorting/thresholding the image. I
> am having to convert the image to uint type or fix type before storing
> it, as it does not allow me to store float values.
>
> When I try and store the float type, I get an error saying that the
> input pixel data array is not equal to the total number of frames in
> the image, but when I convert the same to uint or fix type, it works
> fine, albeit distorting/thresholding the image. Any suggestions on how
> to correct this?
>
> Vivek
This sounds like an incompatibility between the image parameters
(number of bits, bits allocated, high bit, etc) and the actual data
you are passing in. If you can show us how you are setting these
values and then print the type of the data array you are passing
things might become clear. I suspect IDL is truncating the data based
on these values.
Ron
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
