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
Hello, I got a question regarding the ball radius.
In camera.py the ray directions are normalized, hence t values (and distances) are in euclidean space. But the radii are computed on the image plane w.r.t. the unnormalized distances. Shouldn't the radii also be scaled by 1 / ||directions|| before the directions are normalized so you get the radii on the unit sphere?
Greets!
The text was updated successfully, but these errors were encountered:
Hello, I got a question regarding the ball radius.
In camera.py the ray directions are normalized, hence t values (and distances) are in euclidean space. But the radii are computed on the image plane w.r.t. the unnormalized distances. Shouldn't the radii also be scaled by 1 / ||directions|| before the directions are normalized so you get the radii on the unit sphere?
Greets!
I have the same question , i ’m looking forward to relative reply!
The radii are comupted on a virtual imaging plane with a depth value (coordinate along z-axis) as 1 w.r.t. the camera frame. No matter whether rays are normalized or not, this unit depth value has defined coordinates of these pixels.
Hello, I got a question regarding the ball radius.
In camera.py the ray directions are normalized, hence t values (and distances) are in euclidean space. But the radii are computed on the image plane w.r.t. the unnormalized distances. Shouldn't the radii also be scaled by 1 / ||directions|| before the directions are normalized so you get the radii on the unit sphere?
Greets!
The text was updated successfully, but these errors were encountered: