-
Updated
Jul 26, 2021 - C++
ros
Here are 5,041 public repositories matching this topic...
-
Updated
Oct 12, 2020
-
Updated
Jul 26, 2021 - C++
-
Updated
Jul 21, 2021 - C++
-
Updated
Jul 13, 2021
-
Updated
Feb 15, 2021
This PR should fix #3435 and also:
- makes Webots display a warning if a
ShapewithcastShadows TRUEcontains a mesh geometry which is too large to cast shadows, e.g., the mesh has more than 21845 triangles (21845 = 65535 / 3). - Fix all the proto files raising this warning.
- Fix all the world files raising this warning.
After testing many worlds, it seems that only the Robo
Hello,
I want to use ros2 to output lane information. I noticed that there is lane-line sensor, but it only supports cyberrt, and there is no relevant source code. I would like to ask, is it OK to create the corresponding ros2 message? Can I reuse this sensor, or do I need to write my own sensor?
thank you
-
Updated
Jul 21, 2021
I recently ran into an issue using AMCL, for which I was given this warning message:
[ WARN] [1425574394.999492201]: No laser scan received (and thus no pose updates
have been published) for 1425574394.999407 seconds. Verify that data is being published
on the /scan topic.
However, the actual issue was a miscofiguration of the odom_frame_id :
`<param name="odom_frame_id"
-
Updated
Jul 1, 2021 - C++
-
Updated
Jun 18, 2019 - C++
-
Updated
Jul 6, 2021 - C++
-
Updated
Apr 26, 2021 - C++
-
Updated
Jul 12, 2021 - C++
-
Updated
Jun 15, 2021 - C++
-
Updated
Feb 4, 2021 - C++
-
Updated
May 20, 2021 - C++
-
Updated
Jun 21, 2021 - C
-
Updated
Mar 16, 2019 - Python
-
Updated
Jul 18, 2021 - C++
Improve this page
Add a description, image, and links to the ros topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the ros topic, visit your repo's landing page and select "manage topics."


Feature request
Is your feature request related to a problem? Please describe.
Move test_onboard_logging_generation outside autotest.py to all to validate logger documentation before running the full autotest suite. Ideally, on CI it should run on build_ci.sh with param_parse.py to allow to validate soon that the documentation is correct and not wait that all test pass to trigger a docu