A synthesis result is only as good as the flow that produced it. This topic turns one-off runs into scripted flows with logged runs and nightly regression.
Term | Meaning |
|---|---|
Flow as code | A versioned script that runs every stage the same way on every run. |
QoR | Quality of results: area, timing slack and power read from each run. |
Regression | A nightly rerun compared against a baseline through thresholds. |
Threshold band | The allowed wiggle, such as 5% on area, that separates noise from change. |
Pinned version | A recorded tool, library and script revision that every rerun reuses. |
Lesson | What it covers |
|---|---|
Stages, parameters, and pinned versions of a scripted flow. | |
One width-parameterised adder run at widths 4 and 8 with asserted counts. | |
Run logs and the area, slack and power record of each run. | |
An EXAMPLE baseline against current runs with a runnable comparator. | |
Threshold bands and pinned reruns that separate noise from change. |
Noise until a pinned rerun says otherwise. A move inside the band on unchanged inputs is rerun variation, not a result.