-
Updated
May 31, 2021 - C++
ros
Here are 4,836 public repositories matching this topic...
-
Updated
Oct 12, 2020
-
Updated
May 31, 2021 - C++
-
Updated
May 31, 2021 - C++
-
Updated
May 25, 2021
-
Updated
Feb 15, 2021
Maybe, the Python documentation would be more readable by utilizing the Python typing. For example, instead of:
from controller import Node
class Node:
def getId(self):
def getDef(self):
def getParentNode(self):
def isProto(self):
def getFromProtoDef(self, name):we could write
from contro-
Updated
Sep 14, 2020
Map is missing annotation MapHolder and child holders! Please add to scene and set holder transforms
UnityEngine.Debug:LogError(Object)
Simulator.Map.MapManagerData:.ctor() (at Assets/Scripts/Map/MapManagerData.cs:25)
Simulator.Editor.MapMeshes.MapMeshBuilder:BuildMesh(GameObject, MapMeshMaterials, Boolean, LaneLineOverride) (at Assets/Scripts/Editor/Map/Meshes/MapMeshBuilder.cs:266)
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
May 31, 2021 - C++
-
Updated
Jun 18, 2019 - C++
-
Updated
May 31, 2021 - C++
-
Updated
Apr 26, 2021 - C++
-
Updated
May 28, 2021 - C++
-
Updated
Mar 1, 2021 - C++
-
Updated
Feb 4, 2021 - C++
-
Updated
May 20, 2021 - C++
-
Updated
Mar 16, 2019 - Python
-
Updated
May 26, 2021 - C
-
Updated
May 27, 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