Synthesis & Logic Optimization · All levels

Scenario: QoR Storm: Reports & Metrics

Reports & Metrics for Scenario: QoR Storm.

Reports and metrics

Reports & Metrics for Scenario: QoR Storm focuses on overnight WNS/TNS regression with no RTL intent change. The goal is to connect observed QoR movement to mechanism, ownership, and regression risk.

A report is useful only when it supports decisions. For Scenario: QoR Storm, read metric movement with baseline context and expected budget.

Metric movement

diagram
QOR TREND — Scenario: QoR Storm

metric quality
  ^
  |                      target band
  |                o  o  o
  |            o
  |      o  regression
  +----------------------------------> synthesis iteration
   baseline    tuning     signoff-ready

Track: overnight WNS/TNS regression with no RTL intent change
  • Track overnight WNS/TNS regression with no RTL intent change with exact run manifests.

  • Keep timing/area/power side-by-side in review dashboards.

  • Require one-sentence mechanism hypothesis for every major delta.

  • Store before/after artifacts with owner signoff.

Synthesis deep dive

Interview readiness comes from repeatable QoR reasoning under pressure.

Concept diagram

diagram
INTERVIEW ANSWER SHAPE

context -> metric -> mechanism -> fix -> regression -> ownership

Metric graph

diagram
PANEL SCORING

clarity      ███████
mechanism    ██████
regression   █████

Reports and artifacts

  • mock scorecard

  • scenario debrief

  • Q&A coverage

  • framework adherence

Mini case study

Candidate improved by replacing tool-command answers with evidence-driven closure narratives.

Debug branches

  • State assumptions first

  • Defend option tradeoffs

  • Close with rollback/regression

Senior review question

Ask: what evidence proves this QoR move is real and stable?

Key takeaways

  • State exact run context (RTL, SDC, libs, switches) with every QoR claim.

  • Re-run timing, area, and power regressions after each synthesis ECO.

Common pitfalls

  • Comparing runs with mismatched constraints or library views.

  • Timing-only fixes that violate power or area budgets.

  • Skipping equivalence checks after structural changes.

Report reading lens