Generated banner for Tao Train Dino
Generated logo for Tao Train Dino

Tao Train Dino

NVIDIAOfficialCreated by NVIDIA Corporation

  • Skill
  • Tool integration
  • Software development
  • Apache-2.0
  • Medium risk

From the author

DINO (DETR with Improved DeNoising Anchor Boxes) for 2D object detection. Transformer-based detector with denoising training, multi-scale features, and optional distillation support. Use when training, evaluating, exporting, distilling, quantizing, or running inference for a TAO DINO detector. Trigger phrases include "train DINO", "DETR object detection", "TAO 2D detection", "DINO with distillation".
— the description by NVIDIA Corporation

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The tao-train-dino skill provides an interface for training, evaluating, exporting, distilling, quantizing, and running inference for DINO (DETR with Improved DeNoising Anchor Boxes) object detection models. It supports transformer-based architectures with denoising training and multi-scale features. The skill integrates with TAO Core to handle model lifecycle tasks, including AutoML-enabled training, and requires specific dataset configurations and spec overrides for all actions.

What it does

  • Trains DINO object detection models with support for AutoML and multi-GPU configurations.
  • Evaluates model performance using standard metrics like mAP50 and COCO mAP.
  • Exports trained models to formats compatible with TensorRT deployment.
  • Supports model distillation to improve student model performance.
  • Performs quantization for optimized model inference.
  • Manages dataset requirements and spec overrides for various model actions.

When to use it

  • When you need to train a DINO 2D object detector on custom COCO-format datasets.
  • When you need to evaluate or benchmark a DINO model's detection accuracy.
  • When you are preparing a DINO model for deployment via TensorRT.
  • When you want to apply distillation or quantization to a DINO model.

Advantages

  • Provides a structured workflow for the entire DINO model lifecycle.
  • Includes AutoML capabilities for automated hyperparameter optimization.
  • Supports multi-GPU training for efficient model development.
  • Offers clear paths for model export and deployment to TensorRT.

Usage examples

“Train a DINO model using my custom dataset.”
The agent will prompt for the training and validation dataset URIs and the number of classes to generate the training spec.
“Run DINO AutoML for my object detection task.”
The agent will initiate an AutoML workflow using the provided dataset and class count, or the default profile if no inputs are provided.
“Export my trained DINO model to TensorRT.”
The agent will guide you through the export process using the appropriate spec template and configuration parameters.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/nvidia/tao-train-dino/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip tao-train-dino.zip -d .agents/skills

Documentation by NVIDIA Corporation

DINO

Standalone install? If this session was not initialized by the TAO skill bank plugin, run the tao-setup skill first (host preflight, credentials, cross-skill discovery).

DINO (DETR with Improved DeNoising Anchor Boxes) for 2D object detection. Transformer-based detector with denoising training, multi-scale features, and optional distillation support.

Uses pretrained backbone weights (e.g. ResNet-50 ImageNet). Set model.pretrained_backbone_path for backbone-only or train.pretrained_model_path for full model.

When To Use

Train, evaluate, export, distill, quantize, or run inference for a TAO DINO 2D object detector.

For TAO Deploy TensorRT actions (gen_trt_engine, TensorRT evaluate, and TensorRT inference), read references/tao-deploy-dino.md first. Deploy spec templates live in this skill's references/ folder with the spec_template_deploy_*.yaml prefix.

Reference Map

  • references/dino-data-specs.md — dataset contracts, per-action dataset requirements, per-action spec-override examples (train, evaluate, export, deploy/gen_trt_engine, inference, quantize, distill), data-source arrays, checkpoint inference, and dataset layout.

  • references/dino-actions-errors.md — important parameters, default values, evaluate/export defaults, hardware, and the full error-pattern catalog.

  • references/dino-tuning-multigpu.md — full AutoML/HPO notes (metrics, hyperparameters, extractor) and multi-GPU spec consistency.

  • references/tao-deploy-dino.md — TensorRT deploy workflow.

  • references/detailed-guide.md — map to the detailed model guide.

Dataclass Schemas

