Fast-DDS
navigation2
Fast-DDS | navigation2 | |
---|---|---|
1 | 8 | |
1,980 | 2,103 | |
1.4% | 3.9% | |
9.5 | 9.4 | |
8 days ago | 3 days ago | |
C++ | C++ | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Fast-DDS
navigation2
-
Create a global plan between any 2 poses with nav2
This line might be your issue according to this github issues post (comment at the very bottom: https://github.com/ros-planning/navigation2/issues/2283)
-
What is your automated ROS2 software testing & simulation workflow?
I recently stumbled upon system tests for Nav2, I didn't dive into details but README says that among other things they test robots in sandbox environment, might be useful.
-
Turtlebot3 Refuses to Move in a Straight Line
The tutorial I was using (which comes straight from nav2) says to run ros2 launch nav2_bringup navigation_launch.py . However, when I went to tune Turtlebot3 via the .param file, it did no change whatsoever. This is because, by default, the file uses up this param file that is significantly different than burger.yaml; After changing it the costmap looks completely different. After reading the source code for the .launch file of the Turtlebot3 nav package for galactic and nav2, I've found out that running ros2 launch nav2_bringup navigation_launch.py params_file:=[PATH_TO_BURGER_YAML] works and completely fixes this issue.
-
SLAM Toolbox namespace for ROS
I am using the nav2_bringup example (https://github.com/ros-planning/navigation2/blob/main/nav2_bringup/launch/multi_tb3_simulation_launch.py) to launch multiple robots, it works fine. This file launches a file for single robots in different namespaces. This file for single robots is also able to switch from localization to mapping, simply by launching the file with argument slam:=True. I added slam as a launch argument for tb3_simulation_launch.py when launched from multi_tb3_simulation_launch.py and when i start the multirobot file with slam:=True it seems to work partially. ROS topics with the name /robot1/slam_toolbox/feedback,/robot1/slam_toolbox/update and /robot2/slam_toolbox/feedback ,/robot2/slam_toolbox/update get created, but /slam_toolbox/graph_visualization and /slam_toolbox/scan_visualization are only there once and not for every robot. In RVIZ there is no sign of SLAM working.
-
Help with Dynamic Window Approach controller
Hey, I am not sure if you can or even want but you could have a look into the C++ DWB planner plugin which is used in the nav2 stack.
- Approach to using nav2 with multiple robots on network?
-
ros2: How do I stop colcon test from complaining about linting?
I have tried all different kinds of headers in the python script (for instance, I have tried a header format like this), and it still complains about copyright linting. I have tried to remove every reference to linting in my package.xml and CMakeLists.txt but colcon/ament just keeps complaining about linting errors.
- How do I remove the unix timestamp that comes with RCLCPP_INFO?
What are some alternatives?
iceoryx - Eclipse iceoryx™ - true zero-copy inter-process-communication
ros2_laser_scan_matcher - Laser scan matcher ported to ROS2
DirectXTex - DirectXTex texture processing library
CppRobotics - Header-only C++ library for robotics, control, and path planning algorithms. Work in progress, contributions are welcome!
InterprocessMemPool - c++ library for interprocess memory pools, communication, and automatic network device discovery. lightweight DDS alternative.
dolly - 🤖🐑 It's a sheep, it's a dolly, it's a following robot. Dolly was born to be cloned.
ros_gz - Integration between ROS (1 and 2) and Gazebo simulation
navigation2_tutorials - Tutorial code referenced in https://navigation.ros.org/
Flow - Flow is a software framework focused on ease of use while maximizing performance in closed closed loop systems (e.g. robots). Flow is built on top of C++ 20 coroutines and utilizes modern C++ techniques.
turtlebot3 - ROS packages for Turtlebot3
mros2 - agent-less and lightweight communication library compatible with rclcpp for embedded devices
isaac_ros_apriltag - Hardware-accelerated Apriltag detection and pose estimation.