Frequently Asked Questions


Following the steps below to debug your model:

  1. Check your config.json file:

  • Check if it is valid JSON format:


    import json config = json.load(open('config.json', 'r'))

    This code should run without exception.

  • If you are using custom transforms, make sure you follow the instructions in Bring your own Transforms.

  1. Check your model file:

  1. Upload model to AIAA again:

Once you make sure all the pieces are correct, upload your model again to AIAA.

  1. Increase triton_model_timeout:

AIAA will poll Triton for this amount of time before AIAA claims the model is not imported correctly. If you are using Triton engine (which is the default case), you can try using a larger timeout to ensure the model import success. e.g.: --triton_model_timeout 120.

  1. Check your logs:

If all the above steps do not work, start using flag --debug 1 and check log files in /workspace/logs. You can also go to Nvidia Developer Forums.


Currently, AIAA requires models to have a single input and a single output. Multi-class segmentation can be achieved by having multiple channels in output.

Most of the time, this is caused by the mismatch of data. Make sure your testing data in AIAA have the same characteristics as the data that you used to train your models.

That would include the following:

  1. Resolution/Spacing

  2. Orientation

  3. Contrast/Phase

For example, the pre-trained segmentation models on NGC are using data from Medical Segmentation Decathlon.

We re-scale the image to have a spacing of [1.0, 1.0, 1.0] and make sure the affine matrix of Nifti have all positive values.


Clara Train API provides some nice transforms to tackle the resolution and orientation problems.


If you trained your model with data augmentation like RandomAxisFlip and RandomZoom then it will be insensitive to orientation.

Yes, we do support 2D models. However, this is only supported by directly interacting with the AIAA server API via HTTP post requests. (Please refer to Tutorial: Brain Segmentation PyTorch for an example.)

We are planning to support 2D models in other clients in the future.

If your GPU card is very tight on memory, you can do some of the following points to alleviate this:

  1. Load fewer models in AIAA server

  2. Reduce roi (the size of scanning window) in config_aiaa.json

  3. Try to reduce your network size

If you start the docker using --net=host, make sure AIAA port and Triton ports are not used by other processes.

If you use -p [host port]:[docker port] to run docker, then just make sure the [host port] is not used by other processes.

To start it all clean, remove the workspace folder and create a new one. Then start AIAA server with the new workspace.

You can provide your own data loader to load data in any format you want (png, jpg, NumPy array). Please refer to Bring your own Data Loader.

Notice that AIAA currently does not support batching, it supports inference on one image/volume for each request. So you need to make sure the ShapeFormat in the end of your pre-transforms chain should not have the batch dimension (“N”). If you are writing custom transforms, make sure you take care of ShapeFormat.

When AIAA runs with Triton backend, it will put one model instance on every GPU that is visible inside the docker.

Users can use -e NVIDIA_VISIBLE_DEVICES=[ids of the GPU you want to use] to control what GPUs are visible. For the number of model instances on each GPU, users can modify gpu_instance_count under triton in their model configs.

When a model instance is loaded in GPU, even if it is not serving any inference requests at that moment, it will occupy some amount of GPU memory. As a result, if users want to free that GPU memory, they will have to either stop the AIAA server or unload some models (using DELETE model API).

Yes. Advanced users can modify apache configs for AIAA which are normally located at /opt/nvidia/medical/nvmidl/apps/aas/www/conf/ in the docker.

By default, it runs as www-data user/group for security reasons. Hence the ownership of AIAA workspace will get modified accordingly.

Yes. But you have to make sure you are using different ports for Triton and they do not overlap. In such cases avoid using --net=host and use direct port mapping to make sure AIAA port and Triton ports are not used by other processes.

You use -p [host port]:[docker port] to run docker and make sure [host port] is not used by other processes. For example -p 9000:80 to map a different host port for HTTP access and -p 9001:443 for HTTPS.

Then you can try

  • curl

  • curl --insecure (if you are running AIAA in ssl mode)

Also recommended to use a different port for Triton server while starting AIAA. For example: --triton_port 8500


Apache inside docker always runs at HTTP port 80 and SSL port 443


More discussions can be found in Nvidia Developer Forums

If you are running AIAA as a non-root user, the HTTP port will be 5000 (instead of 80).

To start container as a non-root user (make sure non-root user name + group name is valid inside the container)


docker run -it --rm --gpus=2 -p 5680:5000 \ -u [user name]:[user group] -v /etc/passwd:/etc/passwd -v /etc/group:/etc/group \ -v /home/xyz:/workspace/ \<version here> \ /bin/bash

After that you can run AIAA as a non-root user: --workspace /workspace


Default workspace (/var/nvidia/aiaa) will not work for non-root user as it might not have required permissions. So always specifying your own workspace with possible permissions set for non-root user.


Note the difference between root and non-root use case. Root user (existing method):


docker run -it --rm --gpus=2 -p 5678:80 -p 5679:443 \ -v /home/xyz:/workspace/ \<version here> \ /bin/bash

First we convert the Clara-Train docker image to singularity.


singularity build clara-train-sdk.simg docker://<version here>

We execute that image using the following commands.


singularity exec --nv clara-train-sdk.simg /bin/bash

Then we use the following commands to launch the AIAA server:


export TZ="UTC" --workspace [somewhere that belongs to the user]

The AIAA server will be up and running at

© Copyright 2020, NVIDIA. Last updated on Feb 2, 2023.