Method

Methodology

PhysDesignBench tests whether an AI agent can go from a specification to a validated physical design: the agent designs with real simulators under a fixed budget, and an independent evaluator rebuilds and scores what it submits.

What the benchmark measures

A complete design workflow

01

Requirement interpretation

Turn a specification, its constraints and an objective J into a concrete device plan.

02

Tool-guided iteration

Use simulators and a limited number of evaluator probes to decide what to change next.

03

Artifact correctness

Submit design source that the evaluator can rebuild into a layout that passes every gate.

04

Verified performance

Score well on J once the rebuilt design has passed design-rule, connectivity, electrical, thermal and numerical checks.

Authority boundary

Agent control and evaluator control stay separate

Agent controls
  • Design source and parameter choices
  • Probe requests, up to 40 for Design and 30 for Reimplementation, within 120 minutes
  • Iteration strategy and final submission
Evaluator controls
  • A separate container that rebuilds the submitted design from source
  • Every validity gate and the objective J
  • The score, bound to the submission's hash; files the agent writes are ignored
Task families

Two kinds of engineering work

Design · 16 tasks

Start from functional requirements

Open-ended tasks, from single components to full electrothermal circuits. The agent chooses the device concept and how to get there. Each task has an expert reference design that passes every gate.

Reimplementation · 10 tasks

Start from a published device

The agent rebuilds a device from the literature and tries to improve on it. The published device's objective is the reference, so matching it scores S = 0.5.

Scoring

Objective J first, then score S

J

Objective

J is task-specific and computed by the evaluator; lower is better. A design that fails any gate has no J and scores S = 0.

S = 1 / (1 + J / c)

Score

S runs from 0 to 1, and S = 0.5 when J equals the reference c. For Design, c is a fixed engineering scale per task; for Reimplementation, c is the published device's objective, so S above 0.5 beats the published device.

The leaderboard follows Table 3 of the paper: the best eligible evaluated design for Design tasks and the final submission for Reimplementation, with invalid results at S = 0, averaged per task family with 95% bootstrap intervals. The RF preview uses a diagnostic S = 1 / (1 + J) and is not part of the ranking.

Scope

What the results do and do not show

They show

How 11 model–agent configurations compare on 26 photonic and multiphysics design tasks, with uncertainty; how often each one reaches a valid design; and every run's probes, scores and final layout.

They do not show

Fabricated performance: every score comes from simulation. Nor equal cost: tokens and time are recorded as each harness reports them. Difficulty levels are relative to these configurations, and other physics domains are outside this release.

PhysDesignBench · see Data & citation for the result files, repository, citation and license.