Vyges Loom

vyges-power

Power analysis — leakage + internal + switching from a netlist and activity, against a budget. Emits the per-instance activity that em-ir needs.

View source on GitHub →

What it does

Used by: teams who need a power number early — and the activity map that makes IR-drop analysis real.

vyges-power reads a gate-level netlist and the Liberty models and computes power — leakage, internal, and switching — from either a vectored activity file (VCD) or vectorless probabilistic toggling. Just as importantly, it emits the per-instance activity / current map that vyges-em-ir consumes, so IR-drop is solved from real per-instance current instead of a worst-case assumption — closing the char → power → em-ir loop.

netlist + .lib + activity (VCD / vectorless)  ──►  vyges-power  ──►  power report + activity map → em-ir

One declarative job

A .pwr job file declares the netlist, the Liberty models, the activity source, and the budget. It can read extracted wire caps (.spef) from vyges-extract for switching power, and writes the activity annotation em-ir reads — one cross-engine spine, no glue scripts.

One declarative job in; a power report out, plus the activity map downstream. --fail-on-budget gates CI.

Try it

$ vyges install loom   # one-time: fetch the Loom suite into ~/.vyges/bin
$ vyges loom power demo   # instant — built-in design, no setup
$ vyges loom power run block.pwr   # leakage + internal + switching report
$ vyges loom power run block.pwr --fail-on-budget   # exit 3 over budget — CI gate

Open core · Apache-2.0

Open and runnable today, and inside VyBox Sley. See all the engines & the data spine →