Generated banner for Tao Train Metric Learning Recognition
Generated logo for Tao Train Metric Learning Recognition

Tao Train Metric Learning Recognition

NVIDIAOfficialCreated by NVIDIA Corporation

  • Skill
  • Tool integration
  • Data and AI
  • Apache-2.0
  • Medium risk

From the author

Metric-learning recognition (ml-recog) for fine-grained visual recognition. Learns embeddings for retrieval-based matching (e.g., retail product recognition) using triplet / contrastive losses. Use when training, evaluating, exporting, or running inference for a TAO metric-learning recognition model. Trigger phrases include "train metric learning", "ml-recog", "retrieval embeddings", "triplet loss recognition", "fine-grained matching".
— the description by NVIDIA Corporation

AutoGineer summary

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

This skill provides a comprehensive workflow for training, evaluating, and deploying metric-learning recognition models. It is designed for fine-grained visual recognition tasks, such as retail product identification, by learning embeddings that facilitate retrieval-based matching. The workflow supports AutoML-enabled training, model evaluation using Precision at Rank 1 metrics, and export for deployment via TensorRT.

What it does

  • Trains metric-learning recognition models using triplet or contrastive losses.
  • Supports AutoML-driven hyperparameter optimization for model training.
  • Evaluates model performance using retrieval-based metrics like Precision at Rank 1.
  • Exports trained models to ONNX format for downstream deployment.
  • Provides integration with TAO Deploy for TensorRT engine generation and inference.
  • Manages dataset requirements for reference and query image sets.

When to use it

  • When building a system for fine-grained visual retrieval or product recognition.
  • When you need to train a model that learns robust embeddings for similarity matching.
  • When you want to leverage AutoML to optimize training parameters for recognition tasks.
  • When deploying models to production environments requiring TensorRT acceleration.

Advantages

  • Optimized for retrieval-based matching tasks.
  • Automated hyperparameter tuning simplifies the training process.
  • Supports standard industry backbones like ResNet and FAN.
  • Seamless transition from training to TensorRT-optimized deployment.

Usage examples

“Train a metric learning recognition model using the default ResNet-50 backbone.”
The agent initiates a training job using the specified dataset paths and default hyperparameters, maximizing Precision at Rank 1.
“Evaluate my trained model on the test dataset.”
The agent runs an evaluation job comparing the model's embeddings against the provided reference and query sets, outputting the final Precision at Rank 1 score.

Install

  1. Download the skill as a ZIP:

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

    mkdir -p .agents/skills && unzip tao-train-metric-learning-recognition.zip -d .agents/skills

Documentation by NVIDIA Corporation

ML Recog

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).

Metric learning recognition for fine-grained visual recognition. Learns embeddings for retrieval-based matching (e.g., retail product recognition). Uses triplet/contrastive losses.

Set model.pretrained_model_path for pretrained backbone.

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

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 for an action requires schemas/<action>.schema.json and references/spec_template_<action>.yaml to exist and parse. Use the packaged selected-action 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

  • Dataset type: ml_recog

  • Formats: default

  • Monitoring metric: val Precision at Rank 1

  • AutoML metric contract: Use val Precision at Rank 1 emitted during training and maximize it. Use test Precision at Rank 1 only for standalone selected-checkpoint validation.

  • Standalone evaluation metric: test Precision at Rank 1. Use the training val Precision at Rank 1 KPI for AutoML recommendation ranking and the test KPI only to verify the selected checkpoint on the evaluation reference/query split.

Per-Action Dataset Requirements
ActionSpec KeySourceFilesList?
evaluatedataset.val_datasettrain_datasetsreference: metric_learning_recognition/retail-product-checkout-dataset_classification_demo/unknown_classes/reference.tar.gz, query: metric_learning_recognition/retail-product-checkout-dataset_classification_demo/unknown_classes/test.tar.gzNo
inferencedataset.val_datasettrain_datasetsreference: metric_learning_recognition/retail-product-checkout-dataset_classification_demo/unknown_classes/reference.tar.gz, query:No
inferenceinference.input_pathtrain_datasetsmetric_learning_recognition/retail-product-checkout-dataset_classification_demo/unknown_classes/test.tar.gzNo
traindataset.train_datasettrain_datasetsmetric_learning_recognition/retail-product-checkout-dataset_classification_demo/known_classes/train.tar.gzNo
traindataset.val_datasettrain_datasetsreference: metric_learning_recognition/retail-product-checkout-dataset_classification_demo/known_classes/reference.tar.gz, query: metric_learning_recognition/retail-product-checkout-dataset_classification_demo/known_classes/val.tar.gzNo
Typical Spec Overrides

Data source overrides are mandatory for every action — the agent MUST construct data source paths from the Per-Action Dataset Requirements table above and include them in spec_overrides.

S3_TRAIN = "s3://bucket/data/train"

train (mandatory data sources):

