Skip to content

[FEATURE] Support MJCF jointinparent actuator transmission #3743

Description

@han-xudong

Description

ModelBuilder.add_mjcf() does not recognize the common actuator target attribute jointinparent. The actuator is silently omitted, even though SolverMuJoCo.TrnType.JOINT_IN_PARENT and the final MuJoCo enum mapping already exist.

Why this matters

For ball and free joints, jointinparent expresses the actuator gear in the parent frame. It is not equivalent to an ordinary joint transmission once the joint rotates. Dropping or downgrading it changes generalized actuator moments.

Proposed behavior

  • Resolve jointinparent through the same named-joint/DOF mapping as joint.
  • Preserve JOINT_IN_PARENT as a distinct transmission type and direct-control actuator.
  • Export it as mjTRN_JOINTINPARENT.
  • Compare the resulting actuator moment against native MuJoCo at a rotated ball-joint pose.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status
    In Progress

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions