-
Notifications
You must be signed in to change notification settings - Fork 14
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
Key 'collate_landmarks' was used the wrong number of times #4
Comments
I have solved this problem. So when I modify the .lua file as following, I run the Static Landmarks demo successfully.
|
This doesn't work, I still has the same problem:
Here is my configure file:
UpdateI have solved the problem, after change the configure file, you should rebuild the cartographer_mir, or you can change the configure file in /install_isolated/share/cartographer_mir/configuration_files/mir-100-mapping.lua |
I'm learning the cartographer these days. I have successfully run the 2D backpack demo and the 3D backpack demo. However, I face a problem when I run the Static Landmarks demo.
Here is the problem.
I have install the "cartographer_mir" successfully. When I try to launch the landmarks demo as guided by https://google-cartographer-ros.readthedocs.io/en/latest/demos.html:
roslaunch cartographer_mir offline_mir_100_rviz.launch bag_filename:=${HOME}/Downloads/landmarks_demo_uncalibrated.bag
, I meet the following error:
So I checked the "offline_mir_100_rviz.launch" file and found that the arg name is 'bag_filenames' instead of ‘bag_filename’. So a 's' is missing in the commend line shown in https://google-cartographer-ros.readthedocs.io/en/latest/demos.html.
However, I meet another error when I fix this problem:
I checked the configurations file: /cartographer_mir/cartographer_mir/configuration_files/mir-100-mapping.lua. I found that the parameter "collate_landmarks" is set to be false. So I modify it to be true as following:
TRAJECTORY_BUILDER.collate_landmarks = true
However, the error is same:
Could someone to help me? I don't know what's the problem.
The text was updated successfully, but these errors were encountered: