What is scenario or view explosion, and why not just analyze every mathematical mode-times-corner combination during optimization?
From PDVerse MMMC Interview Masterclass, part of the pdVerse Mentor Series
Direct answer
Scenario explosion occurs when multiplying multiple modes by many physical corners produces hundreds of analysis views (e.g. 10 modes × 15 corners = 150 views), exhausting memory and bloating PnR runtimes. The solution is dominant scenario pruning during PnR, expanding to the full matrix for final signoff.
Mentor explanation
Managing view explosion balances PnR turnaround time with signoff coverage.
Key terms
- Scenario explosion — combinatorial growth of analysis views (Modes × Corners = Views).
- Dominant scenario pruning — identifying the subset of views (e.g. 8–16 views) that constrain 95%+ of critical paths during placement and routing.
- Full signoff expansion — reactivating all 100+ views for final PrimeTime/Tempus signoff verification.
- Multi-scenario runtime scaling — memory and CPU usage scale linearly with active scenario count during PnR optimization.
Pruning non-dominant scenarios during early implementation accelerates turnaround time without compromising final signoff quality.
Practical example
Managing View Explosion:
+-----------------------------------+-----------------------------------+
| PnR Optimization (Innovus/ICC2) | Final Signoff Audit (PrimeTime) |
+-----------------------------------+-----------------------------------+
| • 8 - 16 Dominant Active Views | • 100% Comprehensive Matrix (192) |
| • Fast turnaround & memory fit | • Distributed over 50 server cores|
| • Closes 98% of all violations | • Guarantees zero corner escapes |
+-----------------------------------+-----------------------------------+Interview trap
Attempting to optimize all 100+ mathematical mode-corner combinations during initial floorplanning and placement. This causes severe runtime and memory bottlenecks without improving QoR.
Key takeaways
- View explosion occurs from the combinatorial multiplication of modes, PVT corners, and RC corners.
- Optimizing too many views simultaneously exhausts RAM and degrades PnR tool convergence.
- Best practice: Prune to 8–16 dominant views during PnR; execute the full comprehensive matrix during distributed signoff STA.
Self-check: can you answer this aloud?
Try a 45-second answer using this structure:
- State the direct answer.
- Explain the timing or physical reason.
- Name one caveat.
- Say how you would verify it in a real flow.
MMMC Signoff Guide
Master Multi-Mode Multi-Corner Timing Signoff
Explore the full 10-chapter MMMC guide on modes, PVT corners, RC parasitics, analysis views, and correlation between implementation and signoff tools.
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.
Keep connecting concepts