Organizing Models
Learn how AI Hub models and model zoos are organized. This page covers JSON model file naming conventions and model zoo directory structure. Local model zoos may follow these conventions.
JSON Model File Naming Conventions
Each JSON model file in a model zoo follows a structured naming convention to maintain consistency and clarity:
Field Descriptions
model family
The name of the model family
resolution
Input tensor size (optional)
<integer>x<integer>
density
Model density (optional)
pruned
, dense
precision
Model calculation precision (optional)
quant
, float
agent
DeGirum runtime agent type for inference (optional)
Agent type
or multi
hardware
Hardware for model inference (optional)
Device type
or multi
version
Version of the compiled model
<integer>
Model Family Names
Use the following conventions when naming model families:
Do not use dashes (
-
). Use underscores (_
) instead.Do not use capital letters. All names should be in lowercase.
Include the backbone network as a suffix when applicable. For example:
posenet_mobilenet_v1
Include the network version as a suffix when applicable. For example:
mobilenet_v1
Different model sizes (such as small or large) should be defined as a suffix when applicable. For example:
yolo_v5s
(for a small version)
These conventions ensure models are easily identifiable and consistent across AI Hub and local model zoos.
Model Zoo Directory Structure
Place each model in its own subdirectory with all required files.
Model zoos on the AI Hub follow this structure by default, and local model zoos can use the same approach.
Example: Model Directory Structure
Each subdirectory corresponds to a single model and contains all the necessary files to define, load, and execute that model.
Last updated
Was this helpful?