No worries.
I might have a look at it next Wednesday. But I cannot promise you anything.
These geometries things are really complex and it might take a while. Of course
you can also give it a try and let me know, if you find out something.
The problem is probably somewhere in the creation of the world geometry. The
world geometry is a geometry, that is fully containing all currently existing
geometries. Out of the world geometry the renderwindows are fed. I would begin
the search by looking where the function
void mitk::BaseRenderer::SetCurrentWorldGeometry(mitk::Geometry3D* geometry)
is called. Yah, but well, as I said it is not a trivial thing.. I spent some
sleepless nights over these things.
Regards,
Bastian
Von: Clarkson, Matt [mailto:[email protected]]
Gesendet: Freitag, 18. Mai 2012 10:40
An: Graser, Bastian
Cc: mitk-users
Betreff: Re: AW: Image Geometry & half voxel shift - Problem?
Thanks!
I don't want to say "it's really urgent", as anyone would say that :-) so
lets just say ... I'm really interested in the outcome of this :-)
If you could let me know any timescales as soon as you have them, and I can try
to help out where possible.
However, it's such a significant part of functionality, I would hesitate to
start attacking the code myself.
Thanks as always.
Matt
On 18 May 2012, at 09:25, Graser, Bastian wrote:
Hi Matt,
This is a very interesting observation. After some consideration time, I would
say your expectations are correct. Yet, I need to consult with some other
experts on that topic. If they approve your expectations as well, we will write
a bug-report for that and try to fix it sometime soon.
Thank you for the detailed description, this is very helpful!
Regards,
Bastian
Von: Clarkson, Matt
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
Gesendet: Donnerstag, 17. Mai 2012 10:58
An: mitk-users
Betreff: [mitk-users] Image Geometry & half voxel shift - Problem?
Hi Everyone,
I have a problem whereby I am seeing a half voxel shift in my millimetre to
voxel calculations, and I believe the following example using this mornings
build of ExtApp illustrates it.
I have a 3x3 test image with voxel size 2mm x 2mm, and a 5x5 test image with
voxel sizes 1mm x 1mm.
The origin for both images should be the centre of the first voxel.
If I load JUST the 3x3 image, the geometry as expected. The first voxel has
index 0,0 and millimetre location 0,0.
If I load JUST the 5x5 image, again, it is as expected.
If I load BOTH the 3x3 and the 5x5 I would expect the smaller 5x5 image to be
centred symmetrically within the 3x3 image, and this is not the case. It looks
like the corners are aligned rather than the centre of the first voxel.
Please find attached my 3x3 image and 5x5 image, and some screenshots.
In the screenshots
first screenshot = 3x3 image = OK
second screenshot = 5x5 image = OK
third screenshot = overlay = PROBLEM????
fourth screenshot = my expectation.
Did I do something wrong, or it my expected behaviour wrong?
Many thanks
Matt
<image001.png>
------------------------------------------------------
Matt Clarkson Ph.D.
CMIC Software Manager
Senior Research Associate
[email protected]<mailto:[email protected]>
Skype: drmattclarkson
Centre For Medical Image Computing
http://cmic.cs.ucl.ac.uk/staff/matt_clarkson/<http://cmic.cs.ucl.ac.uk/>
Tel: 020 7679 0177
Fax: 020 7679 0255
Dementia Research Centre
http://dementia.ion.ucl.ac.uk/
Tel: 08451 555 000 ext. 723653
Fax: 020 7676 2066
------------------------------------------------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
