What does a sigma value in a POCV Liberty variation table actually represent?
From PDVerse STA Mentor Guide ยท pdVerse Mentor Guide
Short Answer
Sigma is the standard deviation of a cell delay's expected spread around its mean value if you could measure that same cell many times across normal manufacturing variation. A larger sigma means the real delay is more likely to land far from the mean; the tool combines each arc's sigma with its neighbors statistically instead of assuming every arc's delay lands at its absolute worst value at once.
Technical Explanation
POCV treats each cell's delay as a distribution, not a single fixed number, and sigma is what describes the width of that distribution.
- Mean is the expected, most likely delay value. The library's
ocv_std_dev_cell_rise(LIB) style table pairs a mean delay with a sigma for the same rising-transition arc, at a given input slew and output load. - Sigma measures spread, not direction. A sigma of 5ps means most real instances of that arc's delay across the chip will land within a few multiples of 5ps of the mean, in either direction, following the normal-distribution assumption the tool uses.
- Combining sigmas is not the same as adding worst cases. If a path has ten arcs each with their own sigma, the tool statistically combines all ten sigmas into one path-level sigma, rather than assuming every arc hits its own worst extreme delay at the same time.
- The output is still a single number for signoff. The tool converts the combined mean and sigma into an effective delay at some number of sigmas out โ for example, three sigmas โ giving one concrete number a report can show, even though the underlying model is statistical.
- Sigma values can vary by transition and load. A more accurate library uses an LVF (Liberty variation format) table so sigma itself changes with input slew and output load, rather than one fixed sigma for every condition on that arc.
- Why the distinction matters: treating a sigma value as if it were just another fixed derate percentage misses the point that POCV's advantage comes specifically from combining many independent spreads statistically, not from a single conservative number.
Common Mistake
The Trap: reading a POCV sigma value as if it were simply a derate percentage on the mean delay, and mentally adding up every arc's sigma along a path to estimate the total.
- A designer sees a 5ps sigma on each of ten arcs and assumes the path's total variation is 50ps, treating the sigmas as if they simply stack.
- Independent sigmas combine statistically, not by simple addition, so the real path-level spread is smaller than that naive sum โ misreading this can make a design look far riskier than it actually is.
Follow-up Question & Model Response
A path has ten arcs, each with a sigma of about 5ps. A colleague estimates the path's total variation at 50ps by adding them up. Is that right?
Candidate Model Response: Not for independent random variations โ that estimate overstates the real spread. When ten independent sigma values combine statistically, the combined sigma grows roughly with the square root of the number of arcs rather than linearly, so ten arcs at 5ps each combine to something closer to 16ps, not 50ps. This is exactly the effect that makes POCV less pessimistic than adding up worst cases: independent variations partly cancel each other out rather than all pushing in the same direction at once. I would let the tool compute the combined sigma directly rather than approximating it by hand, since the exact combination depends on each arc's specific correlation assumptions.
Practical Example
A 10-stage datapath has each arc's ocv_std_dev_cell_rise (LIB) sigma reported around 5ps by report_timing -derate (PT) under POCV. Naively summing ten sigmas would suggest 50ps of spread, but the tool's statistical combination reports a path-level sigma closer to 15ps. Signoff derates the path at three combined sigmas, adding about 45ps of margin instead of the 150ps a naive worst-case sum would have demanded, recovering real slack without reducing statistical coverage.
Complete STA Handbook
Master Signoff-Ready Static Timing Analysis
Get the complete 10-chapter STA handbook covering setup/hold margins, clock modeling, OCV/POCV, crosstalk noise, and PrimeTime closure.

Continue practising