ExpertQuestion 49 of 161

How do you compare two floorplans without cherry-picking metrics?

From PDVerse PnR Interview Handbook, part of the pdVerse Mentor Guide

Short Answer

The core discipline here is simple to state and easy to violate under deadline pressure: decide what you're measuring and how you're measuring it before you look at which floorplan wins on that metric โ€” otherwise you'll unconsciously pick the metrics that favor whichever option you already prefer. Build one scorecard with declared, written-down definitions for area/utilization, usable-row count, macro legality, channel feasibility, pin constraints, congestion, PG reservation, voltage-area legality, early timing, and change risk โ€” and apply the exact same measurement method to both floorplans.

Technical Reference DiagramHow do you compare two floorplans without cherry-picking metrics?

Technical Explanation

  • "
  • Record the measurement settings alongside every number โ€” what tool mode, what scenario, what effort level was used to generate each metric โ€” because a favorable number produced with looser settings than its competitor is not a fair comparison.
  • "
  • Finally, test sensitivity to expected design growth โ€” a floorplan that wins narrowly today but has much less margin for the design's expected growth is a worse long-term choice even if this round's scorecard looks close.

Formula Or Decision Rule

Decision rule: reject hard stops, then choose the lower owned risk across project priorities.

What To Check

  • Warning sign: Each advocate reports only the metric their option wins.
  • Inspect: choose one affected region, macro, row, pin, path, or net and trace the physical cause.
  • Correct: Recompute the full scorecard and require explanations for every material delta.

Command Checks & Actions

  • report_design -floorplan: reports the floorplan state understood by the tool
  • report_congestion -mode summary: reports routing demand, capacity, overflow, or hot spots
  • estimate_timing: performs early virtual timing estimation
  • report_timing: reports timing paths in the active analysis context

Run only the commands needed for this question. Save the report with the floorplan version and analysis context.

Healthy, Suspicious & Hard-stop Results

  • Healthy: Use one scorecard with declared definitions and identical methods for area/utilisation, usable rows, macro legality, channels, pins, congestion, PG reservation, voltage areas, early timing, and change risk.
  • Hard stop: required legality or physical feasibility is missing or unexplained.

Common Mistake

The Trap: Do not hide the symptom with an arbitrary utilisation, halo, channel, blockage, pin move, or die-size change.

What The Interviewer Is Testing

โ€ to measurable physical evidence and an owned correction.

Follow-up Question & Model Response

"* Candidate Model Response: Model response: โ€œI would change it if the same controlled rerun shows that each advocate reports only the metric their option wins. โ€

Physical Design & Planning Handbook

Dive into 14 comprehensive chapters covering netlist sanity, FinFET grids, macro placement, power grids, CTS, and timing budgeting.

Offline PDF Bundle

Want all 1109 questions offline?

Get the complete 4-book PDF bundle (PnR, STA, MMMC, Low Power) with a clickable table of contents - no ads, no internet needed.

See what's inside the bundle
PnR Flow Physical Design Mentor Guide โ€” eight chaptersPnR Flow Mentor GuideEight chapters, library setup through to stream-out.