Mercurial > hg > orthanc-stone

comparison OrthancStone/Resources/Documentation/Coordinates.txt @ 1779:9ab251c03eda

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
unit test VolumeRendering.TextureCorners
author Sebastien Jodogne <s.jodogne@gmail.com>
date Fri, 14 May 2021 10:01:20 +0200
parents fca942f4b4a7
children 20a0aba0ede5
comparison
equal deleted inserted replaced
1778:de5c965f0697 1779:9ab251c03eda
11 patient coordinates to gantry coordinates, but this would be useful 11 patient coordinates to gantry coordinates, but this would be useful
12 to device manufacturers, whereas Stone primarly deals with users of 12 to device manufacturers, whereas Stone primarly deals with users of
13 modalities. 13 modalities.
14 14
15 * The "Image Position Patient" gives the 3D coordinates of the CENTER 15 * The "Image Position Patient" gives the 3D coordinates of the CENTER
16 of the voxel of slice. 16 of the top-left voxel of slice.
17 17
18 * In 2D compositors, the origin of a texture corresponds to the CORNER 18 * In 2D compositors, the origin of a texture corresponds to the CORNER
19 of the texture (*not* to the center of the first pixel). Roughly 19 of the top-left pixel of the texture (*not* to the center of this
20 speaking, the operation "floor()" must be applied to move from 20 pixel). Roughly speaking, the operation "floor()" must be applied to
21 floating coordinates to pixel coordinates. 21 move from canvas coordinates (floating-point numbers) to pixel
22 coordinates in the image buffer (integer numbers).
22 23
23 * The classes deriving from "IVolumeSlicer" must pay to attention to 24 * The classes deriving from "IVolumeSlicer" must pay to attention to
24 convert from centers of 3D voxels to bounding boxes of 2D pixels. 25 convert from centers of 3D voxels to bounding boxes of 2D pixels.