Generated TAO Core schemas are packaged in schemas/<action>.schema.json, with schemas/manifest.json listing available actions. Each generated schema also emits references/spec_template_<action>.yaml from the schema top-level default field. AutoML enablement is declared at the model layer in references/skill_info.yaml via automl_enabled. Runnable AutoML still requires schemas/train.schema.json and references/spec_template_train.yaml to exist and parse. Use the packaged train schema for automl_default_parameters, automl_disabled_parameters, defaults, min/max bounds, enums, option weights, math conditions, dependencies, and popular parameters. Do not expect ~/tao-core at runtime; maintainers regenerate schemas/templates before packaging the skill bank.

Train Action Policy

This model is AutoML-enabled at the model layer. Before handling any train-stage request, read references/skill_info.yaml and resolve the run override from either an explicit automl_policy value or the user's workflow request. Use automl_policy: on by default and only expose on / off in new launch prompts. Treat phrases like "turn off AutoML", "disable AutoML", "no HPO", or "plain training" as automl_policy: off for this run only. When automl_policy: on, automl_enabled: true, and both schemas/train.schema.json and references/spec_template_train.yaml are packaged, route the train action through tao-skill-bank:tao-run-automl by default with this model's skill_dir. Preserve workflow/application overrides for datasets, specs, output directories, GPU/platform settings, parent checkpoints, and automl_policy. Use direct model training only when automl_policy: off or the packaged train schema/template is missing; in the missing-schema case, report that AutoML is enabled but not runnable for this model until schemas are generated.

Non-train actions such as evaluate, inference, export, and deploy flows stay in this model skill. The per-run automl_policy override does not change model metadata.

Training Requirements

The agent MUST read this section before generating any training or AutoML script for DINO.

  • Dataset type: object_detection

  • Formats: coco, coco_raw

  • Accepted dataset intents: training, evaluation, testing, calibration

  • AutoML metric contract: for the default evaluation-backed workflow, use test_mAP50 with maximize direction. Use test_mAP only when the user explicitly requests COCO/paper-style mAP.

  • Training monitoring metrics: val_mAP50 (logged as Validation mAP50) for quick operational checks; val_mAP for COCO/paper-style benchmark comparisons.

  • Evaluate action metrics: test_mAP50 for AP50 and test_mAP for COCO mAP. AutoML workflows that score recommendations with the standalone evaluate action must use the corresponding test_* KPI.

Required datasets — MUST resolve both:

DatasetRequiredWhy
Train dataset URIYesTraining data (COCO format)
Validation dataset URIYes — ALWAYSDINO unconditionally builds a val dataloader. Omitting val_data_sources causes FileNotFoundError at startup regardless of the metric or workflow. If the user has no separate eval split, reuse the train URI.

Required inputs before generating any training spec:

  1. Train dataset URI — S3 path to COCO-format training data

  2. Validation dataset URI — S3 path to COCO-format val data (can be same as train)

  3. num_classes — How many object classes? Default 91 (COCO). Must be >= max(category_id) + 1. Too low causes CUDA error: device-side assert triggered.

Resolve these from the user request or the default profile below. Prompt only for values that are still missing after applying the profile rules.

Bankable local default profile for DINO AutoML smoke runs:

Use this profile only when the user asks to run DINO AutoML and does not provide dataset or class-count inputs. This profile is intentionally small and local to this skill bank; it is for smoke/iteration runs, not a production benchmark. Do not search previous runners, logs, session state, shell history, or the home directory to recover these values.

DINO_AUTOML_PROFILE = {
    "train_dataset_uri": "s3://nvcf-storage-handling/data/tao_od_synthetic_subset_train_no_convert",
    "validation_dataset_uri": "s3://nvcf-storage-handling/data/tao_od_synthetic_subset_val_no_convert",
    "object_classes": 4,
    "dataset_num_classes": 5,
    "image_archive": "images.tar.gz",
    "annotation_file": "annotations.json",
    "max_recommendations": 10,
    "train_num_epochs": 10,
    "train_checkpoint_interval": 10,
    "train_validation_interval": 1,
    "train_num_gpus": 1,
}

If the user supplies any dataset URI or class-count value, prefer the user value and ask for any remaining required DINO value. Do not partially mix a user's custom dataset with this profile's class count unless the user confirms it.

