Check the PPU runtime environment

Asight Systems offers a feature to check the PPU runtime environment. Use the following command:

asys status [<--ppu-env>] [app] [app args]

This command has two check modes: static environment check and runtime environment check.

1. Static environment check

asys status --ppu-env

You can run the static environment check independently, without a target application. It only checks the environment where the asys status command is executed.

Example output:

2. Runtime environment check

asys status --ppu-env <app> <app args>

The runtime environment check requires a target application. The asys status command starts the target application and injects a check library into the target application's process to collect environment information. This lets you diagnose issues caused by the target application modifying PPU environment information during execution, such as model programs launched by a shell script.

Example runtime environment check output:

3. Check items

The PPU environment check tool performs checks in the following eight categories:

1. PPU SDK validity and path check (static, runtime).

2. PPU SDK software stack compatibility check (static, runtime).

3. PPU device validity check (static, runtime).

4. Residual CUDA file check (static, runtime).

5. Docker environment check (static, runtime).

6. Denylist library file check (static, runtime).

7. Validity of PPU SDK libraries loaded by the target application (runtime only).

8. Target application shell log check (runtime only).