Introduction

Compared with industry benchmark operators, the computation results of Ascend-proprietary operators on the AI processor may exhibit discrepancies:

  • Model migration: When a source model (GPU-based) is migrated to the Ascend environment for training or online inference, discrepancies may arise between Ascend-proprietary operators and benchmark operators.
  • Model conversion: During conversion, the ATC tool performs optimizations such as operator elimination, fusion, and splitting. These operations may cause divergence between Ascend-proprietary and benchmark operator computation results.
  • Model compatibility: For offline models converted through ATC, factors such as CANN or model version iterations, model optimization, hardware upgrades, or changes in operator fusion settings may lead to accuracy degradation in the optimized model.

To assist developers in resolving operator accuracy issues, the accuracy debugging tool provides a comparison function between Ascend-proprietary and benchmark operator computation results.

For details about ATC, see ATC.

Overall Accuracy Comparison Workflow

The overall accuracy comparison workflow is as follows:

The following flowchart describes the three supported scenarios:

Figure 1 Overall accuracy comparison workflow