Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] From v3Pixel{Down, Right}_NC to v3Pixel{Down, Right}_W #3

Open
ghost opened this issue Mar 22, 2014 · 1 comment
Open

[Question] From v3Pixel{Down, Right}_NC to v3Pixel{Down, Right}_W #3

ghost opened this issue Mar 22, 2014 · 1 comment

Comments

@ghost
Copy link

ghost commented Mar 22, 2014

The transform is performed in MapPoint::RefreshPixelVector()
https://github.com/Oxford-PTAM/PTAM-GPL/blob/master/Src/MapPoint.cc

  double dPixelRate = fabs(v3Center_NC * v3Normal_NC);
  double dOneRightRate = fabs(v3OneRightFromCenter_NC * v3Normal_NC);
  double dOneDownRate = fabs(v3OneDownFromCenter_NC * v3Normal_NC);

I checked the code in MapMaker. The v3Normal_NC is always initialized with(0, 0, -1). My question is why v3OneRightFromCenter_NC, v3Normal_NC, v3OneDownFromCenter_NC are not orthogonal to each other? Then the dot product calculated above are zeros.

  Vector<3> v3CenterOnPlane_C = v3Center_NC * dCamHeight / dPixelRate;
  Vector<3> v3OneRightOnPlane_C = v3OneRightFromCenter_NC * dCamHeight / dOneRightRate;
  Vector<3> v3OneDownOnPlane_C = v3OneDownFromCenter_NC * dCamHeight / dOneDownRate;

Is there an picture to explain how this transform is done?

Best regards,
Tyler

@ghost
Copy link
Author

ghost commented Mar 22, 2014

[Solved]
I think I understand now.
illustration

v3OneRightFromCenter_NC
v3Center_NC

are the blue unit vectors.

v3CenterOnPlane_C
v3OneRightOnPlane_C

are the long black and red vectors.

Is that correct?

Best regards,
Tyler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants