> For the complete documentation index, see [llms.txt](https://campus-rover.gitbook.io/lab-notebook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://campus-rover.gitbook.io/lab-notebook/fiiva/handy-commands.md). # handy-commands.md ## TurtleBot3 Control * `roslaunch turtlebot3_fake turtlebot3_fake.launch` - Launch the TB3 Fake Turtlebot Simulator plus RViz * `roslaunch turtlebot3_teleop turtlebot3_teleop_key.launch` - Launch TB3 teleop * `roslaunch turtlebot3_gazebo turtlebot3_simulation.launch` - Drives a turtlebot around on autopilot ## Gazebo worlds * `roslaunch turtlebot3_gazebo turtlebot3_empty_world.launch` - Empty world - no walls * `roslaunch turtlebot3_gazebo turtlebot3_stage_1.launch` - Simple square walled area * `roslaunch turtlebot3_gazebo turtlebot3_stage_2.launch` - Simple square walled area * `roslaunch turtlebot3_gazebo turtlebot3_stage_3.launch` - Simple square walled area * `roslaunch turtlebot3_gazebo turtlebot3_world.launch` - Weird 6 sided wall world * `roslaunch turtlebot3_gazebo turtlebot3_house.launch` - Elaborate house world ## Running RViz with Gazebo * `roslaunch turtlebot3_gazebo turtlebot3_gazebo_rviz.launch` - Not sure why its needed. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://campus-rover.gitbook.io/lab-notebook/fiiva/handy-commands.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.