We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
I evaluated the same image pair using both NVS.pth and geometry_pose.pth based on:
NVS.pth
geometry_pose.pth
sh scripts/run_eval_nvs.sh sh scripts/run_eval_geometry_pose.sh
However, the predicted pointmap from NVS.pth is significantly worse than that from geometry_pose.pth.
Below are the visual comparisons:
Left column: Top and front views from NVS.pth
Right column: Top and front views from geometry_pose.pth
Let me know if I missed any required configuration when using NVS.pth, or if this behavior is expected.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
I evaluated the same image pair using both
NVS.pth
andgeometry_pose.pth
based on:However, the predicted pointmap from
NVS.pth
is significantly worse than that fromgeometry_pose.pth
.Below are the visual comparisons:
Left column: Top and front views from
NVS.pth
Right column: Top and front views from
geometry_pose.pth
Let me know if I missed any required configuration when using
NVS.pth
, or if this behavior is expected.The text was updated successfully, but these errors were encountered: