Configure NVIDIA Earth-2 FourCastNet NIM at Runtime#
Use this documentation for details about how to configure the NVIDIA Earth-2 FourCastNet NIM at runtime.
GPU Selection#
Passing --gpus all to docker run is acceptable in homogeneous environments with 1 or more of the same GPU.
In some environments, it is beneficial to run the container on specific GPUs.
Expose specific GPUs inside the container by using either:
The
--gpusflag, for example--gpus='"device=1"'.The environment variable
NVIDIA_VISIBLE_DEVICES, for example-e NVIDIA_VISIBLE_DEVICES=1.
The device IDs to use as inputs are the output of nvidia-smi -L.
GPU 0: Tesla H100 (UUID: GPU-b404a1a1-d532-5b5c-20bc-b34e37f3ac46)
See the NVIDIA Container Toolkit documentation for more instructions.
Model Profiles#
The FourCastNet NIM has the following model profiles that can be used:
FourCastNet 3 ERA5 72ch#
NIM_MODEL_PROFILE: 22e778cf9fb13e9a598eff3568293d386a8546fc7c960d8ce963f1c6ac09a0fb
FourCastNet 3 probabilistic model for predicting atmospheric dynamics trained on 72 variables of ERA5. No fine-tuning process used.
Environment Variables#
The FourCastNet NIM allows a few customizations that are referenced on the start up of the container. The following variables can be used to change the NIM behavior:
Variable |
Default |
Description |
|---|---|---|
NGC_API_KEY |
Your NGC API key with read access to the model registry for the model profile you are using. |
|
NIM_MODEL_PROFILE |
“22e7…a0fb” |
The model package to load into NIM on launch. This is downloaded from NGC assuming that you have the correct permissions. |
NIM_HTTP_API_PORT |
8000 |
Publish the NIM service to the specified port inside the container. Make sure to adjust the port passed to the |
NIM_DISABLE_MODEL_DOWNLOAD |
Disable model download on container startup. |
Mounted Volumes#
The following paths inside the container can be mounted to enhance the runtime of the NIM:
Container Path |
Required |
Description |
Example |
|---|---|---|---|
|
No |
This is the directory within which models are downloaded inside the container. This directory must be accessible from inside the container. This can be achieved by adding the option |
|