google-deepmind / google-deepmind/dm_control

Optionally enable actuation in `physics.after_reset`?

Open
#517 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
4.7k
Forks
764
PR merge metrics
No merged PRs in 30d

Description

Would it make sense to optionally enable actuation in the `after_reset` method [here](https://github.com/google-deepmind/dm_control/blob/main/dm_control/mujoco/engine.py#L310)?

The use case I have in mind is initializing episode with actuators in a certain activation state `physics.data.act`, before any control input is provided. What do you think?

Contributor guide

Open the contributing guide

Research direction

Start by reading the after_reset method in dm_control/mujoco/engine.py at the linked location, along with the surrounding reset behavior. Determine how an optional actuation path could initialize physics.data.act before control input while preserving the current default behavior; the issue is complete when that behavior is defined and implemented consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.