Require both timing directions and electrical limits in a reusable report checker.
Hardware context: Mapped sequential paths under timing and load stress. Reject timing and electrical failures without rejecting valid implementations.
A path can pass setup and still fail hold, or have positive slack while violating an electrical limit. Write a checker for the four metrics in the supplied report.
Accept varied good timing reports and reject setup, hold and heavy-load failures. The fixture reports use their stated internal-path scopes; this exercise assumes coverage was reviewed separately.
Requirements
| Requirement | Limit | Unit |
|---|---|---|
| Maximum slack | ≥ 0 | ns |
| Minimum slack | ≥ 0 | ns |
| Slew violations | = 0 | count |
| Capacitance violations | = 0 | count |
Live analysis: Fresh TT ideal-wire OpenSTA reports with propagated clock delay where present. Required metrics are maximum slack, minimum slack, slew-violation count and capacitance-violation count.
Public Report
{
"setup": 0.9002,
"hold": 0.0324,
"slew": 0,
"capacitance": 0
}Full specification
| Report metric | Meaning |
|---|---|
| setup | Maximum slack in ns; require at least zero. |
| hold | Minimum slack in ns; require at least zero. |
| slew | Slew violations; require zero. |
| capacitance | Capacitance violations; require zero. |
Fresh TT ideal-wire OpenSTA reports with propagated clock delay where present. Required metrics are maximum slack, minimum slack, slew-violation count and capacitance-violation count.
Numeric checks use inclusive bounds. A missing measurement always fails. Only the documented fields are accepted.
Examples
Example 1
One Lower Bound- Input
{ "checks": [ { "metric": "setup", "min": 0.9002 } ] }- Output
PASS on the public sample
This example checks one metric. A complete checker must cover all the specified requirements.
Example 2
A Bound Above the Sample- Input
{ "checks": [ { "metric": "setup", "min": 1.9002 } ] }- Output
FAIL on the public sample
The supplied report is unchanged. Tightening a limit changes the checker’s verdict.
Example 3
An Exact Check- Input
{ "checks": [ { "metric": "setup", "equals": 0.9002, "tol": 0 } ] }- Output
PASS on the public sample
Exact equality is useful for required zero counts. Valid timing values may vary across good reports.
Submission Rules
- Write a JSON object with a checks array. Each entry names one metric and min/max or equals with optional absolute tol.
- All checks must pass for the report to pass. Missing and nonfinite values fail.
- Run applies your checker to the public reference. Submit also tests hidden good and faulty reports.
Hints
Hint 1
Maximum and minimum timing are separate comparisons.
Hint 2
Violation counts require equality to zero.
Hint 3
Avoid requiring an exact slack value: correct implementations have different margins.
What is checked: Fresh TT ideal-wire OpenSTA reports with propagated clock delay where present. Required metrics are maximum slack, minimum slack, slew-violation count and capacitance-violation count.
Run checks the public report. Submit checks the reference, at least two additional good reports and at least three faulty reports. The fixed circuit and allowed settings use the pinned OpenROAD/OpenSTA engine.
More problems on this topic