The QoR Assessment Summary includes two parts:
- A score that predicts whether your design meets timing goals.
- Flow guidance based on the current implementation status.
The assessment score estimates your design's likelihood of meeting performance targets at the current point in the flow. Run the command early in the flow to maximize benefits, as earlier runs save more compile time. Although early results are slightly less accurate, the score typically differs by no more than one point from the final post-route score.
Vivado calculates the score by analyzing design metrics such as:
- AMD UltraFast™ methodology compliance
- Device utilization
- Control sets
- Clocking structure
- Setup and hold slack
- Device-specific factors depending on the implementation stage
For example:
- After
synth_design, the tool evaluates clocking netlist structures. - After
place_design, clock skew contributes more heavily. - After
route_design, routing completion becomes a key factor.
Scores range from 1 to 5. If the score is less than 5, use the
report_qor_suggestions command to improve it.
| Score | Meaning |
|---|---|
| 1 | Design will likely not complete implementation. |
| 2 | Design will complete implementation but will not meet timing. |
| 3 | Design will likely not meet timing. |
| 4 | Design will likely meet timing. |
| 5 | Design will meet timing. |
Flow guidance updates dynamically based on design status. It can include:
- Whether to address methodology issues
- Whether to apply suggestions from
report_qor_suggestions - Whether to use machine learning (ML) strategies or incremental compile
The following figure shows an example of a design with a QoR assessment score of 2.