-
Notifications
You must be signed in to change notification settings - Fork 152
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
Mesher queue empty warning, poor mesh generation? #195
Comments
我有一样的问题 |
I have not solved it yet unfortunately. I have found that I get the same issue with the Euroc V1_01_easy.bag file. |
I am also having similar problems when working with the oak-d camera (not even getting meshes) which I believe are related. Can you please share the camera configuration yaml file, the params (in the Kimera_VIO resources), the launch file, and the rviz file. It would be nice to share as well which linux and ROS version you are using and gtsam version. |
I have the same issue with Euros V1_01_easy.bag. Have you solved it? |
我也没解决 我导给我安排别的活了 没有继续修改了
At 2024-07-14 06:51:48, "avb" ***@***.***> wrote:
I have the same issue with Euros V1_01_easy.bag. Have you solved it?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
I had a bit of luck when I moved into environments with more, flat horizontal and vertical surfaces, but I have since discovered that the odometry (and actually the mesh too, now I'm thinking of it) in the ros version is utter garbage, so I've been working with getting the non-ros version working with live data instead. However, I've had no response from the writers (or anyone else who has solved it) on either getting the ros odometry to not be garbage (see here) and or getting the non-ros working with live data (see here). I've got a version of the non-ros that will compile and run the camera, but so far it just crashes right away after the camera boots. |
Hello, I am trying to get the mesher working properly, and I keep getting very odd results that don't seem to line up with the environment, and I am wondering if that is due to the mesher queue issues that keep coming up? I put a piece of the outputs below so you can see, as well as a screenshot of what the mesh looks like. Any idea what is going wrong here and how to fix it to get a better mesh?
The text was updated successfully, but these errors were encountered: