fercabe
commented
1 year ago Dear Miguel Angel,
DLL follows the usual ROS standards for odometry, that is, a TF that transform the robot base_link into the odometric frame.
You only need to specify the corresponding parameters in the launch files, they are the following:
- base_frame_id: Defines the robot base_link frame name, defualt value is "base_link"
- odom_frame_id: Defines the odometric frame name, the default name is "odom"
- global_frame_id: Define the global frame name, default value is "world". The odometric frame will be transformed into the global frame so that the Lidar sensing information matches the provided map.
You can find a good explanation about how TF is used in localization in the AMCL package, in section 3.1.6.
The mbzirc launch should work straight the way with the parameters of the launch file, if this is not the case, just let me known. We lately performed some updates in the grid map that might affect the initial position of the launch file.
Un abrazo! Fernando Caballero
MigVega
You mention in your paper and the comments of your launch files that one could/should use an accurate odometry system. However, I don't know the requirements or how to achieve that.
I tried to integrate into one single workspace, A-LOAM, and DLL, and run them in parallel; however, even changing the frame names did not work.
The closest example I found to recreate that was in the mbzirc.launch file. However, it says that the odometry is already in the bag file. In this case, my question is, how can I save the odometry resulting from LOAM into a bag file so that it is usable by DLL?
I appreciate any help you can provide. I want to compare my method with yours in a large-scale dataset. I believe that DLL is one of the best localization algorithms. Therefore, It would be an interesting comparison!