Alloy: Open-Source Multi-Material Robot Simulation

Краткое содержание

Pixel highlights Alloy, an Apache-2.0 open-source physics engine for robot learning that brings rigid robots, cloth, soft bodies, sand, and liquids together in one scene. By routing each material to a specialized solver, Alloy could help researchers build more realistic tasks such as pouring, folding, and scooping without stitching together separate simulation tools.

DEV Community

Robots, liquids, cloth and sand in one scene: an open-source engine for robot learning

Many of the tasks we want robots to learn mix materials: pouring water into a glass, folding a towel, scooping sand, routing a cable. In simulation those materials usually live in different tools, so a policy that has to pour and grasp ends up stitched across engines, or the liquid gets left out. Alloy is an open-source (Apache-2.0) physics engine for robot learning that puts them in one scene. The paper is on arXiv: Alloy: A Multi-Material Physics Engine for Robot Learning. One scene, one solver per material Alloy is built on MuJoCo Warp and Newton and picks a solver for each object from its material: Object Solver Robots and rigid bodies MuJoCo Warp (MuJoCo C on the CPU) Cloth and soft bodies Newton's VBD solver Sand, granular material and pastes Newton's implicit MPM solver Liquids Alloy's own DFSPH solver Objects from different solvers touch each other in the same scene. sim.routes() tells you which solver each object got. Here an MJCF arm sits beside a tub of water and a tray of sand: import alloy

ARM = """



"""

scene = alloy.Scene(dt=0.01)
scene.add_ground()
scene.add_robot("arm", mjcf=ARM, pos=(0, 0, 0.1))
scene.add_open_box("tub", inner=(0.08, 0.08, 0.05), wall=0.01, pos=(0.5, 0, 0))
scene.add_liquid("water", size=(0.064, 0.064, 0.024), pos=(0.5, 0, 0.024))
scene.add_open_box("tray", inner=(0.1, 0.1, 0.05), wall=0.01, pos=(0.5, 0.4, 0))
scene.add_box("sand", size=(0.06, 0.06, 0.03), pos=(0.5, 0.4, 0.03), material="sand_silica_dry")
sim = alloy.build(scene, device="cpu")
print({n: sim.routes()[n]["solver"] for n in ("arm", "water", "sand")})
sim.run(0.3, targets={"shoulder": (0.0, 0.3)})
print(sim.state(world=0)["arm/shoulder.q"].round(2), sim.check()["ok"])
{'arm': 'mujoco', 'water': 'sph', 'sand': 'mpm'}
0.25 True
The MJCF string is the robot; a robot file such as a Franka loads the same way with add_robot. sim.check() grades the world, so you can catch a simulation that blew up instead of training on it. For reinforcement and imitation learning Many copies of a scene run in parallel worlds on one NVIDIA GPU, or on a CPU. Gymnasium-style vector environments and ready-made training tasks. Trained example policies on the Hub: pouring, cable lifting and Go2 walking. For coding agents Alloy ships an MCP server, so an agent such as Claude Code can build and run scenes itself: pip install alloy-engine
claude mcp add alloy -- alloy mcp
When to use something else Rigid robots only: MuJoCo Warp on its own is the leaner choice. If you want the solvers themselves, differentiable simulation or inverse kinematics, use Newton directly. Many worlds of sand or paste are limited by the stress solve, and a liquid beside sand meets it only at the sand's surface. The full list is on the Keep in mind page. Links Paper: https://arxiv.org/abs/2611.16312 (and its Hugging Face page) Code: https://github.com/argonrobotics-ai/alloy Docs: https://alloy.argonrobotics.ai/docs/ Install: pip install alloy-engine (Python 3.11 or 3.12)
Alloy: Open-Source Multi-Material Robot Simulation
Powered by Readybot.io

Последнее от Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …

Why a Java HPA Got Stuck at 20 Kubernetes Pods

Pixel shares how a Spring Boot pricing service autoscaled to 20 Kubernetes pods and stayed there because the JVM retained committed heap memory after traffic …