--op_name_map

Applicable Products

• Ascend 950PR/Ascend 950DT: not supported
• Atlas A3 training products/Atlas A3 inference products: not supported
• Atlas A2 training products/Atlas A2 inference products: not supported
• Atlas 200I/500 A2 inference products: supported
• Atlas inference products: supported
• Atlas training products: supported

Description

Sets the directory (including the name) of the mapping configuration file of a custom operator. The function of a custom operator varies according to the network. You can specify the mapping between the custom operator and the actual custom operator running on the network.

In Caffe networks, some layers share identical type names yet feature different computing functions, such as the DetectionOutput layer. Use operator mapping to specify the detection operator type, for example, FSRDetectionOutput and SSDDetectionOutput. Otherwise, offline model generation fails.

This option applies only to the Caffe framework.

See Also

• This option can be used only when --framework is set to 0. If --framework is set to 1 and the network model is based on the MindSpore framework, this option is invalid but the model conversion still succeeds.

Arguments

Argument: Directory (including the name) of the custom operator mapping configuration file.

Format: The directory (including the file name) can contain letters, digits, underscores (_), hyphens (-), periods (.), and Chinese characters.

Suggestions and Benefits

None

Example

The following is an example of the content of the custom operator mapping configuration file (opname_map.cfg is assumed as the file name):

DetectionOutput:SSDDetectionOutput

Upload the configured opname_map.cfg file to any directory on the server where the ATC tool is located, for example, $HOME/module.

--op_name_map=$HOME/module/opname_map.cfg

Dependencies and Restrictions

None