From 829d2d1ad9bc0acc20fbf64f22027c615055385e Mon Sep 17 00:00:00 2001 From: Steven Palma Date: Thu, 9 Oct 2025 15:20:07 +0200 Subject: [PATCH] fic(docs): local docs links (#2149) --- docs/source/integrate_hardware.mdx | 4 ++-- docs/source/introduction_processors.mdx | 6 +++--- docs/source/phone_teleop.mdx | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/source/integrate_hardware.mdx b/docs/source/integrate_hardware.mdx index 7e7fe0bf..ed9dc8dd 100644 --- a/docs/source/integrate_hardware.mdx +++ b/docs/source/integrate_hardware.mdx @@ -8,7 +8,7 @@ To that end, we provide the [`Robot`](https://github.com/huggingface/lerobot/blo - Your own robot which exposes a communication interface (e.g. serial, CAN, TCP) - A way to read sensor data and send motor commands programmatically, e.g. manufacturer's SDK or API, or your own protocol implementation. -- LeRobot installed in your environment. Follow our [Installation Guide](./installation.mdx). +- LeRobot installed in your environment. Follow our [Installation Guide](./installation). ## Choose your motors @@ -65,7 +65,7 @@ class MyCoolRobotConfig(RobotConfig): ``` -[Cameras tutorial](./cameras.mdx) to understand how to detect and add your camera. +[Cameras tutorial](./cameras) to understand how to detect and add your camera. Next, we'll create our actual robot class which inherits from `Robot`. This abstract class defines a contract you must follow for your robot to be usable with the rest of the LeRobot tools. diff --git a/docs/source/introduction_processors.mdx b/docs/source/introduction_processors.mdx index 308edbb3..6f376861 100644 --- a/docs/source/introduction_processors.mdx +++ b/docs/source/introduction_processors.mdx @@ -297,9 +297,9 @@ LeRobot provides many registered processor steps. Here are the most commonly use ### Next Steps -- **[Implement Your Own Processor](implement_your_own_processor.mdx)** - Create custom processor steps -- **[Debug Your Pipeline](debug_processor_pipeline.mdx)** - Troubleshoot and optimize pipelines -- **[Processors for Robots and Teleoperators](processors_robots_teleop.mdx)** - Real-world integration patterns +- **[Implement Your Own Processor](./implement_your_own_processor)** - Create custom processor steps +- **[Debug Your Pipeline](./debug_processor_pipeline)** - Troubleshoot and optimize pipelines +- **[Processors for Robots and Teleoperators](./processors_robots_teleop)** - Real-world integration patterns ## Summary diff --git a/docs/source/phone_teleop.mdx b/docs/source/phone_teleop.mdx index 22159193..76e3c367 100644 --- a/docs/source/phone_teleop.mdx +++ b/docs/source/phone_teleop.mdx @@ -79,7 +79,7 @@ After running the example: - Android: after starting the script, open the printed local URL on your phone, tap Start, then press and hold Move. - iOS: open HEBI Mobile I/O first; B1 enables motion. A3 controls the gripper. -Additionally you can customize mapping or safety limits by editing the processor steps shown in the examples. You can also remap inputs (e.g., use a different analog input) or adapt the pipeline to other robots (e.g., LeKiwi) by modifying the input and kinematics steps. More about this in the [Processors for Robots and Teleoperators](./processors_robots_teleop.mdx) guide. +Additionally you can customize mapping or safety limits by editing the processor steps shown in the examples. You can also remap inputs (e.g., use a different analog input) or adapt the pipeline to other robots (e.g., LeKiwi) by modifying the input and kinematics steps. More about this in the [Processors for Robots and Teleoperators](./processors_robots_teleop) guide. - Run this example to record a dataset, which saves absolute end effector observations and actions: