You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Bug
Thank you very much for your work, at the moment I would like to be able to reproduce the ORBSLAM3 program and the comparison of the trajectory accuracy between the slam program and the trajectory truth in the simulation environment you have provided, but at the moment there are a few issues that arise.
Steps to Reproduce
I have calibrated well in the webots environment that you provide
I implemented the extraction of the truth value of the robot body trajectory via pycharm
I use ros to pass the image information into the SLAM program and calculate the trajectory
I ended up using evo to achieve accuracy comparisons between trajectories
Expected behavior
What I'm hoping for is that the trajectory truth should not be too far off from the historical trajectory computed by the SLAM program without influence
Screenshots
Here's a scree
nshot of my calibration
Here's a reproduction of my ORBSLAM3 program in webots
Here's my final trajectory comparison Where the gray line segments are the true values of the trajectories extracted from the webots, and the colored line segments are the trajectories calculated by ORBSLAM3
This discussion was converted from issue #6546 on May 08, 2024 09:34.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Describe the Bug
Thank you very much for your work, at the moment I would like to be able to reproduce the ORBSLAM3 program and the comparison of the trajectory accuracy between the slam program and the trajectory truth in the simulation environment you have provided, but at the moment there are a few issues that arise.
Steps to Reproduce
Expected behavior
What I'm hoping for is that the trajectory truth should not be too far off from the historical trajectory computed by the SLAM program without influence
Screenshots
Here's a scree
nshot of my calibration
Here's a reproduction of my ORBSLAM3 program in webots
Here's my final trajectory comparison Where the gray line segments are the true values of the trajectories extracted from the webots, and the colored line segments are the trajectories calculated by ORBSLAM3
System
webots R2023A
ubuntu 20.04
ORBSLAM3
evo
Beta Was this translation helpful? Give feedback.
All reactions