base on This repository contains a full wrapper class for running ORB-SLAM3 on a docker container with ROS2 Humble with Ubuntu 22.04. # ORB-SLAM3 ROS2 Wrapper Docker This repository contains a dockerized comprehensive wrapper for ORB-SLAM3 on ROS 2 Humble for Ubuntu 22.04. ## Build status  # Demo GIF  # Steps to use this wrapper ## 1. Clone this repository 1. ```git clone https://github.com/suchetanrs/ORB-SLAM3-ROS2-Docker``` 2. ```cd ORB-SLAM3-ROS2-Docker``` 3. ```git submodule update --init --recursive --remote``` ## 2. Install Docker on your system ```bash cd ORB-SLAM3-ROS2-Docker sudo chmod +x container_root/shell_scripts/docker_install.sh ./container_root/shell_scripts/docker_install.sh ``` ## 3. Build the image with ORB_SLAM3 1. Build the image: ```sudo docker build --build-arg USE_CI=false -t orb-slam3-humble:22.04 .``` 2. Add ```xhost +``` to your ```.bashrc``` to support correct x11-forwarding using ```echo "xhost +" >> ~/.bashrc``` 3. ```source ~/.bashrc``` 4. You can see the built images on your machine by running ```sudo docker images```. ## 4. Running the container 1. ```cd ORB-SLAM3-ROS2-Docker``` (ignore if you are already in the folder) 2. ```sudo docker compose run orb_slam3_22_humble``` 3. This should take you inside the container. Once you are inside, run the command ```xeyes``` and a pair of eyes should pop-up. If they do, x11 forwarding has correctly been setup on your computer. ## 5. Building the ORB-SLAM3 Wrapper Launch the container using steps in (4). ```bash cd /home/orb/ORB_SLAM3/ && sudo chmod +x build.sh && ./build.sh cd /root/colcon_ws/ && colcon build --symlink-install && source install/setup.bash ``` ## Launching ORB-SLAM3 Launch the container using steps in (4). If you are inside the container, run the following: 1. ```ros2 launch orb_slam3_ros2_wrapper unirobot.launch.py``` 3. You can adjust the robot namespace in the ```unirobot.launch.py``` file. ## Running this with a Gazebo Classic simulation. 1. Setup the ORB-SLAM3 ROS2 Docker using the steps above. Once you do (1) step in the ```Launching ORB-SLAM3``` section, you should see a window popup which is waiting for images. This is partially indicative of the setup correctly done. 2. Setup the simulation by following the README [here](https://github.com/suchetanrs/gz-sim-environment) 3. Once you are able to teleop the robot, you should be able to run ORB-SLAM3 with both the containers (simulation and wrapper) running parallely. ## Running the map_generator package. This package can be used to generate a global pointcloud from the SLAM. It subscribes to the published `map_data` and an input pointcloud either from a LiDAR or from a depth camera. It stitches the input pointclouds together based on the latest pose-graph data. To run the package, these steps can be followed: 1. Make sure the simulation is running. Run the orb_slam3 container and once you are in the bash shell, run the following: `./launch_slam.sh` 2. The top-left terminal contains the launch file to run the slam. This must be launched first. 3. The bottom-left terminal contains the launch file to start the pointcloud_stitcher node. This should run soon after you launch the SLAM. 4. If you wish to publish the global pointcloud at any point during the SLAM's operation, simply run the python file in the top-right terminal. You should be able to view the global pointcloud in rviz (you can launch RViz with the correct configuration from the bottom-right terminal). ### Potential issues you may face. The simulation and the wrapper both have their ```ROS_DOMAIN_ID``` set to 55 so they are meant to work out of the box. However, you may face issues if this environment variable is not set properly. Before you start the wrapper, run ```ros2 topic list``` and make sure the topics namespaced with ```robot_0``` are visible inside the ORB-SLAM3 container provided the simulation is running along the side. ## Services | Service Name | Purpose | type | |-------------------------|---------------|---------------| | `orb_slam3/get_map_data` | Sends the map_data in the response. | `slam_msgs::srv::GetMap` | | `orb_slam3/get_landmarks_in_view` | Takes an input pose and publishes the feature points visible from that pose. | `slam_msgs::srv::GetLandmarksInView` | | `orb_slam3/get_all_landmarks_in_map` | Publishes all feature points in the map and fills the same pointcloud in the response. | `slam_msgs::srv::GetAllLandmarksInMap` | | `orb_slam3/reset_mapping` | Resets the current mapping instance and clears all keyframes. | `std_srvs::srv::SetBool` | ## Published Topics | Topic Name | Purpose | type | |-------------------------|---------------|---------------| | `map_points` | Publishes the point cloud representing feature points collected from the SLAM process. This is published when `orb_slam3/get_all_landmarks_in_map` service is called. | `sensor_msgs::msg::PointCloud2` | | `visible_landmarks` | Publishes the point cloud of feature points (landmarks) visible from a given pose. This is published when `orb_slam3/get_landmarks_in_view` service is called. | `sensor_msgs::msg::PointCloud2` | | `slam_info` | Publishes overall SLAM-related information. | `slam_msgs::msg::SlamInfo` | | `map_data` | Continuously publishes the map data generated by the SLAM algorithm. | `slam_msgs::msg::MapData` | | `robot_pose_slam` | Publishes the robot's pose expressed in the global frame. | `geometry_msgs::msg::PoseStamped` | ## ROS Parameters | Parameter Name | Default Value | Description | |-------------------------|---------------|-----------------------------------------------------------------------------| | `robot_base_frame` | `base_footprint` | The name of the frame attached to the robot's base. | | `global_frame` | `map` | The name of the global frame of reference. It represents a fixed world coordinate frame in which the robot navigates.| | `odom_frame` | `odom` | The name of the odometry frame. | | `rgb_image_topic_name` | `rgb_camera` | The topic to recieve rgb images. | | `depth_image_topic_name` | `depth_camera` | The topic to recieve depth images. | | `imu_topic_name` | `imu` | The topic to recieve IMU messages (Not used in RGB-D mode). | | `odom_topic_name` | `odom` | The topic to recieve on board odometry messages (Used only if `odometry_mode` is set to true). | | `visualization` | `true` | A boolean flag to enable or disable visualization. When set to `true`, the ORB-SLAM3 viewer will show up with the tracked points and the keyframe trajectories.| | `odometry_mode` | `false` | A boolean flag to toggle odometry mode. When `false`, the system operates without relying on odometry data, which might be used in scenarios where odometry information is unavailable or unreliable. In this case, it publishes the transform directly between the ```global_frame``` and the ```robot_base_frame```| | `publish_tf` | `true` | Publishes the map->odom tf in case `odometry_mode` is set to `true` and map->odom->base_link in case odometry_mode is set to `false`.| | `map_data_publish_frequency`| `1000` | Time interval at which map_data should be published (ms).| | `do_loop_closing`| `true` | Enable or disable loop closing in ORB-SLAM3. This will also disable re-localisation and multi-map if `false`| ## Important notes ORB-SLAM3 is launched from ```orb_slam3_docker_20_humble/orb_slam3_ros2_wrapper/launch/rgbd.launch.py``` which inturn is launched from ```orb_slam3_docker_20_humble/orb_slam3_ros2_wrapper/launch/unirobot.launch.py``` Currently the ```rgbd.launch.py``` launch file defaults to ```orb_slam3_ros2_wrapper/params/gazebo_rgbd.yaml```. You can modify this with your own parameter file in case you wish to use your own camera. The very initial versions of this code were derived from [thien94/orb_slam3_ros_wrapper](https://github.com/thien94/orb_slam3_ros_wrapper) and [zang9/ORB_SLAM3_ROS2](https://github.com/zang09/ORB_SLAM3_ROS2) # Star history <img src="star-history-2025416.png" alt="Star-history" width="600">", Assign "at most 3 tags" to the expected json: {"id":"8520","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"