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

A Problem About Using SLAM Data as Gaussian Input #198

Open
yuyunlong2002 opened this issue Dec 28, 2024 · 0 comments
Open

A Problem About Using SLAM Data as Gaussian Input #198

yuyunlong2002 opened this issue Dec 28, 2024 · 0 comments

Comments

@yuyunlong2002
Copy link

I want to convert the map file generated by openvslam(*.msg) into colmap sparse point cloud file format (points3D.bin, images.bin, cameras.bin) as input for Gaussian Splatting, but the result generated by Gaussian is very bad.The point cloud generated by Gaussian Plating using SLAM results is very messy, especially on the Z-axis, the height is disordered.
This is the visualization result of my conversion of openvslam result to colmap format in GUI:
image
And this is the visualization result of colmap sparse reconstruction:
image

I believe that there are no errors in the position relationship between the camera and the point cloud in the conversion results.(Maybe I made some mistake^_^). From the two images above, it can be seen that colmap sparse reconstruction generates more point clouds. However, after downsampling the sparse point clouds generated by colmap, the results are also better than those generated by openvslam, so it should be possible to rule out the reason of the number of point clouds

This is the point cloud generated by me using the openvslam results for Gaussian generation:
image
image
And this is the point cloud I reconstructed using colmap for Gaussian generation:
image
image
It can be seen that the Colmap processing result is much better for GS than the openvslam result. I found that the Colmap result has 63 keyframes, while the openvslam result only has 54 keyframes. I have ruled out some possible reasons for the difference in effect, including the number of point clouds, point cloud color (Colmap sparse reconstruction result point cloud contains RGB information, openvslam result point cloud does not contain RGB information), error information (error mentioned in the Colamp Points3D file header), and TRACK information (track mentioned in the Colamp Points3D file header)
Can someone tell me which step went wrong?

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

1 participant