How would you export or visualize clock tree QoR data instead of just reading a text report?

Short Answer

report_clock_qor supports -csv with -output <file> to export the report as CSV for spreadsheet analysis, and -histogram_type latency|transition|capacitance|local_skew|robustness|wire_delay_fraction to get a distribution view instead of a flat table -- useful for spotting outliers across hundreds of leaf sinks that a table alone would bury.

Technical Explanation

• report_clock_qor -csv -output <file> exports the report as CSV, meant for spreadsheet analysis rather than reading in the shell.
• -histogram_type latency|transition|capacitance|local_skew|robustness|wire_delay_fraction gives a distribution view instead of a flat table.
• The distribution view matters specifically because a flat table of hundreds of leaf sinks can hide a small cluster of real outliers that a histogram makes visually obvious.

Follow-up Question & Model Response

"Why would a histogram of local_skew be more useful for finding a problem than a histogram of latency?"

Candidate Model Response: Because local_skew is the metric most likely to reveal a small cluster of genuinely problematic sinks -- a latency histogram mostly reflects tree depth and topology, which is expected to vary, while a local_skew outlier cluster is a real signal something specific is wrong.