The GF180 KLayout LVS deck does not read the VNW and VPW well labels, so check_ports flags missing ports and fails every cell in two libraries, even though device and net comparison succeed. The verification result is wrong because two files disagree on where labels live.

Recurring agent failure issue in globalfoundries-pdk-libs-gf180mcu_fd_pv (fossi-foundation)

globalfoundries-pdk-libs-gf180mcu_fd_pv (fossi-foundation)ECADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in globalfoundries-pdk-libs-gf180mcu_fd_pv (fossi-foundation) that mostly hits the electrical engineer.

Failure pattern: agent / 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 globalfoundries-pdk-libs-gf180mcu_fd_pv (fossi-foundation).

Evidence

  1. 1fossi-foundation/globalfoundries-pdk-libs-gf180mcu_fd_pv Issue #46: KLayout LVS: every 7-track and 9-track standard cell fails `flag_missing_ports` because the deck does not read the VNW (21/10) and VPW (204/10) textsgithub.com

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.