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

Provide pointcloud without depth image is block the path generation in current code. #57

Open
tdnet12434 opened this issue Jun 21, 2023 · 0 comments

Comments

@tdnet12434
Copy link

tdnet12434 commented Jun 21, 2023

Hi.

First of all, Thank you for the amazing public work!

I have tried FUEL with the simulation provided in the code.
I see it relied on a depth camera and projection to 3d pointcloud with the help of camera_pose/orientation provided by the VIO system.

But I want to try it with my stereo-imu setup. I already have pointcloud which is generated fast enough to feed the system. And odometry msg which have front-z, left-x, up-y. I know that simulation based on ROS front-x, left-y, up-z so I transform it in every Odomcallback. And posemsg I think it's already in z-front, x-left, y-down already, so it should be fine. However, after many tries, I can't make it work as the same when providing a depth image at all.

One thing I can observe is, when I use a depth image along with pointcloud topic (which is a bad depth image), I can see trajectory after trigger a goal topic by RVIZ. But if I provide only pointcloud and pose and disable depth image topic, I can see the map.

Is it possible to provide only pointcloud without depth image? Any advice would be appreciated.
Thank you advanced!

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