Update EDA Bench data card framing
Browse files- DATA_CARD.md +48 -9
DATA_CARD.md
CHANGED
|
@@ -47,11 +47,13 @@ plausibility.
|
|
| 47 |
|
| 48 |
## Contamination Policy
|
| 49 |
|
| 50 |
-
The default benchmark should be reported as open-book hardware
|
| 51 |
-
Agents may use web search and may discover public upstream projects
|
| 52 |
-
|
| 53 |
-
|
| 54 |
-
|
|
|
|
|
|
|
| 55 |
|
| 56 |
Repository build artifacts should contain runner and harness code, public
|
| 57 |
documentation, the task-pack manifest, and loader/grader support code. Task
|
|
@@ -84,6 +86,19 @@ score-supported through explicit I/O simulation oracles:
|
|
| 84 |
Full task packs include tests for the explicit I/O oracle. The reference project
|
| 85 |
must score `1.0` through `score_components["io_simulation"]`, and the fail
|
| 86 |
canary must score below the release threshold using the same simulation oracle.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 87 |
|
| 88 |
## Evaluation Claims
|
| 89 |
|
|
@@ -92,31 +107,55 @@ plus behavioral transient I/O simulation oracle. Scores should not be interprete
|
|
| 92 |
direct proof of electrical safety, regulatory compliance, manufacturability,
|
| 93 |
production readiness, or high-speed protocol compliance.
|
| 94 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 95 |
## Known Limitations
|
| 96 |
|
| 97 |
- The current oracle models realized copper, trace width/length/layer R/L/C
|
| 98 |
parasitics, same-layer trace-intersection shorts, close-trace coupling,
|
| 99 |
vias, zones, pad resistance, leakage, R/C/L/diode passives, deterministic
|
| 100 |
generic IC coupling, task-required boundary-net interface families,
|
| 101 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 102 |
connector pin/net semantic contracts, generic signal net-name tolerance,
|
|
|
|
|
|
|
| 103 |
diagnostic exact reference-pad, role/topology, and route-shape checks, hard
|
| 104 |
caps for wrong external pin/net mapping, missing routed copper, split or isolated external I/O,
|
| 105 |
power/ground/signal shorts, missing simulated signal or I/O transfer
|
| 106 |
-
responses,
|
| 107 |
-
|
|
|
|
|
|
|
|
|
|
| 108 |
tasks still need richer calibrated models: device behavioral models,
|
| 109 |
IBIS/SPICE/S-parameter data, field-solver stackups, power sequencing,
|
| 110 |
differential-channel expectations, and task-specific tolerances.
|
| 111 |
- The benchmark disables proxy grading based on component, footprint, routing,
|
| 112 |
or outline similarity.
|
| 113 |
-
- The built-in
|
| 114 |
upstream projects through search, so results measure web-enabled agent
|
| 115 |
performance rather than closed-book design synthesis. This is intentional for
|
| 116 |
the default open-book track and should be disclosed in any leaderboard or
|
| 117 |
paper claim.
|
| 118 |
- Some upstream projects have restrictive or unclear redistribution terms. See
|
| 119 |
`LICENSES.md` and per-source license notices before republishing subsets.
|
|
|
|
|
|
|
|
|
|
|
|
|
| 120 |
|
| 121 |
## Maintenance
|
| 122 |
|
|
|
|
| 47 |
|
| 48 |
## Contamination Policy
|
| 49 |
|
| 50 |
+
The default benchmark should be reported as open-book hardware task solving.
|
| 51 |
+
Agents may use web search and may discover public upstream projects, just as
|
| 52 |
+
public software-engineering benchmarks may expose code history, issue threads,
|
| 53 |
+
or patches. Claims should therefore be limited to public-information EDA task
|
| 54 |
+
solving under fixed prompts, fixed tooling, and recorded provenance. Do not use
|
| 55 |
+
default leaderboard results as evidence of closed-book synthesis or
|
| 56 |
+
memorization-resistant hidden answers.
|
| 57 |
|
| 58 |
Repository build artifacts should contain runner and harness code, public
|
| 59 |
documentation, the task-pack manifest, and loader/grader support code. Task
|
|
|
|
| 86 |
Full task packs include tests for the explicit I/O oracle. The reference project
|
| 87 |
must score `1.0` through `score_components["io_simulation"]`, and the fail
|
| 88 |
canary must score below the release threshold using the same simulation oracle.
|
| 89 |
+
Fail canaries remove active internal circuitry when available, falling back to
|
| 90 |
+
external boundary removal for passive boards, so validation covers plausible
|
| 91 |
+
external shells that do not contain the circuit needed to work.
|
| 92 |
+
|
| 93 |
+
The task-pack builder also stages generated mutation canaries for missing board
|
| 94 |
+
outlines, unrouted external nets, isolated external pads, external power/signal
|
| 95 |
+
pads tied to ground, and missing high-speed-like routes for high-speed carrier
|
| 96 |
+
tasks. Four representative calibrated tasks currently add stricter task-family
|
| 97 |
+
checks: USB-C breakout, RS-485 transceiver breakout, BQ24295 power path, and
|
| 98 |
+
M.2/PCIe adapter.
|
| 99 |
+
|
| 100 |
+
A full generated-mutation sweep on May 6, 2026 validated 40/40 tasks and 162
|
| 101 |
+
generated mutation canaries below the release threshold.
|
| 102 |
|
| 103 |
## Evaluation Claims
|
| 104 |
|
|
|
|
| 107 |
direct proof of electrical safety, regulatory compliance, manufacturability,
|
| 108 |
production readiness, or high-speed protocol compliance.
|
| 109 |
|
| 110 |
+
| Claim | Status |
|
| 111 |
+
|---|---|
|
| 112 |
+
| Open-book agent task solving under fixed prompts/tools/provenance | Supported |
|
| 113 |
+
| External I/O behavior under the released oracle | Supported |
|
| 114 |
+
| Closed-book PCB synthesis | Not supported |
|
| 115 |
+
| Manufacturing, regulatory, thermal, EMC, or production readiness | Not supported |
|
| 116 |
+
| Exact component inventory, reference designator, outline, or route-shape matching | Not a primary score |
|
| 117 |
+
|
| 118 |
## Known Limitations
|
| 119 |
|
| 120 |
- The current oracle models realized copper, trace width/length/layer R/L/C
|
| 121 |
parasitics, same-layer trace-intersection shorts, close-trace coupling,
|
| 122 |
vias, zones, pad resistance, leakage, R/C/L/diode passives, deterministic
|
| 123 |
generic IC coupling, task-required boundary-net interface families,
|
| 124 |
+
task-required generic internal active-role realization,
|
| 125 |
+
broad component-function realization for active devices, passives,
|
| 126 |
+
decoupling, filters, and protection networks,
|
| 127 |
+
active-device power/ground integrity,
|
| 128 |
+
absolute fabrication geometry sanity for outlines, trace widths, and via
|
| 129 |
+
annular rings,
|
| 130 |
+
external-net and board-wide same-layer short electrical-health contracts,
|
| 131 |
+
refdes-invariant external
|
| 132 |
connector pin/net semantic contracts, generic signal net-name tolerance,
|
| 133 |
+
KiCad DRC and schematic ERC errors relative to the reference when
|
| 134 |
+
`kicad-cli` is available,
|
| 135 |
diagnostic exact reference-pad, role/topology, and route-shape checks, hard
|
| 136 |
caps for wrong external pin/net mapping, missing routed copper, split or isolated external I/O,
|
| 137 |
power/ground/signal shorts, missing simulated signal or I/O transfer
|
| 138 |
+
responses, missing task-required internal active realization, missing
|
| 139 |
+
component-function realization, missing active-device power integrity,
|
| 140 |
+
DRC/ERC error violations, implausible trace/via/outline fabrication geometry,
|
| 141 |
+
grossly implausible impedance, and missing or implausible differential-pair
|
| 142 |
+
families. Many public hardware
|
| 143 |
tasks still need richer calibrated models: device behavioral models,
|
| 144 |
IBIS/SPICE/S-parameter data, field-solver stackups, power sequencing,
|
| 145 |
differential-channel expectations, and task-specific tolerances.
|
| 146 |
- The benchmark disables proxy grading based on component, footprint, routing,
|
| 147 |
or outline similarity.
|
| 148 |
+
- The built-in web harnesses are web-enabled. Agents may be able to discover public
|
| 149 |
upstream projects through search, so results measure web-enabled agent
|
| 150 |
performance rather than closed-book design synthesis. This is intentional for
|
| 151 |
the default open-book track and should be disclosed in any leaderboard or
|
| 152 |
paper claim.
|
| 153 |
- Some upstream projects have restrictive or unclear redistribution terms. See
|
| 154 |
`LICENSES.md` and per-source license notices before republishing subsets.
|
| 155 |
+
- The current canary suite validates frozen references, structural fail canaries,
|
| 156 |
+
and generated mutation canaries. Additional mutation types should be added for
|
| 157 |
+
future releases, especially swapped pins, missing pull-ups, missing
|
| 158 |
+
decoupling, and active devices without power/ground.
|
| 159 |
|
| 160 |
## Maintenance
|
| 161 |
|