-
Notifications
You must be signed in to change notification settings - Fork 559
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
can I fix the camera pose? Or given some restrictive priors #30
Comments
Hello @kuaiqushangzixiba dust3r/dust3r/cloud_opt/optimizer.py Line 66 in 517a430
The same can be done with focals and principal points dust3r/dust3r/cloud_opt/optimizer.py Line 82 in 517a430
dust3r/dust3r/cloud_opt/optimizer.py Line 91 in 517a430
Note that if you only care about having all reconstructions living in the same reference frame, you can get the output camera poses and parameters after processing the first sequence and set them manually for the rest of the reconstructions. Note that setting inaccurate camera poses might hinder the quality of the output in some cases. Best |
Line 91 in 517a430
return _convert_scene_output_to_glb(outdir, rgbimg, pts3d, msk, focals, cams2world, as_pointcloud=as_pointcloud, transparent_cams=transparent_cams, cam_size=cam_size) Thanks a lot! |
And when I set preset_pose(), I got the following error, I found that the declaration of this method was not defined in the code AttributeError: 'PointCloudOptimizer' object has no attribute '_get_msk_indices' |
A very good job! I have a fixed use of the scene, 4 cameras fixed to shoot an object, but I find that each time the output camera is not in the same position, can you give some prior conditions or modify the code to fix the camera pose?
The text was updated successfully, but these errors were encountered: