Principle:ARISE Initiative Robosuite Robot Base Model Design
| Knowledge Sources | |
|---|---|
| Domains | Robotics, Simulation, Mechanical Design |
| Last Updated | 2026-02-15 07:00 GMT |
Overview
An abstraction layer for robot base and mount hardware that defines the physical attachment point, rotation offset, and geometric extents for different base types including fixed mounts, mobile wheeled platforms, and legged locomotion bases.
Description
A robot arm does not exist in isolation -- it must be attached to some form of base or mount that anchors it in the workspace or enables locomotion. The base model design principle provides an abstract class hierarchy for these attachment mechanisms, covering static mounts (bolted to a table or wall), mobile wheeled platforms, and legged walking bases. Each base type is represented as an MJCF model that can be programmatically merged into a robot's body tree.
The robot base model base class wraps an MJCF XML file and computes a rotation offset from the quaternion of its root body, which is used to correctly orient the robot when the base is attached. It declares abstract properties for the top offset (the mounting surface location relative to the root body), horizontal radius (for collision-free placement), and important sites, geometries, and sensors. The collision geometry is colored consistently to distinguish base structures from robot and environment elements.
The legged base model extends the base with locomotion-specific capabilities. It can remove joint actuation from specific leg segments (converting them to passive elements), remove free joints (for floating-base configurations), and programmatically add mobile joints (slide and hinge) with velocity actuators to enable base translation and rotation. This allows the same physical leg model to be used in both fully actuated walking mode and simplified floating-base mode where only the base pose is controlled.
Usage
Apply this principle when defining the physical mounting or locomotion hardware for a robot in simulation. When the same robot arm should be usable with different base types (fixed mount, wheeled base, legged platform), implement each base as a separate model class and use the factory pattern to select the appropriate one at runtime.
Theoretical Basis
The base model hierarchy uses type-based dispatch for attachment:
RobotBaseModel (abstract base)
+-- MountModel (static mount, merged below robot root)
+-- MobileBaseModel (wheeled/holonomic platform)
+-- LegBaseModel (legged locomotion base)
+-- NullBaseModel (no physical base, identity attachment)
robot.add_base(base):
if isinstance(base, MountModel): add_mount(base)
if isinstance(base, MobileBaseModel): add_mobile_base(base)
if isinstance(base, LegBaseModel): add_leg_base(base)
if isinstance(base, NullBaseModel): add_null_base(base)
Legged base mobile joint injection adds three joints for planar mobility:
slide joint (forward): axis=[0,1,0], frictionloss=250
slide joint (side): axis=[1,0,0], frictionloss=250
hinge joint (yaw): axis=[0,0,1], frictionloss=250
Each joint receives a corresponding velocity actuator with force limits, enabling simplified base control without modeling full leg dynamics.
Rotation offset is extracted from the base body quaternion and converted to (x,y,z,w) convention for consistent composition with the robot body orientation.