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

Problem about BEV render #42

Closed
zjulabwjt opened this issue May 23, 2024 · 7 comments
Closed

Problem about BEV render #42

zjulabwjt opened this issue May 23, 2024 · 7 comments

Comments

@zjulabwjt
Copy link

hi, @DRosemei thanks for your great work! I use my datasets run RoMe, but find in bev render, img is not a bev result. What wrong might cause this problem? Thanks for your help!
image

@DRosemei
Copy link
Owner

@zjulabwjt Sorry for late reply. You can check ego car poses and make sure they are mostly paralleled to road/ground.

@zjulabwjt
Copy link
Author

zjulabwjt commented May 29, 2024

@zjulabwjt Sorry for late reply. You can check ego car poses and make sure they are mostly paralleled to road/ground.

@DRosemei thanks for your reply. I visualize my ego pose xyz,The range of z-axis variation of the vehicle's pose is 4.9 meter during movement. And the trajectory nearly a straight line. I also found the trajectory before and after multiplying the vehicle's pose by the transform_normal2origin matrix does not match. Is it because the plane fitting algorithm fails in this case? Besides, how to understand the code transform_normal2origin[2, 3] += self.camera_height and in my dataset how to set this value, because if self.camera_height is not suitable, the loss nearly zero, and render img is white.
image

@DRosemei
Copy link
Owner

@zjulabwjt
Q: Is it because the plane fitting algorithm fails in this case?
A: It may be yes. Plane fitting algorithm is not always good especially. You can skip this and "camera_height", use actual (but may not be accurate road elevations) to init/supervise/fix elevation mlp.

@zjulabwjt
Copy link
Author

zjulabwjt commented May 31, 2024

@zjulabwjt Q: Is it because the plane fitting algorithm fails in this case? A: It may be yes. Plane fitting algorithm is not always good especially. You can skip this and "camera_height", use actual (but may not be accurate road elevations) to init/supervise/fix elevation mlp.

@DRosemei
Thank you for your advice. Following your suggestions, I improved the effectiveness of road surface reconstruction using pre-trained z mlp. However, In our scenario, there are a large number of vehicles. Due to the removal of dynamic objects during the training process, this results in numerous holes in the final road surface. I attempted to fuse the depth map from LiDAR with multi-view camera data, but I'm still encountering this issue. Is there any effective method to address this situation?
image

@DRosemei
Copy link
Owner

DRosemei commented Jun 3, 2024

@DRosemei It is unavoidable, so we use more than one clip to reconstruct the whole area

@zjulabwjt
Copy link
Author

@DRosemei It is unavoidable, so we use more than one clip to reconstruct the whole area

Thanks for your reply! Does multiple clip data refer to data collected multiple times from the same area at different times?

@DRosemei
Copy link
Owner

DRosemei commented Jun 3, 2024

@zjulabwjt Yes, it does and you can refer https://www.bilibili.com/video/BV1ve4y1i7aZ?p=18&vd_source=5051310ed13090afc35ea319bbc5cac3 for more infomation.

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