File Paths
During the installation of the CANN package, related configurations and log information are generated. Table 1 lists the paths for storing these files.
{arch} indicates the CPU architecture, and ${HOME} indicates the directory of the current user.
Name |
Path |
|---|---|
Software package installation log path |
If the installation path is specified, replace the following default installation path as required. Take the Toolkit package as an example:
If the size of the installation log file exceeds 50 MB, the file is automatically dumped to a backup file, for example, ascend_toolkit_install_bak.log, in the current path. |
Path for recording information such as the software package version, CPU architecture, and installation path after the installation |
If the installation path is specified, replace the following default installation path as required. Take the Toolkit package (The structure of the NNRT directory is the same as that of the Toolkit directory)and NNAE as an example.
|
Path for recording the installation paths of software packages |
|
Path for recording installation parameters (such as --install-for-all and --whitelist) specified during software package installation |
If the installation path is specified, replace the following default installation path as required. Take the Toolkit package (The structure of the NNRT directory is the same as that of the Toolkit directory)and NNAE as an example.
|
Default installation path of the custom operator package |
If the installation path is specified, replace the following default installation path as required. Take the Toolkit software package as an example (The structure of the NNAE directory is the same as that of the Toolkit directory):
If the custom operator package fails to be installed due to insufficient permission, modify the permission on the vendors directory through the installation user of the operator package. For details about the custom operator package, see CANN TBE&AI CPU Operator Development Guide. |