-
Notifications
You must be signed in to change notification settings - Fork 15
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
3d Projective geometry warping using ground truth depth and pose is not working #6
Comments
For example, I'm considering frames 1 and 2 of The corresponding camera poses are below
I've attached the frame1, frame2 and frame2_warped (frame1 warped to the view of frame2). Ideally, frame2_warped should match with frame2 (except for the object motions). Am I missing something? |
It looks like the polarity of the transform you are doing is somehow reversed? Shouldn't frame2_warped be more zoomed in than the original frame1? You could try using the visualization script at https://github.com/oscarmcnulty/gta-3d-dataset/blob/master/test_vis.py to debug? |
Thanks for the lightning-quick reply. That was my thought too. So, I tried changing the sign of the z-translation after computing the relative transformation. Though the camera zoomed into the scene, the amount of zooming was very small compared to frame2. So, I thought something else might be wrong. Can you please confirm if my computation of depth, camera intrinsic, and camera poses is correct? |
Hi,
Thanks for sharing your database. I'm trying to use the database in a view synthesis related task.
Given two frames, I'm trying to reconstruct one from the other using 3d projective geometry based warping from here.
For depth, I'm using the your code to get disparity map and then compute depth map as
1/disparity
and clipping max value to 0For camera poses, I'm using the
viewMatrix
you've provided in the json files.I'm constructing the camera intrinsic using the fov you've mentioned: 50
However, the reconstructed image is not matching with the rendered image.
The text was updated successfully, but these errors were encountered: