How does the DRC heat map help triage thousands of violations?

Short Answer

A heat map shows where violations are dense instead of listing them one by one, so thousands of errors turn into a few clusters with a likely shared cause. In ICC2 you turn it on with signoff.check_drc.enable_icv_explorer_mode (ICC2) before signoff_check_drc (ICC2); it needs IC Validator P-2019.06 or later and an IC Validator NXT licence. Standalone, IC Validator Explorer DRC runs the high-priority checks first and opens its results with a heat map in VUE.

Technical Explanation

• Thousands of errors rarely have thousands of causes. A dense square over one macro corner or one channel usually means one cause such as a bad abstract, fill overlap or a crowded pin region.
• In ICC2: set the option to true, run signoff DRC, then choose View > Map > ICV Heatmap. You can select violation types and layers, change the number of bins and adjust transparency.
• Standalone icv -explorer (ICV) has three modes. standalone runs selected basic rules plus methodology checks; tiers runs everything in priority order; auto also stops slow rules on layers that already have many violations.
• Explorer tiers put methodology warnings, fill overlap diagnostics and priority rules in tier 0; lower-numbered tiers run first. In auto mode, rules in tiers 0 and 1 are never stopped early, and a clean design runs to full signoff results.
• The guide's debug order is methodology warnings, diagnostics, priority rules, user tiers, then all remaining rules. Zoom into the red regions, probe, repeat.
• icv -hm (ICV) turns on violation heat maps in a normal run, and -hm_cell (ICV) adds named cells. Explorer DRC needs Elite licensing with ICValidator-Manager and ICValidator2-GeometryEngine.
• A heat map shows where to look. Each cluster still needs its cause confirmed by reading real markers.

What To Check

• The top few dense bins and which rules and layers fill them.
• Whether clusters line up with macros, channels, fill or an ECO region.
• The Explorer tier 0 results first: methodology warnings and fill overlap.
• After each fix, whether the cluster disappears on the next run.

Healthy, Suspicious & Hard-stop Results

• Healthy (illustrative): Violations spread thinly with no bin above a handful, pointing to scattered fixable errors.
• Suspicious (illustrative): Over 70% of errors sit in 3 bins around one macro, a strong sign of one systematic cause.
• Hard stop: Tier 0 fill overlap or methodology warnings across the whole block. Fix that before looking at any single rule.

What The Interviewer Is Testing

• Knowledge of the ICC2 option and its licence and version needs.
• Understanding the Explorer modes and tier order.
• A strong answer treats clusters as causes to confirm.

Follow-up Question & Model Response

"When would you use Explorer auto mode instead of a normal full run?"

Candidate Model Response: When you do not know how many violations there are, for example the first run after fill or a big ECO. Auto mode runs the priority tiers first and stops slow rules on layers that already have many errors, so you get useful results much sooner. If the design is clean, auto mode stops nothing and gives full signoff results. With a known clean baseline and a small change, a normal or incremental run is enough.