-
Notifications
You must be signed in to change notification settings - Fork 56
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
Inconsistent extrinsics #20
Comments
This should be the right way to do it, yes. What do you mean it's not consistent? There could be some variations in extrinsics between scenes, since the vehicle is recalibrated, is that the case? |
I see. Weird then, because I used such extrinsics to compute the so-called "non-overlapping" masks (with pretrained depth and pose), but those masks are always zero. Any suggestion on how the cross-view photometric loss should be computed? |
Maybe @ivasiljevic can shed some light on this as he looked into this most recently. |
I tried to find the world coord pointcloud of all views and merge them, but, the view pointclouds are not matched, I think the reason is about extrinsic matrix |
I think the right way should be T_cam1tocam5 = data_cam5["extrinsics"] @ np.linalg.inv(data_cam1["extrinsics"]) |
I tried two ways to build T_cam1tocam5. T_cam1tocam5 = np.linalg.inv(data_cam5["extrinsics"]) @ data_cam1["extrinsics"] can get right cross-view synthesis result. But in theory, the right T_cam1tocam5 should be data_cam5["extrinsics"] @ np.linalg.inv(data_cam1["extrinsics"]). So I got confused. Maybe the provided "extrinsics" is the inverse of tranformation matrix, i.e. T_wc? |
Hi,
Could you advise how to compute the extrinsics between the cameras? I tried this way:
T_cam1tocam5 = np.linalg.inv(data_cam5["extrinsics"]) @ data_cam1["extrinsics"].
Is this the right way?
If this is right, then why the transformation is not consistent across different sequences?
Thanks.
The text was updated successfully, but these errors were encountered: