Gary Bey cardboardcode

For People In A Hurry: Setting up to Detect AprilTag in ROS2

TLDR: This is a set of instructions to help set up necessary ROS2 packages to start detecting Apriltag.

TLDR: This is a set of instructions to help set up necessary ROS2 packages in order to run ros1_bridge.

ros1_bridge allows nodal communication between ROS1 and ROS2 packages, providing higher flexibility in setting up an overall ROS system.

TLDR: This is a set of instructions to help set up ROS 1 Noetic on Ubuntu 20.04.

sudo sh -c 'echo "deb http://packages.ros.org/ros/ubuntu $(lsb_release -sc) main" > /etc/apt/sources.list.d/ros-latest.list'

sudo apt-get update && sudo apt-get install curl -y

TLDR: These are a quick list of instructions to quickly install and run rmf_web on your local workstation.

docker pull ghcr.io/open-rmf/rmf/rmf_demos:latest

TLDR:These are a quick list of instructions to quickly install and run nav_rest_api_turtlebot on your local workstation.

TLDR:These are a quick list of instructions to quickly build rmf from source on your local workstation.

This is a minimal proof that different ROS 2 distribution can communicate succesfully with each other.

In this example, a ROS 2 Humble talker node is able to communicate to a ROS 2 Jazzy listener node between their individualized docker containers.

This document contains quick and easy steps to upgrade Google Chrome Browser whenever it asks for it to be re-installed.

The alternative would be to manually access the Chrome install page.

1. Download the google-chrome-stable_current_amd64.deb from official Google website by running command below:

	[INFO] [launch]: All log files can be found below /root/.ros/log/2025-04-21-14-35-46-158426-rosi-0-1
	[INFO] [launch]: Default logging verbosity is set to INFO
	[INFO] [rmf_traffic_schedule-1]: process started with pid [25]
	[INFO] [rmf_traffic_schedule_monitor-2]: process started with pid [26]
	[INFO] [rmf_traffic_blockade-3]: process started with pid [27]
	[INFO] [schedule_visualizer_node-4]: process started with pid [28]
	[INFO] [fleetstates_visualizer_node-5]: process started with pid [29]
	[INFO] [rmf_visualization_building_systems-6]: process started with pid [30]
	[INFO] [floorplan_visualizer_node-7]: process started with pid [31]
	[INFO] [obstacle_visualizer_node-8]: process started with pid [32]

	[INFO] [launch]: All log files can be found below /root/.ros/log/2025-04-27-07-28-14-133521-rosi-0-1
	[INFO] [launch]: Default logging verbosity is set to INFO
	[INFO] [rmf_traffic_schedule-1]: process started with pid [27]
	[INFO] [rmf_traffic_schedule_monitor-2]: process started with pid [28]
	[INFO] [rmf_traffic_blockade-3]: process started with pid [29]
	[INFO] [schedule_visualizer_node-4]: process started with pid [30]
	[INFO] [fleetstates_visualizer_node-5]: process started with pid [31]
	[INFO] [rmf_visualization_building_systems-6]: process started with pid [32]
	[INFO] [floorplan_visualizer_node-7]: process started with pid [33]
	[INFO] [obstacle_visualizer_node-8]: process started with pid [34]