Do not prompt for image layout for the standard DINO dataset. The standard TAO DINO dataset artifact is images.tar.gz plus annotations.json. Use images.tar.gz in the remote image_dir spec override. The SDK downloads the archive and rewrites the runtime spec to the extracted folder named after the archive stem (images.tar.gz -> images). Only deviate if the user explicitly provides a different image artifact name.

Core Workflow

DINO supports train, evaluate, export, distill, quantize, and inference. Data-source overrides are mandatory for every action — DINO's config.json has empty data_sources because the runner cannot auto-resolve array-of-objects spec keys. The agent MUST construct data source paths and include them in spec_overrides.

See references/dino-data-specs.md for the per-action dataset requirements table, the standard dataset artifact (images.tar.gz + annotations.json) and runtime folder rewrite rules, and the complete per-action spec_overrides examples for train, evaluate, export, deploy/gen_trt_engine, inference, quantize, and distill — including checkpoint inference via parent_model, the results_dir/train/ checkpoint location, and the distillation FAN-teacher / student rules.

Important Parameters And Defaults

Default values: num_epochs=10, batch_size=4, learning_rate=2e-4, lr_backbone=2e-5, num_classes=91, backbone=resnet_50.

  • dataset.num_classes: Default 91 (COCO). Must be >= max(category_id) + 1. Too low causes CUDA error: device-side assert triggered. Set as <num_classes> + 1 in spec overrides.

  • num_epochs: default 10 (quick iteration); real datasets typically need 30-50+ epochs for good mAP.

See references/dino-actions-errors.md for the full parameter list (backbone options, train.optim.lr/lr_steps, model.num_queries, batch_size), default values, evaluate defaults, export defaults (input 960x544, opset 17, TRT data types, workspace 1024 MB), and hardware requirements.

Multi-GPU And AutoML / HPO

When increasing train.num_gpus, also set train.gpu_ids to the same visible device range, or distributed startup can be inconsistent.

AutoML runs training — all Training Requirements above apply. For no-input local smoke runs, use DINO_AUTOML_PROFILE. For training-log-only scoring, use val_mAP50 (extracted from Validation mAP50) or val_mAP. When each recommendation is scored through the standalone evaluate action, use test_mAP50 or test_mAP with direction="maximize".

See references/dino-tuning-multigpu.md for the full multi-GPU spec-consistency rule (8-GPU example, NCCL timeout note) and the full AutoML/HPO notes (metric selection, metric_extractor, recommended hyperparameters, weight_decay behavior, dense-dataset resume guidance, and parent-model inference mappings).

Error Patterns

Common failures include CUDA OOM (reduce batch_size), missing val_data_sources (FileNotFoundError at startup — always supply val), num_classes too low (CUDA device-side assert), and the parent dino gen_trt_engine / dino convert PyT-CLI restrictions.

See references/dino-actions-errors.md for the complete error-pattern catalog with diagnostics and fixes.

Spec Param / Parent Model Inference

Model-specific inference mappings belong in this MD file. For parent_model/parent_model_folder, pass the upstream train/export/AutoML child job id as the parent job id; list the parent result folder, filter checkpoint artifacts, and select the resolved model.

See references/dino-tuning-multigpu.md for the full inference-mapping table (per action: parent_model, key, output_dir, ptm_if_no_resume_model, resume_model, create_onnx_file) and the TensorRT-mapping note. TensorRT mappings live in the deploy workflow, not the PyT model skill.

Deployment

Files

references/tao-deploy-dino.md

DINO Deploy

DINO deploy covers the TAO Deploy actions for a trained and exported DINO object detector. Use the dino model skill for train, checkpoint evaluation, quantize, distill, and export. Use this deploy workflow after export when the input artifact is an ONNX model and the desired output is a TensorRT engine or TensorRT-backed predictions.

Supported actions: gen_trt_engine, evaluate, inference.

Quick Start

Set the deploy container once at the top of the session — every command below uses it:

TAO_DEPLOY_IMAGE=nvcr.io/nvidia/tao/tao-toolkit:7.3.0-deploy  # versions-key: images.tao_toolkit.deploy
Generate TensorRT Engine
docker run --gpus all --rm --shm-size=16g \
  -v /path/to/specs:/specs \
  -v /path/to/export:/models \
  -v /path/to/results:/results \
  "$TAO_DEPLOY_IMAGE" \
  dino gen_trt_engine -e /specs/dino_deploy_gen_trt_engine.yaml
