Why inspect active analysis types in each scenario?
From PDVerse PnR Interview Handbook · pdVerse Mentor Guide
Short Answer
A scenario can exist while setup, hold, or other required analysis is inactive.
Technical Explanation
A scenario is the active pairing of a mode and a corner. A name in the database is useful only when the required analyses and constraints are active in it.
What To Check
• Warning sign: The MCMM matrix has all expected names but omits the critical check type. • Inspect: Compare one named object across the related reports; the same object should tell a consistent story. • Correct: Correct scenario status in the setup and rerun coverage reports across the required matrix.
Command Checks & Actions
• report_scenarios: shows the MCMM scenario matrix and analysis status
Run the commands in order. Each line answers a separate part of the check.Healthy, Suspicious & Hard-stop Results
• Expected: A scenario can exist while setup, hold, or other required analysis is inactive. • Investigate: The MCMM matrix has all expected names but omits the critical check type. • Stop before floorplanning when required logic or timing coverage is missing or unexplained. Correct scenario status in the setup and rerun coverage reports across the required matrix.
Common Mistake
Do not assume the check passed just because ICC2 continued: The MCMM matrix has all expected names but omits the critical check type. Fix or narrowly justify the named objects, then rerun the same command.
What The Interviewer Is Testing
Be ready to explain why this matters before floorplanning: The MCMM matrix has all expected names but omits the critical check type.
Follow-up Question & Model Response
Model response: “I would save the report, inspect one affected object in the correct block and scenario, and make or request this correction: Correct scenario status in the setup and rerun coverage reports across the required matrix. Then I would reopen the clean checkpoint and rerun the same evidence.”
Practical Example
Symptom: The MCMM matrix has all expected names but omits the critical check type. Corrective path: Correct scenario status in the setup and rerun coverage reports across the required matrix.
Continue practising