Games / Call the number

Call the number measured, not estimated

A summary of a real run is shown, then a question about one of its numbers: over or under. The true value is revealed on a scale afterwards, so a wrong call still shows how far off it was. Choose a family of metrics, or take them all mixed together.

SourceEach summary describes a real run, and the number revealed afterwards is what that run produced. Guessing the direction is the point: a physical designer who knows roughly what a metric should be is the one who notices when a run has gone wrong. Reference: the OpenROAD documentation (OpenROAD-flow-scripts on GitHub).

Every metric

A mixed round drawn from every family, which is how the numbers arrive in real life.

41summaries across 5 families

mixed round play

Area and utilization

How much silicon a design ends up occupying, and what changes it.

cell areautilizationrepair growth

6 summaries play

Wires and routing

How much metal it takes to connect a design, and what makes it more.

wire lengthlayersspread

10 summaries play

Power and voltage drop

What a design draws, and what the grid does with it.

total powervoltage dropgrid

8 summaries play

Counts and the cell mix

How many cells a design really ends up with, and what they all are.

instance countfillclock buffersrepair

9 summaries play

Speed

How fast a block can actually run, and what changes that.

minimum periodmaximum frequencyslack

8 summaries play