Operator Project Building

mkdir build_out

export ASCEND_TENSOR_COMPLIER_INCLUDE=/home/HwHiAiUser/Ascend/ascend-toolkit/latest/atc/include
export SYSTEM_INFO=centos_x86_64

• ASCEND_TENSOR_COMPLIER_INCLUDE specifies the path of the ATC header files. Set it to the actual one.
• SYSTEM_INFO specifies the form name field of the generated OPP runfile after build. Set it as needed.

  Assume that the operating system is CentOS and the architecture is AArch64, set this parameter to centos_aarch64. Then, the generated OPP runfile is named custom_opp_centos_aarch64.run.

  If the SYSTEM_INFO environment variable is not set, the form name is automatically obtained based on the OS and architecture configuration.

cd build_out

cmake .. -DCMAKE_CXX_COMPILER=g++

make

After successful build, an OPP runfile custom_opp_<target os>_<target architecture>.run is generated in the build_out directory.

The generated OPP contains all operators in the directory of the current custom operator project.

The custom.proto file is as follows:

syntax = "proto2";
package domi.caffe;
message NetParameter {
  optional string name = 1; 
  // LayerParameter definition. Retain the default definition.
  repeated LayerParameter layer = 100;  // ID 100 so layers are printed last.

}
message LayerParameter {
  optional string name = 1;  // Definition for model parsing. Retain the default definition.
  optional string type = 2;  // Definition for model parsing. Retain the default definition.

 // Add the definition of the custom operator layer to LayerParameter. The ID must be unique in the built-in caffe.proto file and must be less than 5000.
 // The built-in caffe.proto file is stored in atc/include/proto/caffe.proto in the ATC installation path.
  optional CustomTestParameter custom_test_param = 1000;  

}

// Add the definition of the custom layer.
message CustomTestParameter {
  optional bool adj_x1 = 1 [default = false];
  optional bool adj_x2 = 2 [default = false];
}

1. You are advised to keep the parameter type (in bold and italic) unique and not the same as that defined in the built-in caffe.proto file in the atc/include/proto directory.
2. The custom.proto file in the sample code contains the definition of the custom Caffe operator. If there are other custom operators, add their definitions to this file.

Configure environment variables and build settings in the op/caffe/build.sh script in the Caffe custom project.

• ASCEND_TENSOR_COMPLIER_INCLUDE specifies the path of the ATC header files.
  • If it is not set, the default path /usr/local/Ascend/atc/include is used.
  • If the actual ATC path is not the default path, uncomment this environment variable and change it to the actual path of the ATC header files, for example:

    export ASCEND_TENSOR_COMPLIER_INCLUDE=/home/HwHiAiUser/Ascend/ascend-toolkit/latest/atc/include

• SYSTEM_INFO specifies the form name field of the generated OPP runfile after build. Set it as needed.

  Assume that the operating system is CentOS and the architecture is AArch64, set this parameter to centos_aarch64. Then, the generated OPP runfile is named custom_opp_centos_aarch64.run.

  If the SYSTEM_INFO environment variable is not set, the form name is automatically obtained based on the OS and architecture configuration.

After modifying the path, run the :wq command to save the modifications and exit.

Run the following command in the op/caffe directory of the custom Caffe operator project:

./build.sh

After successful build, an OPP runfile custom_opp_<target os>_<target architecture>.run is generated in the build_out directory.

If you need to rebuild the project, run the ./build.sh clean command to clear the build outputs.

The custom.proto file is as follows:

syntax = "proto2";
package domi.caffe;
message NetParameter {
  optional string name = 1; 
  // LayerParameter definition. Retain the default definition.
  repeated LayerParameter layer = 100;  // ID 100 so layers are printed last.

}
message LayerParameter {
  optional string name = 1;  // Definition for model parsing. Retain the default definition.
  optional string type = 2;  // Definition for model parsing. Retain the default definition.

 // Add the definition of the custom operator layer to LayerParameter. The ID must be unique in the built-in caffe.proto file and must be less than 5000.
 // The built-in caffe.proto file is stored in atc/include/proto/caffe.proto in the ATC installation path.
  optional CustomTestParameter custom_test_param = 1000;  
}

// Add the definition of the custom layer.
message CustomTestParameter {
    optional bool adj_x1 = 1 [default = false];
    optional bool adj_x2 = 2 [default = false];
}

1. You are advised to keep the parameter type (in bold and italic) unique and not the same as that defined in the built-in caffe.proto file in the atc/include/proto directory.
2. The custom.proto file in the sample code contains the definition of the custom Caffe operator. If there are other custom operators, add their definitions to this file.

Run the following command in the op/all directory of the custom operator project to build the custom operator project:

./build.sh

After successful build, an OPP runfile custom_opp_<target os>_<target architecture>.run is generated in the build_out directory.

If you need to rebuild the project, run the ./build.sh clean command to clear the build outputs.