> For the complete documentation index, see [llms.txt](https://anonymous-humanoid.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anonymous-humanoid.gitbook.io/docs/getting-started-software.md). # Getting Started (Software) This section covers the software configuration for the humanoid robot, from embedded system setup, simulation, to policy training and implementation. Use the pages below as a step-by-step reference for the software configuration:

		Cover image
Embedded Environment Setup	Set up the ROS2 embedded development environment	arc_bridge_ros_architecture.drawio.svg	Embedded Environment Setup
Quick Start Demos	Run ready-made demos to quickly verify the robot's basic functions and get familiar with the workflow.	image.png	Quick Start Demos
Training Environment	Install the simulation and reinforcement learning environment used to train the robot's control policies.	image.png	Training Environment
Locomotion Sim2Sim and Sim2Real	Validate trained locomotion policies in simulation before deploying them to the physical robot.	image.png	Locomotion Sim2Sim and Sim2Real
Jetson Orin	Configure the Jetson Orin onboard computer that runs the robot's deployed software.	image.png	Jetson Orin

--- # 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://anonymous-humanoid.gitbook.io/docs/getting-started-software.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.