Repository Generated After Tuning Cannot Be Matched

Symptom

The AOE tuning tool completes tuning and generates a repository, but the repository cannot be matched.

Solution

Check whether the parameters during tuning are consistent with those during ATC-to-model conversion or AOE re-tuning. The following parameters must be consistent to ensure that the generated repository can be matched.

**Table 1** Parameters that affect the matching of the subgraph repository
Option	Cause Affecting the Matching of the Subgraph Repository	Description
--input_format	Sets the input data format.	Supported by both ATC and AOE. The values must be consistent.
--input_shape	Sets the shape of each input.	Supported by both ATC and AOE. The values must be consistent.
--output_type	Sets the output data type of a network or an output node.	Supported by both ATC and AOE. The values must be consistent.
--insert_op_conf	Inserts new operators, affecting the network structure.	Supported by both ATC and AOE. The values must be consistent.
--out_nodes	Sets different nodes on the network as output nodes.	Supported by both ATC and AOE. The values must be consistent.
--input_fp16_nodes	Sets the name of the input node whose input data type is FP16, affecting the data type of the input node.	Supported by both ATC and AOE. The values must be consistent.
--is_input_adjust_hw_layout	Sets whether the network input data type is FP16 and whether the data format is NC1HWC0, affecting the network input data type and format.	Supported by both ATC and AOE. The values must be consistent.
--is_output_adjust_hw_layout	Sets whether the network output data type is FP16 and whether the data format is NC1HWC0, affecting the network output data type and format.	Supported by both ATC and AOE. The values must be consistent.
--fusion_switch_file	Sets different fusion patterns, affecting the network structure.	Supported by both ATC and AOE. The values must be consistent.
--enable_scope_fusion_passes	Sets different fusion patterns, affecting the network structure.	Supported by both ATC and AOE. The values must be consistent.
--enable_small_channel	Changes the network fusion pattern.	Supported by both ATC and AOE. The values must be consistent.
--precision_mode	Affects the dtype of some network operators.	Supported by both ATC and AOE. The values must be consistent.
--op_precision_mode	Affects the dtype of some network operators.	Supported by both ATC and AOE. The values must be consistent.
--modify_mixlist	Affects the dtype of some network operators.	Supported by both ATC and AOE. The values must be consistent.
--keep_dtype	Affects the dtype of some network operators.	Supported by both ATC and AOE. The values must be consistent.
--op_select_implmode	Affects the dtype of some network operators.	Supported by both ATC and AOE. The values must be consistent.
--optypelist_for_implmode	Affects the dtype of some network operators.	Supported by both ATC and AOE. The values must be consistent.
--dynamic_batch_size	Affects the network shape and needs to be kept consistent.	The dynamic batch is complex. The repository saved for tuning corresponds to the repository of some profiles that have performance benefits. The values must be consistent.
--dynamic_image_size	Affects the network shape and needs to be kept consistent.	The dynamic image size is complex. The repository saved for tuning corresponds to the repository of some profiles that have performance benefits. The values must be consistent.
--dynamic_dims	Affects the network shape and needs to be kept consistent.	The dynamic shape is complex. The repository saved for tuning corresponds to the repository of some profiles that have performance benefits. The values must be consistent.

If the parameter values are inconsistent, you need to change them to be consistent and perform tuning again to generate a repository with the consistent parameters.

Parent topic: Troubleshooting