W1.5.2 Vectorless or Recorded?

MediumDebug20 minOpenROAD · recorded experimentsReview the topic

Two recorded power reports of one multiplier disagree by a factor of five. Find out why, and decide which one goes into the budget.

Hardware context: Activity recorder on a bus, and recorded power reports of a multiplier. Turn waveforms into SAIF totals and judge how much of an estimate rests on recorded activity.

An 8 × 8 multiplier block (1,017 cell pins) gets new operands in every cycle. Its product is used in about one cycle in ten. One simulation of that workload was dumped twice: once from the RTL, once from the synthesized netlist.

Report A read the RTL VCD and says 1.265 mW. Report B read the netlist VCD and says 0.241 mW. Both used the same netlist, corner and clock. Each report came with its annotation summary.

Name the cause of the gap. Give the share of pins that report A annotated from its file, in per cent. Then say which report you would put in the power budget.

Requirements

RequirementLimitUnit
The cause you named explains the gap= 1count
Error of your annotated share for report A≤ 0.5%
The report you would use for the power budget= 1count

Recorded experiments: Recorded build-time OpenSTA 3.1.0 runs on the opiso0 netlist: sky130_fd_sc_hd, tt, 10 ns clock (probe tools/probes/lowpower/activity-data.mjs, 2026-11-12). Both read a VCD of the same Icarus run of the same workload. No tool runs during grading.

Full specification

Report A (RTL VCD):

GroupInternal (W)Switching (W)Leakage (W)Total (W)
Sequential7.832e-50.000e+01.312e-107.832e-5
Combinational6.737e-45.127e-48.486e-101.186e-3
Clock0.000e+00.000e+00.000e+00.000e+0
Total7.520e-45.127e-49.798e-101.265e-3
Report A: report_activity_annotation
vcd             50
unannotated    967

Report B (netlist VCD):

GroupInternal (W)Switching (W)Leakage (W)Total (W)
Sequential6.854e-50.000e+01.305e-106.854e-5
Combinational9.199e-58.000e-58.443e-101.720e-4
Clock0.000e+00.000e+00.000e+00.000e+0
Total1.605e-48.000e-59.748e-102.405e-4
Report B: report_activity_annotation
vcd           1017
unannotated      0

Recorded build-time OpenSTA 3.1.0 runs on the opiso0 netlist: sky130_fd_sc_hd, tt, 10 ns clock (probe tools/probes/lowpower/activity-data.mjs, 2026-11-12). Both read a VCD of the same Icarus run of the same workload. No tool runs during grading.

The share check compares your number with report A's summary, within 0.5 percentage points.

Examples

Example 1

Blame the Leakage
Input
{
  "cause": "leakage",
  "annotated_percent": 4.9,
  "use": "B"
}
Output
The cause you named explains the gap: 0
Error of your annotated share for report A: 0 %
The report you would use for the power budget: 1

Compare the columns that differ, then read both annotation summaries.

Example 2

Blame the Clock
Input
{
  "cause": "clock",
  "annotated_percent": 4.9,
  "use": "B"
}
Output
The cause you named explains the gap: 0
Error of your annotated share for report A: 0 %
The report you would use for the power budget: 1

Compare the columns that differ, then read both annotation summaries.

Example 3

Trust the Bigger Number
Input
{
  "cause": "workload",
  "annotated_percent": 100,
  "use": "A"
}
Output
The cause you named explains the gap: 0
Error of your annotated share for report A: 95.1 %
The report you would use for the power budget: 0

Compare the columns that differ, then read both annotation summaries.

Submission Rules

  • Submit one JSON object with every documented field.
  • Run checks your answers against the recorded reports. Submit applies the same requirements and records the result.
  • The numbers are estimates for one corner and one workload.

Hints

Hint 1

Compare the reports column by column. Which columns hold the gap, and which are tiny in both?

Hint 2

The Clock row is the same in both. Is there a clock tree in this netlist at all?

Hint 3

Divide the annotated pins by all pins. Then ask where the activity of the other pins came from.

What is checked: Recorded build-time OpenSTA 3.1.0 runs on the opiso0 netlist: sky130_fd_sc_hd, tt, 10 ns clock (probe tools/probes/lowpower/activity-data.mjs, 2026-11-12). Both read a VCD of the same Icarus run of the same workload. No tool runs during grading.

Run and Submit use the same measured requirements. Run is a preview; Submit records an attempt. No physical tool runs during this exercise; the records come from the pinned build-time experiments.

More problems on this topic

Report a problem with this page

Your configuration JSONSaved locally
Ln 1, Col 1Ctrl/⌘ + Enter runs
Not run yet

Run your configuration to inspect the result.

OpenROAD · recorded experiments