Measure PPA
Read the selected rows in <project>/reports/flow_engine.json and open their
native reports. flow/steps.json names each current tool and
flow/native_limits.json retains its original limits. Review tool_ran,
native_steps, native_metrics, and each metric's value, operator and limit.
A missing native measurement is NOT_MEASURED. AI reviews the engineering
meaning of every result and fixes problems in the design, tool or plugin.
python3 programs/flow_engine.py report --project <project>
Collect the numbers from the tool's actual outputs. Name the design, top,
stage, corner, mode, Liberty files, activity basis and parasitics used.
- Read cell area and cell counts from the synthesis or physical database.
Distinguish cell area, macro area, core area and die area, and keep their units.
- Read setup and hold WNS, TNS, unconstrained paths and DRV from native timing
reports. Identify whether timing used estimated or extracted parasitics.
- Read power with its voltage, process/temperature corner and switching-activity
basis. Missing activity is a limitation, not measured design power.
- Read wirelength, via counts, congestion and physical violations from the
native implementation reports when those measures were requested.
Write a table with each measured value, units, original requirement, result
and source path. Report an absent value as NOT_MEASURED. Do not replace it
with zero, an estimate, a stale report or a hash-bound claim. Explain any
reused measurement's actual scope. Review physical plausibility and state
what the run did not measure. Early estimates belong in ppa-predict.
1---2name: ppa-measure3description: Read PPA artefacts that the tools already wrote — STA reports, power reports, area reports, DEF/GDS summaries — and turn them into an evidence-linked measurement report of canonical `vibeic.ppa.metric.v1` records, each carrying its scope and its native source path. Use when the user says "measure PPA", "what is the real area/power/timing", "collect the PPA numbers", "post-route PPA", or when a report must state what was measured AND what was not.4metadata:5 source: https://skillmd.com/skills/vibeic/ppa-measure6---78# Measure PPA910Read the selected rows in `<project>/reports/flow_engine.json` and open their11native `reports`. `flow/steps.json` names each current tool and12`flow/native_limits.json` retains its original limits. Review `tool_ran`,13`native_steps`, `native_metrics`, and each metric's value, operator and limit.14A missing native measurement is `NOT_MEASURED`. AI reviews the engineering15meaning of every result and fixes problems in the design, tool or plugin.1617```bash18python3 programs/flow_engine.py report --project <project>19```2021Collect the numbers from the tool's actual outputs. Name the design, top,22stage, corner, mode, Liberty files, activity basis and parasitics used.2324- Read cell area and cell counts from the synthesis or physical database.25 Distinguish cell area, macro area, core area and die area, and keep their units.26- Read setup and hold WNS, TNS, unconstrained paths and DRV from native timing27 reports. Identify whether timing used estimated or extracted parasitics.28- Read power with its voltage, process/temperature corner and switching-activity29 basis. Missing activity is a limitation, not measured design power.30- Read wirelength, via counts, congestion and physical violations from the31 native implementation reports when those measures were requested.3233Write a table with each measured value, units, original requirement, result34and source path. Report an absent value as `NOT_MEASURED`. Do not replace it35with zero, an estimate, a stale report or a hash-bound claim. Explain any36reused measurement's actual scope. Review physical plausibility and state37what the run did not measure. Early estimates belong in `ppa-predict`.