Evaluate TensorRT Engine
docker run --gpus all --rm --shm-size=16g \
  -v /path/to/specs:/specs \
  -v /path/to/eval/images:/data/images \
  -v /path/to/eval/annotations.json:/data/annotations.json \
  -v /path/to/results:/results \
  "$TAO_DEPLOY_IMAGE" \
  dino evaluate -e /specs/dino_deploy_evaluate.yaml
TensorRT Inference
docker run --gpus all --rm --shm-size=16g \
  -v /path/to/specs:/specs \
  -v /path/to/infer/images:/data/images \
  -v /path/to/label_map.txt:/data/label_map.txt \
  -v /path/to/results:/results \
  "$TAO_DEPLOY_IMAGE" \
  dino inference -e /specs/dino_deploy_inference.yaml

Deploy action metadata is in tao-deploy-dino.skill_info.yaml. Deploy spec templates live in this references folder:

  • spec_template_deploy_gen_trt_engine.yaml

  • spec_template_deploy_evaluate.yaml

  • spec_template_deploy_inference.yaml

Deploy Workflow

  1. Train DINO with the dino skill.

  2. Export the trained checkpoint to ONNX with the dino skill. Keep any ONNX sidecar files in the same directory as the ONNX file.

  3. Build a TensorRT engine with this workflow's gen_trt_engine action.

  4. Run TensorRT evaluate or inference with this workflow. For TensorRT inference, use the engine job as the parent artifact, not the train job.

Direct TAO Launcher spelling is tao deploy dino gen_trt_engine, tao deploy dino evaluate, and tao deploy dino inference.

Required Inputs

ActionRequired artifactSpec key
gen_trt_engineExported DINO ONNX modelgen_trt_engine.onnx_file
gen_trt_engineOutput engine pathgen_trt_engine.trt_engine
gen_trt_engine INT8 onlyCalibration image foldergen_trt_engine.tensorrt.calibration.cal_image_dir
gen_trt_engine INT8 onlyCalibration cache output pathgen_trt_engine.tensorrt.calibration.cal_cache_file
evaluateTensorRT engineevaluate.trt_engine
evaluateCOCO eval image folderdataset.test_data_sources.image_dir
evaluateCOCO eval annotationsdataset.test_data_sources.json_file
inferenceTensorRT engineinference.trt_engine
inferenceImage folder listdataset.infer_data_sources.image_dir
inferenceClass map text filedataset.infer_data_sources.classmap

For direct Docker runs, image inputs must be mounted as folders because TAO Deploy checks local directories. In microservice-style job chains, standard DINO dataset artifacts may be supplied as images.tar.gz; the platform layer downloads and extracts the archive before invoking TAO Deploy.

Spec Overrides

The deploy defaults are not safe to reuse blindly. Carry forward the structural settings from the training/export spec, especially:

{
    "dataset.num_classes": "<object classes> + 1",
    "model.backbone": "<backbone used for train/export>",
    "model.num_queries": "<num_queries used for train/export>",
    "model.num_select": "<num_select used for train/export>",
    "model.num_feature_levels": "<num_feature_levels used for train/export>",
    "model.enc_layers": "<enc_layers used for train/export>",
    "model.dec_layers": "<dec_layers used for train/export>",
    "model.dropout_ratio": "<dropout_ratio used for train/export>",
    "model.dim_feedforward": "<dim_feedforward used for train/export>",
}

Recommended gen_trt_engine starting overrides:

{
    "gen_trt_engine.onnx_file": "/models/model.onnx",
    "gen_trt_engine.trt_engine": "/results/dino.engine",
    "gen_trt_engine.tensorrt.data_type": "FP16",
    "gen_trt_engine.tensorrt.min_batch_size": 1,
    "gen_trt_engine.tensorrt.opt_batch_size": 1,
    "gen_trt_engine.tensorrt.max_batch_size": 8,
    "gen_trt_engine.batch_size": -1,
}

Use FP16 by default. The upstream deploy default is INT8, but INT8 requires a real extracted calibration image directory, a calibration cache path, positive cal_batch_size, positive cal_batches, and at least cal_batch_size * cal_batches calibration images.

