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

W2C and extrinsics #81

Closed
haowang020110 opened this issue Nov 29, 2024 · 2 comments
Closed

W2C and extrinsics #81

haowang020110 opened this issue Nov 29, 2024 · 2 comments

Comments

@haowang020110
Copy link

Dear author
Sorry I have a name problem
It seemed that the normal conception of the camera extrinsics is w2c matrix.
However you made extrinsics=c2w, can you tell me the reason?
Sorry again for my poor knowledge.

w2c = repeat(torch.eye(4, dtype=torch.float32), "h w -> b h w", b=b).clone()
w2c[:, :3] = rearrange(poses[:, 6:], "b (h w) -> b h w", h=3, w=4)
return w2c.inverse(), intrinsics

@donydchen
Copy link
Owner

Hi, @haowang020110, there is no specific reason for using c2w or w2c. The main reason might be the encoder involves some operations that are easier to start from camera space, e.g., the wrapping operation (#80), and the encoder predicts 3D Gaussians in camera space, which is then transformed into world space. Hence, it seems more convenient to use c2w in this project.

@haowang020110
Copy link
Author

Thanks a lot!

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

2 participants