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

Question about camera parameter estimation in 3DTRL #1

Open
saltwaterroon opened this issue Aug 9, 2023 · 2 comments
Open

Question about camera parameter estimation in 3DTRL #1

saltwaterroon opened this issue Aug 9, 2023 · 2 comments

Comments

@saltwaterroon
Copy link

Hello, thanks for your great work and code release! I've successfully trained 3DTRL on DeiT-S and achieved 79.8% accuracy, which aligns with the results in your paper. However, I've observed an unusual pattern in camera parameter estimation. Rotation and translation tensors appear nearly identical for each input image, as shown in the attached figure. Is this correct? Could you provide insights into this? Have you encountered a similar phenomenon?
image

@elicassion
Copy link
Owner

Hi @saltwaterroon ,

I think what you observed is similar to mine. Since we train those estimations without supervision, and the ImageNet dataset is not designed for multi-view inputs, the estimated parameters only have little differences. If you can numerically check them instead of printing, you will notice differences between them.

Again, since it is done without any supervision, we don't expect it to produce exact estimations. Some correlations / differences might be enough for the model.

@saltwaterroon
Copy link
Author

Thank you for your assistance. I took your advice and did observe slight numerical differences in the output values, but they were indeed quite minimal. And the rotation tensor tends to approximate zero for most input images. However, in Figure 9 of your visualization, it appears that the camera parameter estimations exhibit significant variation for different input images. Since the differences I've observed are relatively small, I'm curious about the methods or factors that lead to such distinctions in the visual representation.
I would appreciate it if you could provide any further clarification.

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