google-deepmind / google-deepmind/mujoco
[<Actuator>] Custom Control Range Mapping for Actuators in MJCF XML
- Dominant language
- C++
- Stars
- 15.2k
- Forks
- 1.8k
- Avg merge
- 10d 16h
- Merged PRs (30d)
- 25
Description
**Summary**
I am suggesting a feature to map the inherited joint control range to a custom range for the **_position controller_** within the tag in the XML configuration file. This feature would be particularly useful for scenarios where the joints are procedurally generated, and each joint starts in a random position within its respective movement range.
As an example, this joint is initiated with random position hence the range is between -1.5 and -0.2
``
The new feature could be implemented by adding a new attribute to the tag that specify the desired control range. For example:
``
**Problem Description**
In many simulations, especially those involving procedurally generated robots, joints initialize at random positions within their respective movement ranges. These ranges vary for each joint, with some joints having negative minimum range aswell. As a result, each actuator ends up with a unique control range. Currently, there is no built-in functionality to standardize or map these control ranges to a consistent scale. This leads to a high number of actuators, each requiring manual adjustment to set their control ranges appropriately in python or c++.
**Benefits**
- Standardizing control ranges simplifies the setup and management of multiple actuators, also desired for learning applications.
- Allows for convenience in simulations where the random initial joint positions does not affect the actuator configurations.
Thank you for your attention and for your continuous efforts in improving MuJoCo.
Here is a procedurally generated truss robot model from my research.

Contributor guide
Assessment
This issue has not been assessed yet.