Skip to content

Randomizing drive gains

73 · Domain randomization

Five arms with a heavy tip on vertical hinges. At 1 s the script writes a sampled joint_target_ke and joint_target_kd per world, calls notify_model_changed(JOINT_DOF_FORCE_PROPERTIES), and steps the target to 90 degrees. Stiffer drives oscillate faster; lower damping overshoots more. Steel integrates drives implicitly by folding dt * kd + dt^2 * ke into the mass matrix, and the notification makes sure that matrix is rebuilt with the new gains.

0.00 s

What to look at

  • The oscillation period shortens as ke grows.
  • The arm with the lowest kd overshoots the most.

Key parameter

model.joint_target_ke / joint_target_kd

Per-DOF drive gains. The explicit drive force reads them every step; the implicit part lives in the mass matrix.

Try changing

  • Use update_mass_matrix_interval=10 and drop the notify call.
  • Try drive_mode="rows" and compare the responses.

Concept

When Steel sees a randomized value

What it is

Notify with the matching flags after changing these model arrays so Steel refreshes all derived data consistently. Some inputs are cached until notification; mass, inertia and drive gains can also be picked up by periodic mass-matrix rebuilds, so their behavior without notification depends on update_mass_matrix_interval.

In this scene

The arm with the lowest kd overshoots the most.

Considerations

Cost
Call only, default solver, six-link chain and four boxes per world, 1024 worlds (1.12 ms per collide + step): JOINT_DOF_FORCE_PROPERTIES 25 µs (7 µs captured). Flags measured one at a time; combined calls and feature validation can cost more. Body-inertial and joint-DOF notifications also request a mass-matrix refresh.
Graph capture
These flags can be captured in a reset graph. Kinematic-flag changes, sleeping, and shape flags with sparse factors plus restitution run eagerly; captured calls skip some value checks.
Interactions
world_mask limits which worlds lose their warm start; cached data is refreshed for every world.
Use it when
Policies that must tolerate actuator stiffness and damping errors.

The script

cd tutorials && python dr_drive_gains.py prints each variant's final metric; --record out.json also writes the replay. Every tutorial imports replay.py from the same folder.

tutorials/dr_drive_gains.py
# SPDX-FileCopyrightText: Copyright (c) 2026 Skild AI and the Steel contributors
# SPDX-License-Identifier: Apache-2.0
"""Drive gain randomization: per-world joint_target_ke/kd + JOINT_DOF_FORCE_PROPERTIES."""
import math
import newton
import numpy as np
import warp as wp
from newton.solvers import SolverSteel
from replay import Recorder
DT = 1.0 / 240.0
SUBSTEPS = 8
WORLDS = 5
def tf(x, y, z):
return wp.transform((x, y, z), wp.quat_identity())
def build():
arm = newton.ModelBuilder()
link = arm.add_link(xform=tf(0.0, 0.0, 0.6))
arm.add_shape_box(link, xform=tf(0.15, 0.0, 0.0), hx=0.15, hy=0.02, hz=0.02)
cfg = newton.ModelBuilder.ShapeConfig(density=8000.0)
arm.add_shape_sphere(link, xform=tf(0.3, 0.0, 0.0), radius=0.04, cfg=cfg)
j = arm.add_joint_revolute(
-1, link, axis=newton.Axis.Z, parent_xform=tf(0.0, 0.0, 0.6), target_ke=20.0, target_kd=2.0
)
arm.add_articulation([j])
builder = newton.ModelBuilder()
builder.replicate(arm, WORLDS, spacing=(0.0, 0.45, 0.0))
return builder.finalize()
def simulate(rec, label, ke, kd):
model = build()
solver = SolverSteel(model)
state_0, state_1, control = model.state(), model.state(), model.control()
newton.eval_fk(model, model.joint_q, model.joint_qd, state_0)
run = rec.variant(label, model)
for frame in range(rec.frames(5.0)):
if frame == rec.fps: # randomize at 1 s, then step the target to 90 degrees
model.joint_target_ke.assign(ke.astype(np.float32)) # one DOF per world
model.joint_target_kd.assign(kd.astype(np.float32))
# the drives are folded into the mass matrix, which this refreshes
solver.notify_model_changed(newton.ModelFlags.JOINT_DOF_FORCE_PROPERTIES)
control.joint_target_q.fill_(math.radians(90.0))
q = np.degrees(state_0.joint_q.numpy())
run.frame(state_0, **{f"ke {p:.1f} kd {d:.2f}": v for p, d, v in zip(ke, kd, q)})
for _ in range(SUBSTEPS):
solver.step(state_0, state_1, control, None, DT)
state_0, state_1 = state_1, state_0
run.check(solver)
if __name__ == "__main__":
rng = np.random.default_rng(8)
ke = rng.uniform(2.0, 20.0, WORLDS)
kd = rng.uniform(0.05, 0.5, WORLDS)
order = np.argsort(ke)
ke, kd = ke[order], kd[order]
rec = Recorder()
simulate(rec, "gains sampled per world", ke, kd)
rec.save()

Recorded with SolverSteel on Newton 1.9.0.dev0, Warp 1.19.0, NVIDIA RTX PRO 6000 Blackwell Server Edition. Replays read the state back every frame, so they are not a speed benchmark. Script · page text