You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2020. It is now read-only.
Just earlier, I accidentally introduced a bug where I found the cosine distance of a bearing and a world point. Unfortunately, this was incorrect. I needed to transform the world point into the camera space first before computing the cosine distance for the purpose of filtering the point.
Also, a common thing to do is to compute this projection error as cosine distance via: 1.0 - bearing.dot(&view_point.bearing()).
Solution
We need to create a projection_error or similarly named method on the Bearing or CameraPoint. It can also be on both, so long as one simply calls the other.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Justifications
Just earlier, I accidentally introduced a bug where I found the cosine distance of a bearing and a world point. Unfortunately, this was incorrect. I needed to transform the world point into the camera space first before computing the cosine distance for the purpose of filtering the point.
Also, a common thing to do is to compute this projection error as cosine distance via:
1.0 - bearing.dot(&view_point.bearing())
.Solution
We need to create a
projection_error
or similarly named method on theBearing
orCameraPoint
. It can also be on both, so long as one simply calls the other.The text was updated successfully, but these errors were encountered: