search

nagyistoce / platinum-image

Automatically exported from code.google.com/p/platinum-image
0 stars 0 forks source link

New coordinate system #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The current coordinate system for locating lookat points has certain 
deficiencies:
1. images are assumed to have corresponding geometry
2. the coordinate system does not correlate to voxel positions, which can make 
it hard to access 
each slice

Original issue reported on code.google.com by arvi...@gmail.com on 10 May 2007 at 2:13

GoogleCodeExporter commented 9 years ago 
Images currently tend to be underscaled when initially displayed. Consider these
solutions:
1. scale for min-fit instead of max fit
2. scale to a specific voxel-pixel ration instead of image dimensions

Original comment by arvi...@gmail.com on 28 May 2007 at 12:31

GoogleCodeExporter commented 9 years ago 
Specs:
1. view multiple images with positioning & orientation
2. view multiple images sans positioning but with matching dimensions

Original comment by arvi...@gmail.com on 5 Jun 2007 at 12:29

GoogleCodeExporter commented 9 years ago

Original comment by arvi...@gmail.com on 18 Jun 2007 at 9:37

GoogleCodeExporter commented 9 years ago

Original comment by arvi...@gmail.com on 1 Aug 2007 at 10:44

GoogleCodeExporter commented 9 years ago 
The world (mm) coordinate system is implemented in r. 332, with
* image coordinates correctly displayed
the following aspects untested:
* Oblique image orientation
* image value display (tested, not working correctly)
* voxel size import from DICOM

Original comment by arvi...@gmail.com on 1 Aug 2007 at 5:27

GoogleCodeExporter commented 9 years ago 
r. 333 adds pageup/down stepping through image voxel by voxel

Original comment by arvi...@gmail.com on 1 Aug 2007 at 7:37

GoogleCodeExporter commented 9 years ago 
All features have been added, only testing remains on this issue

Original comment by arvi...@gmail.com on 2 Aug 2007 at 12:15

GoogleCodeExporter commented 9 years ago

Original comment by arvi...@gmail.com on 3 Aug 2007 at 5:27

GoogleCodeExporter commented 9 years ago

Original comment by arvi...@gmail.com on 3 Aug 2007 at 5:29

GoogleCodeExporter commented 9 years ago 
The initial size of an opened image is too large to fit the window.

Original comment by petter.r...@gmail.com on 7 Aug 2007 at 6:46

GoogleCodeExporter commented 9 years ago 
How is the value for display_scale selected? I have found that a value of 250 
would 
make the initial size more suitable than the current value of 25. But this 
seems to 
influence the number of slices when you scroll through the slices.

Original comment by petter.r...@gmail.com on 7 Aug 2007 at 4:14

GoogleCodeExporter commented 9 years ago 
The value for renderer_base::display_scale is the number of mm:s displayed in a 
window at zoom 1. The 
"suitable size" will vary for each image depending on the subject's actual size.
Solution in r. 390: zoom value is adjusted when assigning an added image to a 
new viewport to encompass the 
entire image (including z)

Original comment by arvi...@gmail.com on 14 Aug 2007 at 10:08