This is the code for writing triples. <https://git...
# openlane
It seems that would be an OpenRoad issue then?
not obviously, since the STA tool itself focuses on min/max timing checks, they might not wish to consume memory for unused typical timing
but again, there is report_power, which is often observed at typical timing
I tried a few ways to get the typical timing out, but I soon get conflicts with previously executed steps. So I decided to try to get some support, before I waste too much time.
It seems that just averaging min/max might be the way to go. This is for a given corner, right? So I'm not sure what typical would be in the context of STA which finds max and min paths...