Sample Usage Guide
1. Function Description
This sample demonstrates graph construction using MatMul operator normal attributes, aimed at helping graph developers quickly understand normal attribute definition and usage.
2. Directory Structure
python/
├── src/
| └── make_matmul_graph.py // sample file
├── CMakeLists.txt // Build script
├── README.md // README file
├── run_sample.sh // Execution script
3. Usage Instructions
3.1. Prepare CANN Package
- Install
toolkitandopspackages correctly following Environment Preparation - Set environment variables (assuming package is installed at /usr/local/Ascend/)
source /usr/local/Ascend/cann/set_env.sh
3.2. Build and Execute
- Note: Compared with C/C++ graph construction, Python graph construction requires additional LD_LIBRARY_PATH and PYTHONPATH settings (refer to configuration in sample)
bash run_sample.sh -t sample_and_run_python
This command will:
- Automatically generate ES interfaces
- Compile sample program
- Generate dump graph and run the graph
After successful execution, you will see:
[Success] sample execution successful, pbtxt dump generated in current directory. The file starts with ge_onnx_ and can be opened in netron for display
Output File Description
After successful execution, the following files will be generated in current directory:
ge_onnx_*.pbtxt- protobuf text format of graph structure, can be viewed with netron
3.3. Log Printing
If you need log printing to assist debugging during executable program execution, you can set the following environment variables before bash run_sample.sh -t sample_and_run_python to print logs to screen:
export ASCEND_SLOG_PRINT_TO_STDOUT=1 # Print logs to screen
export ASCEND_GLOBAL_LOG_LEVEL=0 # Log level set to debug level
3.4. DUMP Graph During Graph Compilation Process
If you need to DUMP graph to assist debugging graph compilation process during executable program execution, you can set the following environment variables before bash run_sample.sh -t sample_and_run_python to DUMP graph to execution path:
export DUMP_GE_GRAPH=2
4. Core Concepts Introduction
4.1. Graph Construction Steps
- Create graph builder (provides context, workspace and construction-related methods needed for graph construction)
- Add starting nodes (starting nodes refer to nodes without input dependencies, usually including graph inputs (like Data nodes) and weight constants (like Const nodes))
- Add intermediate nodes (intermediate nodes are computation nodes with input dependencies, usually generated by user graph construction logic, and connected using existing nodes as inputs)
- Set graph output (explicitly specify graph output nodes as computation result endpoints)
4.2. Normal Attributes
Concept Explanation: Normal attributes are operator configuration parameters used to control operator behavior; attribute values are determined during graph construction and do not change at runtime.
Graph Construction API Features:
- Attribute values must be determined during graph construction, cannot be runtime variables
- If using default values, corresponding parameters can be omitted (use default values) or explicitly passed
- ES API will perform type checking based on attribute type, ensuring passed value types are correct
For example, MatMul operator prototype is shown below, ES graph construction generated API is MatMul(), supporting use in Python
REG_OP(MatMul)
.INPUT(x1, TensorType({DT_FLOAT, DT_FLOAT16, DT_INT32, DT_BF16, DT_HIFLOAT8}))
.INPUT(x2, TensorType({DT_FLOAT, DT_FLOAT16, DT_INT32, DT_BF16, DT_HIFLOAT8}))
.OPTIONAL_INPUT(bias, TensorType({DT_FLOAT, DT_FLOAT16, DT_INT32, DT_BF16}))
.OUTPUT(y, TensorType({DT_FLOAT, DT_FLOAT16, DT_INT32, DT_BF16, DT_HIFLOAT8}))
.ATTR(transpose_x1, Bool, false)
.ATTR(transpose_x2, Bool, false)
.OP_END_FACTORY_REG(MatMul)
Its corresponding function prototype is:
- Function name: MatMul
- Parameters: 5 in total, in order: x1, x2, bias, transpose_x1, transpose_x2
- Return value: output y
Python API:
Matmul(x1: Union[TensorHolder, TensorLike], x2: Union[TensorHolder, TensorLike], bias: Optional[Union[TensorHolder, TensorLike]] = None, *, transpose_x1: bool = False, transpose_x2: bool = False) -> TensorHolder:
Note:
- Use TensorLike type to express input, to support case where actual parameter can directly pass numeric values