Setting Environment Variables

Before applying AOE tuning, run the export command to configure environment variables on the current terminal. Configurations in this mode become invalid after the shell terminal is closed.

Required environment variables
1. Run the following command in the development environment as the running user to configure the environment variables required by the AOE tool. Replace ${install_path} with the actual installation path of the CANN software and ${arch} with the actual architecture of the operating system.
```
export LD_LIBRARY_PATH=${install_path}/cann/share/info/ncs/lib64/:${install_path}/cann/${arch}-linux/devlib/:$LD_LIBRARY_PATH
```
  You can also write the preceding commands to the ~/.bashrc file and run the source ~/.bashrc command to make them valid immediately.
2. Basic environment variables of the CANN software
  The CANN portfolio provides a process-level environment variable setting script to automatically set environment variables. The following commands are used as examples, in which the default installation paths are under the root or non-root user. Replace them with actual installation paths.
```
# Configure environment variables after installing the Toolkit package as the root user.
source /usr/local/Ascend/cann/set_env.sh 
# Configure environment variables after installing the Toolkit package as a non-root user.
source ${HOME}/Ascend/cann/set_env.sh 
```
3. AOE depends on Python. Take Python 3.7.5 as an example. Run the following commands in the development environment as the running user to set environment variables:
```
# Set the Python 3.7.5 library path.
export LD_LIBRARY_PATH=/usr/local/python3.7.5/lib:$LD_LIBRARY_PATH
# If multiple Python 3 versions exist in the user environment, use Python 3.7.5.
export PATH=/usr/local/python3.7.5/bin:$PATH
```
  Replace the Python 3.7.5 installation path based on the actual requirements. You can also write the preceding commands to the ~/.bashrc file and run the source ~/.bashrc command to make the modification take effect immediately.
Optional environment variables: AOE tuning environment variables in the development environment. The following is an example:
```
export TUNE_BANK_PATH=/home/HwHiAiUser/custom_tune_bank
export TE_PARALLEL_COMPILER=8
export REPEAT_TUNE=False
```

**Table 1** Environment variables
Environment Variable	Description
TUNE_BANK_PATH	Path of the custom repository generated after tuning. The path must be an absolute path or a relative path to the path of the AOE tuning engine. The path must exist and the user must have the read, write, and execute permissions on the path. If the path specified by TUNE_BANK_PATH does not exist or the user does not have the required permissions on the path, the tuning process will report an error and exit. The priority of the paths for storing the custom repository is: TUNE_BANK_PATH > ASCEND_CACHE_PATH > default path. For details about TUNE_BANK_PATH and ASCEND_CACHE_PATH, see Environment Variables. Custom subgraph repository If this environment variable is not configured, run the env command to check whether ASCEND_CACHE_PATH exists. If it exists, the custom repository is stored in ${ASCEND_CACHE_PATH}/aoe_data. If it does not exist, the custom repository is stored in ${HOME}/Ascend/latest/data/aoe/custom/graph/${soc_version} by default. If this environment variable is configured, the custom repository is stored in the path specified by this environment variable. Custom operator repository If this environment variable is not configured, run the env command to check whether ASCEND_CACHE_PATH exists. If it exists, the custom repository is stored in ${ASCEND_CACHE_PATH}/aoe_data/${soc_version}. If it does not exist, the custom repository is stored in ${HOME}/Ascend/latest/data/aoe/custom/op/${soc_version} by default. If this environment variable is configured, the optimal policy after tuning is stored in *${soc_version}* in the configured path. NOTE: If multiple users share the repository, the users must set TUNE_BANK_PATH to the same path and have the read and write permissions on the path. If the repository path is customized before tuning, you also need to configure this environment variable if you want to use the custom repository during model conversion.
TE_PARALLEL_COMPILER	Environment variable required for operator build. Parallel build is especially useful when a deep network is to build. The value of TE_PARALLEL_COMPILER indicates the number of operator build processes, which must be an integer. If the value is greater than 1, parallel build is enabled. In a scenario where AOE tuning is enabled, the maximum value of the environment variable is calculated as follows: Maximum value = Number of CPU cores x 80%/Number of AI processors. The value ranges from 1 to 32. The default value is 8. This environment variable can accelerate operator build. Therefore, it can accelerate the tuning of processes related to operator build.
REPEAT_TUNE	Whether to initiate tuning again. This environment variable takes effect only when subgraph tuning or operator tuning is enabled. If it is set to False and a network tuning case (a tiling policy for a specific shape) is available in the repository (built-in or custom), the tuning process of the case is skipped. When the logic of some operators is changed, for example, the ND input support is added to the GEMM operator, you need to set this environment variable to True and initiate tuning again. The value can be True or False. The default value is False.

You can write the commands for configuring environment variables into the custom script for future use.

Parent topic: AOE Tuning