Report formats

In Timing Review you load a PrimeTime, Fusion Compiler, Tempus or Innovus report folder, select a stage, and Lens indexes all its scenarios and clocks automatically.

Supported formats

Format	Status
ICC2 `report_timing.min` and `report_timing.max`	Shipped
PrimeTime `report_timing`	Shipped
Clock QoR summary	Shipped
PrimeTime constraint PBA	Shipped
Cadence Tempus (STA, scenario-shaped)	Supported, development-grade
Cadence Innovus (implementation, stage-shaped)	Supported, development-grade

The Fusion Compiler format is the report_timing.min and report_timing.max report pair that Fusion Compiler and IC Compiler II both write; older Lens documentation calls it the ICC2 format, and it is the same format. In Lens it is the Fusion Compiler tool flow.

Lens reads Tempus and Innovus reports with its Cadence parser and labels each with its own report dialect and unit basis.

Development-grade means the Cadence parsers are in the product and read real Tempus and Innovus reports, but the verification sweep against real vendor output that promotes a format to shipped has not been completed for them. For you it means: use Tempus and Innovus results, but check them against the raw report before relying on a number, and tell the Lens team about any report Lens misreads.

Lens does not support Calibre or StarRC parasitics, .sdf files or custom TCL summaries.

Files Lens looks for

Timing reports

You need at least one of the two timing reports below, SETUP and HOLD; for PrimeTime you need both. For what the two checks mean, see Setup and hold.

Report	Fusion Compiler (FC)	PrimeTime (PT)	Used for
SETUP timing	`report_timing.max`	`_max_timing_GBA.rpt` or `_max_timing_PBA.rpt`	SETUP WNS and TNS, violating paths, per-clock SETUP metrics, path analysis
HOLD timing	`report_timing.min`	`_min_timing_GBA.rpt` or `_min_timing_PBA.rpt`	HOLD WNS and TNS, violating paths, per-clock HOLD metrics, path analysis

A PrimeTime scenario needs both reports unless the project's one-sided scenario opt-in is on (in Settings, under Data Sources). Without the opt-in, a PrimeTime scenario with one side missing is reported as incomplete and is not analyzed; Lens never saves the missing side as 0.0. See A scenario is reported incomplete.
Fusion Compiler works with either report.

Optional reports

Report	Typical pattern	Adds
Clock QoR summary (FC and PT)	`report_clock_qor.summary`, `report_qor`	Latency, skew, sinks and CTS levels, and the CTS suggestion rule
Constraint PBA (PT)	`_constraint_PBA.rpt`	Per-clock WNS and status in Corner Sensitivity

Lens also reads these optional files when you configure them; none is required for Timing Review:

File	Where it is used
Fusion Compiler `report_pvt` (Report : pvt)	Corner Sensitivity, for each scenario's voltage, temperature and process
Clock inventory reports (`*_clock.rpt`, also `.gz`)	The clock list and clock types
Local skew (`report_clock_qor.local_skew`) and DRV reports (`report_qor.start`, `icc2_drv.rpt`)	Skew and design-rule details in the Timing Review alerts and suggestions
SDC constraint files	Reference only: Digital Soul's constraint-evidence review reads them to check constraints; Lens never writes them and never uses them for timing

Compressed (.gz) reports and nested subdirectories are supported.

Units

PrimeTime reports are always in nanoseconds; there is nothing to configure.

A Cadence report states no time unit: the unit is a property of the cell library, which Lens never sees. Set Settings → Timing unit for Cadence reports to ns or ps; the setting is per project. Until you set it, numbers from Cadence reports show an explicit "unit unknown" marker.

Fusion Compiler reports, like PrimeTime reports, are always read in nanoseconds; the setting applies only to Cadence reports.

Cadence reports

Lens detects a Cadence report by its file content, not by a tool-flow setting. Point Lens at one and it goes to the Cadence parser automatically.
A Cadence run writes one report, so its scenarios are one-sided by nature: a scenario has only a setup or only a hold report. A project with a Cadence source has the one-sided scenario opt-in turned on once, automatically; if you turn it off afterwards, it stays off. With the opt-in on, the missing side shows as not measured (—), never as 0.0 or clean.
The cell/interconnect split on a Cadence -net report rests on a single real Innovus report, and everywhere Lens shows the split, it says so. Row shapes Lens has not seen are declined rather than guessed.

Truncated and violation-only reports

If your PrimeTime or Fusion Compiler run truncates paths with report_timing -max_paths, Lens TNS will be understated. That is a property of the source report, not a Lens defect, so check your -max_paths setting before quoting TNS.
A violation-only report (report_timing -slack_lesser_than 0) carries no passing margin, so passing clocks show N/A rather than 0.

Still have a question?

Updated 19 October 2026