{
    "train.num_epochs": 30,
    "train.checkpoint_interval": 10,
    "train.validation_interval": 10,
    "train.num_gpus": 1,
    "dataset.train_dataset": f"{S3_TRAIN}/metric_learning_recognition/retail-product-checkout-dataset_classification_demo/known_classes/train.tar.gz",
    "dataset.val_dataset": {"reference": f"{S3_TRAIN}/metric_learning_recognition/retail-product-checkout-dataset_classification_demo/known_classes/reference.tar.gz", "query": f"{S3_TRAIN}/metric_learning_recognition/retail-product-checkout-dataset_classification_demo/known_classes/val.tar.gz"},
}

evaluate (mandatory data sources):

{
    "evaluate.checkpoint": "<selected train/AutoML checkpoint>",
    "dataset.val_dataset": {"reference": f"{S3_TRAIN}/metric_learning_recognition/retail-product-checkout-dataset_classification_demo/unknown_classes/reference.tar.gz", "query": f"{S3_TRAIN}/metric_learning_recognition/retail-product-checkout-dataset_classification_demo/unknown_classes/test.tar.gz"},
}

inference (mandatory data sources):

{
    "inference.checkpoint": "<selected train/AutoML checkpoint>",
    "dataset.val_dataset": {"reference": f"{S3_TRAIN}/metric_learning_recognition/retail-product-checkout-dataset_classification_demo/unknown_classes/reference.tar.gz"},
    "inference.input_path": f"{S3_TRAIN}/metric_learning_recognition/retail-product-checkout-dataset_classification_demo/unknown_classes/test.tar.gz",
}

Eval Dataset

Required. Evaluation requires reference and query datasets for retrieval metrics.

Important Parameters

  • model.backbone: Default resnet_50. Options: resnet_50, resnet_101, fan_small, fan_base, fan_large, fan_tiny, nvdinov2_vit_large_legacy.

  • model.feat_dim: Embedding dimension. Default 256. Output feature vector size for similarity matching.

  • train.batch_size: Per-GPU batch size. Default 4. val_batch_size also 4. For training and AutoML search, train.batch_size must be divisible by dataset.num_instance.

  • dataset.num_instance: Instances per identity in a batch (P/K sampling). Default 4. Controls how many images of the same class appear together. If using a custom AutoML range for train.batch_size, use explicit options that are multiples of this value.

  • train.optim.trunk.base_lr: Learning rate for the trunk (backbone). Default 3.5e-4 (Adam).

  • train.optim.embedder.base_lr: Learning rate for the embedding head. Default 3.5e-4.

  • train.optim.triplet_loss_margin: Margin for triplet loss. Default 0.3. smooth_loss=True by default.

  • train.optim.miner_function_margin: Hard mining margin. Default 0.1. Controls pair mining difficulty.

  • train.optim.steps: LR decay steps. Default [40, 70] with gamma=0.1.

  • dataset.train_dataset: Path to training images organized in class folders.

  • dataset.val_dataset: Dict with 'reference' and 'query' keys pointing to ImageNet-format directories for retrieval evaluation.

Multi-GPU / Multi-Node

Launch method: Lightning-managed (single python process, Lightning spawns workers).

Spec KeyDescriptionDefault
train.num_gpusNumber of GPUs1
train.gpu_idsGPU device indices[0]
  • Strategy: auto (Lightning picks best strategy automatically)

  • No explicit num_nodes or distributed_strategy config — single-node oriented

Hardware

Minimum 1 GPU(s), recommended 2 GPU(s). 16GB+ VRAM per GPU. Metric learning benefits from larger batch sizes for better triplet sampling but is otherwise moderate on memory.

Error Patterns

Reference/query mismatch: Ensure reference and query datasets share compatible class namespaces for evaluation.

PyTorch 2.6 checkpoint load failure on checkpoint actions: Current TAO ML-Recog checkpoints may contain OmegaConf objects. For checkpoints produced by the same trusted TAO train/AutoML workflow, set TORCH_FORCE_NO_WEIGHTS_ONLY_LOAD=1 in downstream evaluate, inference, export, or resume/retrain job env vars so Lightning can load the full checkpoint. Do not use this env var for untrusted checkpoints.

Spec Param / Parent Model Inference

Model-specific inference mappings belong in this MD file, not in config.json. Generated runners should read this section and apply the mappings with SDK helpers before create_job(). This mirrors the old microservices infer_params.py flow.

Inference mappings from TAO Core ml_recog.config.json:

ActionSpec FieldInference FunctionMeaning
evaluateevaluate.checkpointparent_modelmodel file inferred from the parent job results folder
evaluateresults_diroutput_dircurrent job results directory
exportexport.checkpointparent_modelmodel file inferred from the parent job results folder
exportexport.onnx_filecreate_onnx_fileoutput ONNX path
exportresults_diroutput_dircurrent job results directory
inferenceinference.checkpointparent_modelmodel file inferred from the parent job results folder
inferenceresults_diroutput_dircurrent job results directory
trainmodel.pretrained_model_pathptm_if_no_resume_modelPTM when no resume checkpoint exists
trainresults_diroutput_dircurrent job results directory
traintrain.resume_training_checkpoint_pathresume_modelmodel file inferred from the current job results folder

