[ITK] An important question about intensity rescale of dicom images
Lambert Zijp
ljzijp at gmail.com
Mon Mar 28 04:54:37 EDT 2016
Hi Tommi,
If those images are CT, it might be that the pixelvalues are converted to
Hounsfield units: the pixelvalues are shifted so that 'air' equals -1000.
Using the reader with *signed short* would then solve your problem.
Greetings,
Lambert
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=oa-2115-v2-b>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=oa-2115-v2-b>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Mon, Mar 28, 2016 at 5:45 AM, penitentepid epid <penitentepid at gmail.com>
wrote:
> Hi, ITK group
>
> I have bunch of 12 bits dicom images whose intensity ranges from 0 to
> 4095. (found in dicom header, bitsStoed =12, highBits = 11, pixel
> representation = 0)
> when i used image reader <unsigned short,2>, i got a image whose pixel
> intensity are ranging from 0 to 65535. why does this happen? i mean i
> understand unsigned short is in this range, but did itk internally rescale
> image intensity somehow?
>
> why not put highest of pixel intensity as it suppose to be (4095 in this
> case), and leave rest bits to be zeroes..
>
> tommi.
>
> _______________________________________________
> Community mailing list
> Community at itk.org
> http://public.kitware.com/mailman/listinfo/community
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/community/attachments/20160328/81a9d247/attachment.html>
More information about the Community
mailing list