Skip to main content

Offline Installation

When to use offline installation

Use offline installation when the target host cannot download packages from SiMa.ai services. This can occur when your organization:

  • Blocks large downloads.
  • Restricts access to package registries.
  • Requires approval before you can use downloaded packages.
  • Keeps development hosts separate from computers with internet access.

Download the package on a computer with internet access. Then transfer the package to the target host for installation.

For runtime packages, see PCIe host offline installation or Neat Library offline installation.

Select a package​

PackageUseAvailability
Palette SDKSet up the SDK development environment.SDK 2.1.3.0 or later
Model CompilerInstall Model Compiler in the SDK or on a standalone host.Model Compiler 2.1.3 or later

Before you start​

  • Install sima-cli on the computer with internet access. See Install the SDK.
  • Select a package version that is compatible with your system. See Compatibility.
  • Identify the operating system and processor architecture of the target host.
  • Prepare a USB drive or an internal file share for the transfer.

The download computer and the target host can have different processor architectures. Select the package for the target host. Keep all package files together, including scripts, metadata, checksums, and dependencies.

Install the Palette SDK​

1. Download the package​

Run one command on the computer with internet access. These examples use SDK 3.0.0.1.

For an amd64 target host:

host$sima-cli neat install sdk@v3.0.0.1 -t offline-amd64

For an arm64 target host:

host$sima-cli neat install sdk@v3.0.0.1 -t offline-arm64

2. Install the package​

Model Compiler installation is optional. If you do not need to compile models, skip the Model Compiler download and follow the SDK installation steps below. When the SDK installer asks whether to install Model Compiler, choose to skip it.

To install Model Compiler with the SDK, download the Model Compiler offline package. Put the Model Compiler offline package file in the same directory as the SDK offline package. The SDK installer finds the file automatically. When prompted, select installation from the local package.

  1. Copy the complete downloaded directory to the target host.
  2. Open a terminal in that directory.
  3. Run the installer:
host$bash ./install_offline_sdk.sh

Install Model Compiler​

When to use this procedure

Use this procedure to install Model Compiler separately in an existing SDK or directly on a host. If you installed both the SDK and Model Compiler in the previous step, skip this section.

1. Download the package​

Check the Model Compiler compatibility requirements. Run one command on the computer with internet access. These examples use Model Compiler 3.0.0.1.

For an amd64 target host:

host$sima-cli neat install model-compiler/amd64@v3.0.0.1 -t offline

For an arm64 target host:

host$sima-cli neat install model-compiler/arm64@v3.0.0.1 -t offline

2. Install the package​

Choose one installation location.

In the Palette SDK:

  1. Copy the complete downloaded directory to the host workspace mapped to /workspace in the SDK container.
  2. Open the SDK shell.
  3. Go to the package directory. For an amd64 package, use:
sdk$cd /workspace/model-compiler-offline-amd64

For an arm64 package, use /workspace/model-compiler-offline-arm64.

  1. Run the installer:
sdk$bash ./install_modelsdk_wheels.sh

On a standalone host:

  1. Copy the complete downloaded directory to the target host.
  2. Open a terminal in that directory.
  3. Run the installer:
host$bash ./install_modelsdk_wheels.sh

3. Activate Model Compiler​

  1. Restart the SDK shell or the host shell that you used for installation.
  2. Activate Model Compiler:
sdk or host$activate-model-compiler

To leave the Model Compiler environment, run:

sdk or host$deactivate-model-compiler

Store packages internally​

You can store approved packages on an internal file server. Keep each downloaded directory complete and separate from other package versions. Transfer the complete directory to the target host before you run its installer.