
Metric Learning Recognition
OfficialFreeFine-tune models for visual recognition tasks.
Free · Opens the source repo
What Metric Learning Recognition does
The Metric Learning Recognition skill is designed for developers and data scientists working on fine-grained visual recognition tasks. It enables the training of models that learn embeddings for retrieval-based matching, which is particularly useful in scenarios such as retail product recognition. By utilizing triplet and contrastive losses, this skill helps create robust models that can accurately identify and differentiate between similar items based on visual features.
This skill integrates seamlessly with the TAO (Train, Adapt, Optimize) framework, allowing users to train, evaluate, export, and run inference on metric learning models. Users can set the model.pretrained_model_path to leverage pretrained backbones, enhancing model performance and reducing training time. The skill provides a structured approach to deploying TensorRT actions, with detailed references and spec templates included for each action, ensuring that users can efficiently manage their model lifecycle from training to inference.
Developers will find the packaged schemas and templates invaluable for automating the training process, especially with the AutoML capabilities included. The skill is designed to handle various datasets and provides clear requirements for each action, ensuring that users can quickly set up their training and evaluation environments. With built-in support for monitoring metrics like validation precision, users can track model performance and make informed adjustments during training.
Overall, the Metric Learning Recognition skill is an essential tool for anyone looking to implement advanced visual recognition systems using deep learning techniques. Whether you are developing applications in retail, security, or any domain requiring fine-grained visual analysis, this skill provides the necessary tools and frameworks to streamline your workflow.
When to use it
Use this skill when you need to train or evaluate models for visual recognition, particularly in applications like product identification or image retrieval.
When not to use it
This skill may not be suitable for general image classification tasks that do not require fine-grained recognition or when simpler models suffice.
What you can build with it
Retail Product Recognition
Train models to accurately identify and match retail products based on visual features, improving inventory management.
Image Retrieval Systems
Implement systems that retrieve images based on learned embeddings, enhancing user experience in applications like search engines.
Fine-Grained Classification
Develop models that distinguish between visually similar items, useful in domains like fashion or automotive industries.
How to install Metric Learning Recognition
View source1. Install with the skills CLI
npx skills add nvidia/skills/tao-train-metric-learning-recognition --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by nvidiaML Recog
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 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
- Dataset type: ml_recog
- Formats: default
- Monitoring metric: val Precision at Rank 1
Per-Action Dataset Requirements
| Action | Spec Key | Source | Files | List? |
|---|---|---|---|---|
| evaluate | dataset.val_dataset | train_datasets | reference: 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.gz | No |
| inference | dataset.val_dataset | train_datasets | reference: metric_learning_recognition/retail-product-checkout-dataset_classification_demo/unknown_classes/reference.tar.gz, query: | No |
| inference | inference.input_path | train_datasets | metric_learning_recognition/retail-product-checkout-dataset_classification_demo/unknown_classes/test.tar.gz | No |
| train | dataset.train_dataset | train_datasets | metric_learning_recognition/retail-product-checkout-dataset_classification_demo/known_classes/train.tar.gz | No |
| train | dataset.val_dataset | train_datasets | reference: 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.gz | No |
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_sizealso 4. For training and AutoML search,train.batch_sizemust be divisible bydataset.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 Key | Description | Default |
|---|---|---|
train.num_gpus | Number of GPUs | 1 |
train.gpu_ids | GPU device indices | [0] |
- Strategy:
auto(Lightning picks best strategy automatically) - No explicit
num_nodesordistributed_strategyconfig — 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:
| Action | Spec Field | Inference Function | Meaning |
|---|---|---|---|
| evaluate | evaluate.checkpoint | parent_model | model file inferred from the parent job results folder |
| evaluate | results_dir | output_dir | current job results directory |
| export | export.checkpoint | parent_model | model file inferred from the parent job results folder |
| export | export.onnx_file | create_onnx_file | output ONNX path |
| export | results_dir | output_dir | current job results directory |
| inference | inference.checkpoint | parent_model | model file inferred from the parent job results folder |
| inference | results_dir | output_dir | current job results directory |
| train | model.pretrained_model_path | ptm_if_no_resume_model | PTM when no resume checkpoint exists |
| train | results_dir | output_dir | current job results directory |
| train | train.resume_training_checkpoint_path | resume_model | model 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
Frequently asked questions about Metric Learning Recognition
Similar skills
Spring Boot Testing
Master testing techniques for Spring Boot 4 applications.
GitHub Issues
Manage GitHub issues efficiently with MCP tools.
Geofeed Tuner
Optimize your IP geolocation feeds in CSV format.
Batch Files
Master Windows batch scripting for automation and task management.
Adobe Illustrator Scripting
Automate your Illustrator workflows with ExtendScript.
Plugin Structure
Create and organize Claude Code plugins effectively.
