From b16e18f978f6e667b93c439171b9543fe72dcc3b Mon Sep 17 00:00:00 2001 From: Adil Zouitine Date: Fri, 8 Aug 2025 16:36:09 +0200 Subject: [PATCH] Fix typo in documentation for adapters in robots/teleop section --- docs/source/processors_robots_teleop.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/processors_robots_teleop.mdx b/docs/source/processors_robots_teleop.mdx index cf8b8e040..785c5ff3f 100644 --- a/docs/source/processors_robots_teleop.mdx +++ b/docs/source/processors_robots_teleop.mdx @@ -8,7 +8,7 @@ We use the Phone to SO‑100 follower examples for concreteness, but the same pa - Absolute vs. relative EE control: What each means, trade‑offs, and how to choose for your task. - Three-pipeline pattern: How to map teleop actions → dataset actions → robot commands, and robot observations → dataset observations. -- Adapters (`to_transition` / `to_output`): How these comvert raw dicts to `EnvTransition` and back to reduce boilerplate. +- Adapters (`to_transition` / `to_output`): How these convert raw dicts to `EnvTransition` and back to reduce boilerplate. - Dataset feature contracts: How steps declare features via `transform_features(...)`, and how to aggregate/merge them for recording. - Choosing a representation: When to store joints, absolute EE poses, or relative EE deltas—and how that affects training. - Pipeline customization guidance: How to swap robots/URDFs safely and tune bounds, step sizes, and options like IK initialization.