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

About the ply file #49

Open
ZhenyuSun-Walker opened this issue Sep 11, 2024 · 8 comments
Open

About the ply file #49

ZhenyuSun-Walker opened this issue Sep 11, 2024 · 8 comments

Comments

@ZhenyuSun-Walker
Copy link

Hello sir, I'm sorry to bother you. But I found that it can be tricky to adjust the ply file format to match the dataset_reader of your model. Which kind of .ply file can be processed by MVSGS? I'm quite confused with that.

@TQTQliu
Copy link
Owner

TQTQliu commented Sep 12, 2024

Hi, the point cloud obtained by colmap can be also used as initialization. I'm not quite sure why your point cloud doesn't work, perhaps you could provide some additional information.

@ZhenyuSun-Walker
Copy link
Author

Actually, I use the ply generated from the Dust3R, however, I cannot find the exact difference between its ply file and the ply file generated from your work.

@TQTQliu
Copy link
Owner

TQTQliu commented Sep 13, 2024

The dtype of a point cloud should contain the following items:

# Define the dtype for the structured array
    dtype = [('x', 'f4'), ('y', 'f4'), ('z', 'f4'),
            ('nx', 'f4'), ('ny', 'f4'), ('nz', 'f4'),
            ('red', 'u1'), ('green', 'u1'), ('blue', 'u1')]

I suspect that the point cloud obtained through Dust3R is missing certain properties, which you can check.

Or you can share the point cloud saving code of dust3r with me, and I'll be also happy to check it out for you.

@ZhenyuSun-Walker
Copy link
Author

Thanks for your suggestions! Maybe we can have further communications by email.

@TQTQliu
Copy link
Owner

TQTQliu commented Sep 13, 2024

No problem, if you have further questions, feel free to contact me ([email protected]).

@ZhenyuSun-Walker
Copy link
Author

Actually, I used the InstantSplat to help convert the pointcloud file (which is glb. format) from Dust3R into ply format, but things went strange when it comes to read the ply file with dataset_reader of mvsgs, but the ply file can be read by InstantSplat. And I have checked the dataset_reader code of InstantSplat, and the following part
`

Define the dtype for the structured array

dtype = [('x', 'f4'), ('y', 'f4'), ('z', 'f4'),
        ('nx', 'f4'), ('ny', 'f4'), ('nz', 'f4'),
        ('red', 'u1'), ('green', 'u1'), ('blue', 'u1')]

·

is actually the same.

@ZhenyuSun-Walker
Copy link
Author

No problem, if you have further questions, feel free to contact me ([email protected]).

OK, I'll contact you through that .

@TQTQliu
Copy link
Owner

TQTQliu commented Sep 13, 2024

Actually, I used the InstantSplat to help convert the pointcloud file (which is glb. format) from Dust3R into ply format, but things went strange when it comes to read the ply file with dataset_reader of mvsgs, but the ply file can be read by InstantSplat. And I have checked the dataset_reader code of InstantSplat, and the following part `

Define the dtype for the structured array

dtype = [('x', 'f4'), ('y', 'f4'), ('z', 'f4'),
        ('nx', 'f4'), ('ny', 'f4'), ('nz', 'f4'),
        ('red', 'u1'), ('green', 'u1'), ('blue', 'u1')]

·

is actually the same.

Okay, I'll check it out later.

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