graphics - vtk projection matrix: from world to display -


i'm trying obtain 4x4 projection matrix transforms point in world display coordinates.

having pixel (x, y) , corresponding z-value (from zbuffer), obtain 3d world coordinates vtkworldpointpicker class. let's denote result x.

according documentation, can compute view coordinates of world point applying matrix getcompositeprojectiontransformmatrix x. next, i'm using transformation view initial display coordinates using code found in vtkviewport::viewtodisplay (*):

dx = (v[0] + 1.0) * (sizex*(v[2]-v[0])) / 2.0 + sizex*v[0]; dy = (v[1] + 1.0) * (sizey*(v[3]-v[1])) / 2.0 + sizey*v[1];

where sizex , sizey width , height of image in pixels, , v computed view coordinates.

unfortunately, values not match original:

display [0, 0, 0.716656] // x,y-pixel coordinates , zbuffer x = [0.0255492, -0.0392383, 0.00854707] // world coordinates  (using vtkworldpointpicker)  // camera->getcompositeprojectiontransformmatrix p = [  -1.84177         0         0         0         0   1.20317   1.39445         0         0  -757.134   653.275   -9.9991         0 -0.757126  0.653268         0 ]  v = [-0.0470559, -0.0352919, 25.2931, 0.0352919] // p*x = [7697.18, -0.597848] // using (*)

is approach (in general) correct, or there more conventional way this? help.

edit: provided snippet vtkviewport::viewtodisplay incorrect. should read:

dx = (v[0] + 1.0) * (sizex*(vp[2]-vp[0])) / 2.0 + sizex*vp[0]; dy = (v[1] + 1.0) * (sizey*(vp[3]-vp[1])) / 2.0 + sizey*vp[1];

note, v refers normalised view coordinates, vp viewport (by default, vp := [0, 0, 1, 1])!

the conversion indeed valid, although there might built-in ways obtain final matrix.

assuming 1 (default) viewport used, matrix converting view display coordinates is:

m = [x/2,   0, 0, x/2,        0, y/2, 0, y/2,        0,   0, 1,   0,        0,   0, 0,   1]

where x , y width , height of image in pixels. hence, given point x in world coordinates, display coordinates in homogeneous form are:

c = m * p * x;

where p compositeprojectiontransformmatrix. after normalising (c[i] /= c[3], i = 0,1,2) arrive @ original pixel values.


-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more