What does report_clock_qor actually show you, and what do its -type variants each report?

Short Answer

report_clock_qor is the summary command for clock tree quality: latency, skew, DRC violations, area, and buffer count in its default form. The -type option narrows it: -type latency for longest/shortest path, -type drc_violators for max transition/capacitance violators, -type robustness for cross-corner ratio, -type balance_groups for interclock balance QoR, -type local_skew for worst local skew per group, and -type power for per-clock power breakdown.

Technical Explanation

• report_clock_qor's default form is a summary: latency, skew, DRC violations, area, and buffer count.
• -type latency reports the longest and shortest path in the tree.
• -type drc_violators reports max transition and max capacitance violators specifically.
• -type robustness reports a cross-corner ratio (a sink's latency at the reporting corner versus a required -robustness_corner).
• -type balance_groups, -type local_skew, and -type power report interclock balance QoR, worst local skew per clock/skew group, and per-clock power breakdown respectively.
• -csv and -output let you export the report; -histogram_type gives a distribution view instead of a table.

Follow-up Question & Model Response

"If you only had time to run one -type variant before signoff, which would you pick and why?"

Candidate Model Response: -type drc_violators, since an undetected max-transition or max-capacitance violation is a hard electrical defect, whereas most latency/skew numbers can still be triaged and fixed later in the flow with more margin for iteration.