The kpex --check command on a sky130A netlist with units KLayout expects fails on correct devices and exits 1, while the same lines without units pass. Two tools in one flow read the same SPICE line at different scales: schematic MOSFET sizes in microns, KLayout in metres.

Recurring agent failure issue in klayout-pex (iic-jku)

klayout-pex (iic-jku)ECADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in klayout-pex (iic-jku) that mostly hits the electrical engineer.

Failure pattern: validation / failure

Analyst note

From the Grok pain-radar digests, Nov 9-10 2026 (Nov 9 7:41 AM ET through Nov 10 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-10: issue/PR read; title and state confirmed.

What it costs a team

Modeled annual cost

$30,000

For a team of 5

Prototype delay

3 days

Modeled schedule slip per occurrence

Time lost

240 min

Per engineer per month, about 1 incidents

How the cost is modeled

240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000

A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.

Engineering tools that address it

No engineering tool profile lists this error yet. Browse tools that connect to klayout-pex (iic-jku).

Evidence

  1. 1iic-jku/klayout-pex Issue #497: kpex --check: `M` lines of a `sky130A` `--schematic` count in µm, while KLayout reads them in metresgithub.com

More recurring errors in klayout-pex (iic-jku)

See all 7 klayout-pex (iic-jku) errors

Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.