--op_name_map

Applicability

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.

For example, the Caffe network has layers of the same type but different computing functions, such as the DetectionOutput layer. You need to use operator mapping to specify the detection operator type, such as FSRDetectionOutput and SSDDetectionOutput. Otherwise, the generated offline model will fail to be executed.

This parameter applies only to the Caffe framework.

See Also

This option is supported 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 is successful.

Argument

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 ATC server, for example, $HOME/module.

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

Dependencies and Restrictions

None