Vyges Loom

vyges-sta-si

Static timing analysis with signal integrity — WNS / TNS and the worst path, from one declarative job, with a CI gate that fails on a violation.

View source on GitHub →

What it does

Used by: platform and PD teams gating timing on every commit — sign-off as a check, not a late-stage review.

vyges-sta-si checks whether the design meets timing — reporting worst negative slack (WNS), total negative slack (TNS), and the critical path — while accounting for signal-integrity coupling between nets (crosstalk-induced delay and noise effects). It reads the .lib from vyges-char and the .spef from vyges-extract — the two upstream artifacts on the spine. The timing results and slack metrics are sign-off compatible with standard Liberty and SPEF inputs — no proprietary formats, no hidden transforms.

.lib + .spef + design & constraints  ──►  vyges-sta-si  ──►  WNS / TNS / worst path

One declarative job · built to gate CI

A .sta job file declares the libraries, parasitics, and constraints. Standard CLI: --json, --quiet, --verbose — plus --fail-on-violation, which returns a distinct exit code so a timing violation fails your pipeline automatically. This turns timing sign-off from a late, manual review step into a deterministic CI check.

One declarative job in; one standard sign-off artifact out. Exits non-zero on violations — designed to gate CI, not generate PDFs.

Try it

$ vyges install loom   # one-time: fetch the Loom suite into ~/.vyges/bin
$ vyges loom sta-si demo   # instant — analyze a built-in design → WNS/TNS
$ vyges loom sta-si run top.sta -o top.rpt   # analyze → timing report
$ vyges loom sta-si run top.sta --fail-on-violation   # exit 3 if WNS < 0 (CI gate)

Open core · Apache-2.0

Open and runnable today, and inside VyBox Sley. The per-foundry calibration plugins (NDA) stay private. See all the engines & the data spine →