The Design Runs window displays the state of the current runs.
If the run is running, finished cleanly, or finished with errors, the Design Runs window appears when a run is done.
The Design Runs Window columns show:
- The name of the run
- The target part
- The constraints set associated with a run
- The run strategy
- The status of the last completed step of a run
- The progress of a run
- The start time of a run
- The elapsed time of a run during execution or the final runtime of a completed run
- The timing score of a run: WNS, TNS, WHS, THS, WBSS, and TPWS (see Report Timing Summary for more information on these numbers). This is where you can quickly verify that a run meets timing. If it does not meet timing, you must start the analysis with the Timing Summary Report.
Note: WBSS represents the Worst Bus Skew Slack reported by
- The number of nets that were not successfully routed
- The utilization of the design LUT, FF, block RAMs, DSP, and if applicable, UltraRAMs.
- The total power estimate
- A brief description of the run strategy
- The incremental mode of the design run
If you are using the Vivado® IDE project flow, review the Messages tab for your active synthesis and implementation runs. Messages are grouped by run steps in the flow. All the information saved in the run log files, and the main Vivado session log file, appear in this consolidated and filtered view.
Some messages crossprobe back to a source file that can always be opened by clicking on the file name, or in some cases to a design object related to the message. Depending on which step of the flow you are analyzing, you must open either the synthesized design or the implemented design in order to be able use the object crossprobing from the message.