Prepare Description
Definition of Prepare
Prepare is the process of converting a floating-point model into a pseudo-quantized model. This process involves several key steps:
-
Computation Graph Capture: Execute the complete forward logic of the model and capture the corresponding computation graph during this process. Subsequently, the computation graph will be pruned based on the positions of
QuantStubandDequantStub, retaining only the intermediate parts that require quantization. -
Function-type Operator Replacement: Some torch function-type operators (e.g.,
torch.reciprocal) need to have fake quantization nodes inserted during quantization. Therefore, these operators must be replaced with their corresponding Module-type implementations (e.g.,horizon_plugin_pytorch.nn.Reciprocal), so that fake quantization nodes are placed inside this Module. The model remains equivalent before and after replacement. This replacement process is performed based on the computation graph, so operations not in the graph will not be replaced. -
Operator Fusion: BPU supports fusing specific computational patterns, where the intermediate results of fused operators are represented with high precision. Therefore, we replace multiple operators to be fused with a single Module to prevent quantizing the intermediate results. The model before and after fusion is also equivalent.
-
Operator Conversion: Floating-point operators are replaced with QAT (Quantized Awareness Training) operators. According to the configured qconfig, QAT operators will add FakeQuantize nodes at the input/output/weights.
To keep converted QAT operators work as expected, please ensure that no further modifications are made to the model after calling prepare. For example, converting an unfused BN to a sync BN after prepare may cause the QAT BN to be modified again. The conversion to sync BN should be done before calling prepare.
- Model Structure Check: The QAT model is checked, and a check result file is generated.
Principle of Function Operator Replacement
Function operator replacement relies on the computation graph. However, multiple calls to the same line of code in the graph are expanded into multiple nodes and replaced with multiple Modules. If the model contains code blocks that are called different numbers of times during training and inference, it will cause scale misalignment and affect model accuracy.
To solve this problem, we introduce the concept of "Scope". During operator replacement, multiple calls to the same func code within a single Scope will be replaced with the same shared Module. Currently, there are two ways to define a Scope: 1. The forward method of a Module type defines one Scope; 2. A code block marked with the horizon_plugin_pytorch.fx.jit_scheme.dynamic_block interface is one Scope. Examples are as follows:
- Multiple calls within one Scope are replaced with different Modules
- Scope defined via Module
- Scope defined via
dynamic_block
Note: To enable the conversion from function to Module, we implement a special Wrapper subclass for torch.Tensor. The wrapping and unwrapping of this Wrapper are implemented by registering hooks on appropriate Modules in the model. Therefore, do not modify any hooks in the model after prepare is completed, to avoid invalidation of the replacement and consequent errors or accuracy issues.
Accuracy Description
The model after prepare differs from the floating-point model in terms of computational logic in the following aspects:
Pseudo-quantization nodes are added to the model. For a very small number of operators (such as reciprocal) whose outputs may have extremely large values, to adapt to quantization, their outputs will be clipped to a reasonable range by default.
The above operations will cause changes in the numerical values of the model.
The usage of the prepare interface is as follows:
PrepareMethod
The prepare method includes JIT_STRIP and EAGER. JIT_STRIP belongs to Graph Mode, while EAGER belongs to PrepareMethod.EAGER. Their comparison is as follows:
Currently, JIT_STRIP is our recommended method. The JIT_STRIP will identify and skip pre-process and post-process based on the positions of QuantStub and DequantStub in the model.
Example
- When dynamic code blocks involve operator replacement or fusion, they must be marked with Tracer.dynamic_block. Otherwise, it will lead to quantization information confusion or forward errors.
- Parts of the model where the call count changes (sub-modules or dynamic blocks), if only executed once during the trace, may get fused with non-dynamic parts, leading to forward errors.
When using the graph-based prepare method, it's recommended that the model only contains deployment logic.
If it’s not feasible to extract clean deployment logic due to readability or maintainability concerns, then the following checks should be performed:
-
Check for missing or unexpected keys when loading the checkpoint. Missing or unexpected quantization parameters may indicate that some deployment logic was not quantized or some non-deployment logic was incorrectly quantized. Missing or unexpected model parameters may indicate a mismatch between the forward logic used during prepare and the one used when the checkpoint was generated.
-
Check whether the FX graph generated by multiple prepare runs is consistent. Inconsistent FX graphs suggest that the forward logic differs across runs, and it should be verified whether this is intended.
Model Check
When example_inputs is provided, prepare will perform a model structure check by default. If the check completes, a model_check_result.txt file can be found in the running directory. If the check fails, you need to modify the model based on the warning prompts or call horizon_plugin_pytorch.utils.check_model.check_qat_model separately to check the model. The check process is the same as check_qat_model in the debug tool, and the analysis of the result file is detailed in the check_qat_model related documentation.
