Printable View
Hi, everybody ...
I read, at page 291, PS3.3-2006 (Information Objet Definitions) that,
for US images
e.g.
V=0.30 mm, H=0.25mm
Pixel Aspect Ratio = Vertical Size\Horizontal Size = 0.30mm \0.25 mm
Thus the Pixel Aspect Ratio could be represented as the string "6\5",
or "60\50" or any equivalent integer ratio.
OK.
"12\10", should work, too, right?
How can I deduce that the Spacing is 0.3 * 0.25, and not 0.6*0.5?
Any information welcome.
Jean-Pierre Roux
[email]jpr@creatis.univ-lyon1.fr[/email] wrote:
[color=blue]
> "12\10", should work, too, right?
> How can I deduce that the Spacing is 0.3 * 0.25, and not 0.6*0.5?[/color]
After browsing the archive, the only answer that actually make sense is
one made by D. Clunie:
[url]http://groups.google.com/group/comp.protocols.dicom/msg/2964be122b4ccdc2?hl=en&[/url]
....
I think it is also fairly unusual for viewers and displays
to handle non-square pixels "properly" anyway.
....
The best approach could be to simply set spacing of 1\1 and produce a
warning.
Mathieu
Mathieu Malaterre wrote:[color=blue]
> [email]jpr@creatis.univ-lyon1.fr[/email] wrote:
>[color=green]
> > "12\10", should work, too, right?[/color][/color]
Yes, of course.
[color=blue][color=green]
> > How can I deduce that the Spacing is 0.3 * 0.25, and not 0.6*0.5?[/color][/color]
You can't. The ratio is less information than the pair of pixel
spacings.
[color=blue]
>
> After browsing the archive, the only answer that actually make sense is
> one made by D. Clunie:
> [url]http://groups.google.com/group/comp.protocols.dicom/msg/2964be122b4ccdc2?hl=en&[/url]
>
> ...
> I think it is also fairly unusual for viewers and displays
> to handle non-square pixels "properly" anyway.
> ...[/color]
That's a bit pessimistic! You can easily get non-square pixels by
doing MPR; imagine an axial CT with 0.5 mm square pixels and 1mm slice
separation -- the orthogonal views will have 0.5 mm by 1 mm pixels.
Our viewer handles them fine. I'd be shocked if other commercial
viewers did not.
-Steve
As a matter of fact, our customers have had numerous occasions where
non-square pixels were not being displayed correctly. Specifically,
the other vendors were only using Pixel Aspect Ratio, which works for
most of the IODs out there. But, CT/MR/PET... use Pixel Spacing, not
Pixel Aspect Ratio, which means that the images that were displayed
looked "squished"... Ultimately, we were forced to "fix" our images,
and make our pixels square, to satisfy the customer complaints.
Steve Robbins wrote:[color=blue]
> Mathieu Malaterre wrote:[color=green]
> > [email]jpr@creatis.univ-lyon1.fr[/email] wrote:
> >[color=darkred]
> > > "12\10", should work, too, right?[/color][/color]
>
> Yes, of course.
>[color=green][color=darkred]
> > > How can I deduce that the Spacing is 0.3 * 0.25, and not 0.6*0.5?[/color][/color]
>
> You can't. The ratio is less information than the pair of pixel
> spacings.
>[color=green]
> >
> > After browsing the archive, the only answer that actually make sense is
> > one made by D. Clunie:
> > [url]http://groups.google.com/group/comp.protocols.dicom/msg/2964be122b4ccdc2?hl=en&[/url]
> >
> > ...
> > I think it is also fairly unusual for viewers and displays
> > to handle non-square pixels "properly" anyway.
> > ...[/color]
>
> That's a bit pessimistic! You can easily get non-square pixels by
> doing MPR; imagine an axial CT with 0.5 mm square pixels and 1mm slice
> separation -- the orthogonal views will have 0.5 mm by 1 mm pixels.
> Our viewer handles them fine. I'd be shocked if other commercial
> viewers did not.
>
> -Steve[/color]
> ...[color=blue]
> I think it is also fairly unusual for viewers and displays
> to handle non-square pixels "properly" anyway.
> ...[/color]
I would just add that I think it is very poor engineering (an
understatement..., I could have been more blunt) to NOT handle it
properly. It is just a matter of interpolation to make them square. I
just don't want to get people the impression that it is OK not to
display these images correctly.
Herman O.
[email]dmcnamara@vitalimages.com[/email] wrote:[color=blue]
> As a matter of fact, our customers have had numerous occasions where
> non-square pixels were not being displayed correctly. Specifically,
> the other vendors were only using Pixel Aspect Ratio, which works for
> most of the IODs out there. But, CT/MR/PET... use Pixel Spacing, not
> Pixel Aspect Ratio, which means that the images that were displayed
> looked "squished"... Ultimately, we were forced to "fix" our images,
> and make our pixels square, to satisfy the customer complaints.
>
> Steve Robbins wrote:[color=green]
> > Mathieu Malaterre wrote:[color=darkred]
> > > [email]jpr@creatis.univ-lyon1.fr[/email] wrote:
> > >
> > > > "12\10", should work, too, right?[/color]
> >
> > Yes, of course.
> >[color=darkred]
> > > > How can I deduce that the Spacing is 0.3 * 0.25, and not 0.6*0.5?[/color]
> >
> > You can't. The ratio is less information than the pair of pixel
> > spacings.
> >[color=darkred]
> > >
> > > After browsing the archive, the only answer that actually make sense is
> > > one made by D. Clunie:
> > > [url]http://groups.google.com/group/comp.protocols.dicom/msg/2964be122b4ccdc2?hl=en&[/url]
> > >
> > > ...
> > > I think it is also fairly unusual for viewers and displays
> > > to handle non-square pixels "properly" anyway.
> > > ...[/color]
> >
> > That's a bit pessimistic! You can easily get non-square pixels by
> > doing MPR; imagine an axial CT with 0.5 mm square pixels and 1mm slice
> > separation -- the orthogonal views will have 0.5 mm by 1 mm pixels.
> > Our viewer handles them fine. I'd be shocked if other commercial
> > viewers did not.
> >
> > -Steve[/color][/color]