Datapoint Definitions¶
*NOTE: The value -1
, if not meaningful, indicates that the report/log from which the information is extracted wasn’t found (the stage responsible for it was skipped or failed).
Default Printed Information Variables¶
Variable |
Description |
---|---|
|
The directory of the design |
|
The name of the top level module of the design |
|
The name of the configurations file of the design |
|
The status of the flow at the end of the run. Extracted from total_runtime.txt |
|
The total runtime of running the process on the design. Extracted from total_runtime.txt |
|
The runtime of running the process up to (including) detailed routing on the design. Extracted from routed_runtime.txt |
|
The diearea in mm2 as reported from the def file. |
|
The number of cells in the design as reported by yosys divided by the diearea in mm2. |
|
The number of cells in the design as reported by yosys divided by the diearea in mm2, all divided by the FP_CORE_UTIL configuration parameter. |
|
The core utilization of the design. Extracted from openDP logs. |
|
The peak memory usage of Tritonroute during optimization iterations. Extracted from tritonRoute logs. |
|
The number of cells in the design. Extracted from yosys logs. |
|
The total number of violations from running TritonRoute. Extracted from tritonRoute logs. |
|
The total number of shorts violations from running TritonRoute. Extracted from tritonRoute drc. |
|
The total number of MetSpc violations from running TritonRoute. Extracted from tritonRoute drc. |
|
The total number of off-grid violations from running TritonRoute. Extracted from tritonRoute drc. |
|
The total number of MinHole violations from running TritonRoute. Extracted from tritonRoute drc. |
|
The total number of other types of violations from running TritonRoute. Extracted from tritonRoute drc. |
|
The total number of magic drc violations in the design. Extracted from Magic drc. |
|
The total number of antenna violations in the design. Extracted from Magic antenna check or OpenROAD ARC. |
|
The total number of mismatches and differences between the final layout and the netlist of the design. Extracted from Netgen LVS report. |
|
The total number of electric errors detected by CVC. Extracted from CVC report. |
|
The total number of klayout drc violations in the design. Extracted from klayout drc report ran on the magic generated GDSII. |
|
The total wire length in the design. Extracted from tritonRoute logs. |
|
The number of vias in the final design. Extracted from tritonRoute logs. |
|
Worst Negative Slack. Reported after Synthesis. Extracted from OpenSTA. |
|
Worst Negative Slack. Reported after global placement and before optimizations using estimate parasitics. Extracted from RePlAce/OpenSTA. If the report wasn’t found, the value from the previous STA report is used. |
|
Worst Negative Slack. Extracted from OpenSTA. If the report wasn’t found, the value from the previous STA report is used. |
|
Worst Negative Slack. Reported after global routing using estimate parasitics. Extracted from FastRoute/OpenSTA. If the report wasn’t found, the value from the previous STA report is used. |
|
Worst Negative Slack. Reported after routing and spef extraction. Extracted from OpenSTA. If the report wasn’t found, the value from the previous STA report is used. |
|
Total Negative Slack. Reported after Synthesis. Extracted from OpenSTA. |
|
Total Negative Slack. Reported after global placement and before optimizations using estimate parasitics. Extracted from RePlAce/OpenSTA. If the report wasn’t found, the value from the previous STA report is used. |
|
Total Negative Slack. Reported after OpenPhySyn optimizations. Extracted from OpenSTA. If the report wasn’t found, the value from the previous STA report is used. |
|
Total Negative Slack. Reported after global routing using estimate parasitics. Extracted from FastRoute/OpenSTA. If the report wasn’t found, the value from the previous STA report is used. |
|
Total Negative Slack. Reported after routing and spef extraction. Extracted from OpenSTA. If the report wasn’t found, the value from the previous STA report is used. |
|
Final value for the half-perimeter wire length. Extracted from RePlace logs. |
|
The percentage usage of routing resources on layer 1 in global routing. Extracted from fastroute log. |
|
The percentage usage of routing resources on layer 2 in global routing. Extracted from fastroute log. |
|
The percentage usage of routing resources on layer 3 in global routing. Extracted from fastroute log. |
|
The percentage usage of routing resources on layer 4 in global routing. Extracted from fastroute log. |
|
The percentage usage of routing resources on layer 5 in global routing. Extracted from fastroute log. |
|
The percentage usage of routing resources on layer 6 in global routing. Extracted from fastroute log. |
|
The number of wires in the design. Extracted from yosys logs. |
|
The number of wire bits in the design. Extracted from yosys logs. |
|
The number of public wires in the design. Extracted from yosys logs. |
|
The number of public wire bits in the design. Extracted from yosys logs. |
|
The number of memories in the design. Extracted from yosys logs. |
|
The number of memory bits in the design. Extracted from yosys logs. |
|
The number of cells before ABC. Extracted from yosys logs. |
|
The number of AND gates in the design. Extracted from yosys logs. |
|
The number of flip flops in the design. Extracted from yosys logs. |
|
The number of NAND gates in the design. Extracted from yosys logs. |
|
The number of NOR gates in the design. Extracted from yosys logs. |
|
The number of OR gates in the design. Extracted from yosys logs. |
|
The number of XOR gates in the design. Extracted from yosys logs. |
|
The number of XNOR gates in the design. Extracted from yosys logs. |
|
The number of multiplexers in the design. Extracted from yosys logs. |
|
The number of inputs in the design. Extracted from yosys logs. |
|
The number of outputs in the design. Extracted from yosys logs. |
|
The number of levels in the final design. Extracted from yosys logs. |
|
The number of endcaps in the final design. Extracted from tapcell log. |
|
The number of tapcells in the final design. Extracted from tapcell log. |
|
The number of diodes in the final design. Extracted from diode logs or Fastroute log based on the used diode insertion strategy. |
|
The sum of endcaps, tapcells, and diodes in the final design. |
|
The suggested clock frequency to be used with the design. Calculated based on the value of |
|
The suggested clock period to be used with the design. Calculated based on the value of |
|
The area of the core, in μm2. Extracted from the initial floorplan. |
|
Total internal (within cell) power use at the slowest corner, in uW. Extracted from the post-parasitics multi-corner power usage report. |
|
Total switching power use at the slowest corner, in uW. Extracted from the post-parasitics multi-corner power usage report. |
|
Total leakage power use at the slowest corner, in uW. Extracted from the post-parasitics multi-corner power usage report. |
|
Total internal (within cell) power use at the typical corner, in uW. Extracted from the post-parasitics multi-corner power usage report. |
|
Total switching power use at the typical corner, in uW. Extracted from the post-parasitics multi-corner power usage report. |
|
Total leakage power use at the typical corner, in uW. Extracted from the post-parasitics multi-corner power usage report. |
|
Total internal (within cell) power use at the fastest corner, in uW. Extracted from the post-parasitics multi-corner power usage report. |
|
Total switching power use at the fastest corner, in uW. Extracted from the post-parasitics multi-corner power usage report. |
|
Total leakage power use at the fastest corner, in uW. Extracted from the post-parasitics multi-corner power usage report. |
|
Delay of the longest path, in ns, reported by multi-corner post-parasitics STA. |
Default Printed Configuration Variables¶
Variable |
Description |
---|---|
|
The clock period for the design in ns |
|
Strategies for abc logic synthesis and technology mapping |
|
The max load that the output ports can drive. |
|
The core utilization percentage. |
|
The core’s aspect ratio (height / width). |
|
The pitch of the vertical power stripes on the metal layer 4 in the power distribution network |
|
The pitch of the horizontal power stripes on the metal layer 5 in the power distribution network |
|
The desired placement density of cells. It reflects how spread the cells would be on the core area. 1 = closely dense. 0 = widely spread |
|
Reduction in the routing capacity of the edges between the cells in the global routing graph. Values range from 0 to 1. |
|
Specifies the standard cell library used. |
Optional variables¶
These variables are optional that can be specified in the configuration parameters file. Please refere to this file for the full list of configurations.