For parent_model or parent_model_folder, pass the upstream train/export/AutoML child job id as parent_job_id. The SDK lists the parent result folder, filters checkpoint artifacts, and returns the selected model file or folder. Do not add these mappings back to config.json and do not patch generated runner scripts to guess checkpoint paths.

Deployment

Files

references/tao-deploy-metric-learning-recognition.md

MLRecog Deploy

MLRecog deploy covers the TAO Deploy actions for an exported metric-learning recognition model. Use the ml-recog model skill for training, checkpoint evaluation, quantization, distillation, pruning, export, or non-TensorRT inference where those actions exist. 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" \
  ml_recog gen_trt_engine -e /specs/ml-recog_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:/data \
  -v /path/to/results:/results \
  "$TAO_DEPLOY_IMAGE" \
  ml_recog evaluate -e /specs/ml-recog_deploy_evaluate.yaml
TensorRT Inference
docker run --gpus all --rm --shm-size=16g \
  -v /path/to/specs:/specs \
  -v /path/to/inference:/data \
  -v /path/to/results:/results \
  "$TAO_DEPLOY_IMAGE" \
  ml_recog inference -e /specs/ml-recog_deploy_inference.yaml

Deploy action metadata is in tao-deploy-metric-learning-recognition.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 and export with the ml-recog skill.

  2. Keep the exported ONNX artifact and any sidecar files together in the mounted model directory.

  3. Build the TensorRT engine with this workflow.

  4. Run TensorRT evaluate or inference from the engine artifact produced by gen_trt_engine.

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

Required Inputs

ActionRequired artifact or dataSpec key
gen_trt_engineExported ONNX modelgen_trt_engine.onnx_file
gen_trt_engineCalibration images for INT8gen_trt_engine.tensorrt.calibration.cal_image_dir
evaluateTensorRT engineevaluate.trt_engine
evaluateReference setdataset.val_dataset.reference
evaluateQuery setdataset.val_dataset.query
inferenceTensorRT engineinference.trt_engine
inferenceReference setdataset.val_dataset.reference
inferenceInput/query image folderinference.input_path

For direct Docker runs, mount input folders at the same paths used in the spec. For chained jobs, map exported ONNX artifacts into gen_trt_engine.onnx_file; gen_trt_engine.trt_engine is the generated engine output path and is then mapped into evaluate.trt_engine or inference.trt_engine.

Spec Overrides

Carry structural model and dataset settings forward from the train/export spec. The deploy defaults are templates, not a substitute for the model-specific values used to produce the ONNX file.

Recommended starting overrides:

{
    'gen_trt_engine.tensorrt.data_type': 'INT8',
    'gen_trt_engine.tensorrt.calibration.cal_batch_size': 16,
    'gen_trt_engine.tensorrt.calibration.cal_batches': 100,
}

Model-specific notes:

  • The starter-kit deploy flow builds MLRecog engines with INT8, so provide real calibration images and a writable calibration cache path.

  • Keep reference and query sets paired consistently between evaluate and inference.

  • Use batch_size: 1 for deploy evaluate and inference when validating small or non-divisible datasets. Larger batch sizes can silently drop the final partial batch in TAO Deploy MLRecog evaluation/inference, so only raise this value after confirming the full input count is preserved.

Job Chain Mapping

ActionSpec fieldParent or output
gen_trt_enginegen_trt_engine.onnx_fileexport job ONNX
gen_trt_enginegen_trt_engine.trt_enginenew engine output path
gen_trt_engine INT8calibration image/cache fieldscalibration dataset and new cache output
evaluateevaluate.trt_engineengine job output
inferenceinference.trt_engineengine job output
inferenceinference.input_pathinput/query image folder

Outputs

ActionOutput
gen_trt_engineTensorRT engine and calibration cache under results_dir
evaluateRetrieval or recognition metrics under results_dir
inferenceRecognition outputs under results_dir

Known Pitfalls

Engine profile mismatch: Runtime batch size for evaluate or inference must fit within the TensorRT min/opt/max profile used during gen_trt_engine.

Template class or shape mismatch: Copy class count, input resolution, backbone, and post-processing settings from train/export before running TAO Deploy.

INT8 calibration missing: INT8 builds need an extracted calibration image directory, a writable cache path, and enough images for cal_batch_size * cal_batches.

Mounted paths do not exist: TAO Deploy checks local paths inside the container. Make sure every path in the spec has a matching Docker mount or job artifact mapping.

Deploy inference input missing: ml_recog inference in TAO Deploy requires inference.input_path. dataset.val_dataset.query alone is not consumed by the deploy inference entrypoint.

Tail batch dropped: If deploy evaluation or inference processes fewer query images than exist under the input folder, lower evaluate.batch_size or inference.batch_size to 1. The TensorRT profile still needs min_batch_size: 1.

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, Needs Node.js

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-metric-learning-recognition · 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-metric-learning-recognition.zip