Recommended evaluate overrides:

{
    "evaluate.trt_engine": "/results/dino.engine",
    "dataset.test_data_sources.image_dir": "/data/eval/images",
    "dataset.test_data_sources.json_file": "/data/eval/annotations.json",
    "dataset.batch_size": 1,
    "dataset.eval_class_ids": [1],
    "evaluate.conf_threshold": 0.0,
    "model.num_select": "max(<trained_num_select>, 100)",
}

Set dataset.eval_class_ids to the COCO category ids you want scored. The template default [1] is only a placeholder.

DINO TensorRT evaluation writes num_detections=100 into the COCO metric input. For reduced smoke configs, keep model.num_select >= 100 even if train/export used fewer selected boxes, provided model.num_select <= model.num_queries * dataset.num_classes. Otherwise evaluation can produce predictions and then fail while loading COCO results.

Recommended inference overrides:

{
    "inference.trt_engine": "/results/dino.engine",
    "dataset.infer_data_sources.image_dir": ["/data/infer/images"],
    "dataset.infer_data_sources.classmap": "/data/infer/label_map.txt",
    "dataset.batch_size": 1,
    "inference.conf_threshold": 0.5,
}

label_map.txt must contain one class name per line. Class ids are assigned starting at 1 in file order.

Job Chain Mapping

When generating a chained job runner, infer parent artifacts as follows:

ActionSpec fieldParent
gen_trt_enginegen_trt_engine.onnx_fileexport job ONNX
gen_trt_enginegen_trt_engine.trt_enginenew engine output path
gen_trt_enginegen_trt_engine.tensorrt.calibration.cal_cache_filenew calibration cache output path
evaluateevaluate.trt_engineengine job output
inferenceinference.trt_engineengine job output

For regular DINO inference from a trained checkpoint, use the dino skill. This deploy workflow's inference action expects inference.trt_engine.

Outputs

ActionOutput
gen_trt_engineTensorRT engine at gen_trt_engine.trt_engine
evaluateCOCO metrics in <results_dir>/results.json
inferenceAnnotated images in <results_dir>/images_annotated and labels in <results_dir>/labels

Important Parameters

  • gen_trt_engine.tensorrt.data_type: FP32, FP16, or INT8. Prefer FP16 unless INT8 calibration is explicitly requested.

  • gen_trt_engine.tensorrt.workspace_size: MB of TensorRT workspace. Very large ViT backbones need a larger workspace; DINO deploy raises the workspace for vit_large_dinov2 when needed.

  • gen_trt_engine.tensorrt.min_batch_size / opt_batch_size / max_batch_size: Dynamic profile bounds. Runtime dataset.batch_size for evaluate/inference must fit within the engine profile.

  • dataset.num_classes: Must match train/export and should be max(category_id) + 1 for COCO-style ids.

  • model.num_select: Top-K boxes selected during post-processing. Keep it less than model.num_queries * dataset.num_classes.

  • dataset.augmentation.input_mean / input_std: Keep these aligned with training/export preprocessing.

Known Pitfalls

Engine build uses the wrong shape or class count: The deploy default spec is not the training default. Copy structural values from the export spec before building the engine.

INT8 calibration fails with a missing directory: TAO Deploy expects cal_image_dir entries to be local directories at runtime. Mount or extract the calibration images before invoking Docker.

Number of calibration images ... should be larger: Reduce cal_batch_size or cal_batches, or provide more calibration images.

TensorRT inference cannot find the engine: Chain inference from the gen_trt_engine output. The train/export job does not produce inference.trt_engine.

No detections are drawn: Check inference.conf_threshold, class-map order, and dataset.num_classes. For quick inspection, lower the threshold.

TensorRT evaluate fails with IndexError: index ... is out of bounds: The deploy evaluator expects 100 detections per image. Set model.num_select to at least 100 in the deploy evaluate spec, and make sure it does not exceed model.num_queries * dataset.num_classes.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Declares allowed tools, Needs Python

The author says: Requires docker + nvidia-container-toolkit.

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
NVIDIA Corporation
Publisher
NVIDIA (Official)
Source
NVIDIA/skills · skills/tao-train-dino · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by NVIDIA Corporation or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download tao-train-dino.zip