Tao Train Reid
NVIDIAOfficialCreated by NVIDIA Corporation
- Skill
- Tool integration
- Data and AI
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured interface for managing the lifecycle of person re-identification models within the TAO ecosystem. It utilizes metric learning to generate discriminative embeddings, enabling the identification of the same individual across different camera views. The skill supports training, evaluation, inference, and model export, with built-in support for AutoML to optimize performance metrics like cmc_rank_1.
What it does
- Trains person re-identification models using metric learning.
- Evaluates model performance using mAP and CMC rank metrics.
- Exports trained models to ONNX format for deployment.
- Performs inference on test and query datasets.
- Supports AutoML for automated hyperparameter optimization.
- Manages model checkpoints and configuration overrides.
When to use it
- When you need to match individuals across multiple camera feeds.
- When developing computer vision pipelines for person tracking.
- When you need to optimize re-identification model accuracy via AutoML.
- When preparing a model for deployment in a production environment.
Advantages
- Enables cross-camera person matching through discriminative embeddings.
- Automates hyperparameter tuning via integrated AutoML support.
- Provides standardized workflows for training, evaluation, and export.
- Supports large-batch training for improved metric learning performance.
Usage examples
- “Train a new person re-identification model using the provided training specification.”
- The agent initiates the training process using the specified configuration, optimizing for cmc_rank_1.
- “Evaluate my re-identification model performance.”
- The agent runs the evaluation action against the test and query datasets, reporting mAP and CMC ranks.
- “Export my trained re-identification model to ONNX.”
- The agent processes the checkpoint and generates an ONNX file for deployment.
- “Run inference on my test dataset.”
- The agent executes the inference action and produces a JSON file containing the results.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/tao-train-reid/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip tao-train-reid.zip -d .agents/skills
Documentation by NVIDIA Corporation
Re-Identification
Standalone install? If this session was not initialized by the TAO skill bank plugin, run the
tao-setupskill first (host preflight, credentials, cross-skill discovery).
Person re-identification. Learns discriminative embeddings to match the same person across different camera views. Metric learning based.
Set model.pretrained_model_path for pretrained weights.
Quick Start (docker run)
Docker-native launch — no TAO SDK and no Python on the host. Use the local Docker/platform skill instead when it gives a stricter environment-specific command (non-root UID mapping, cache redirects, remote daemons).
TAO_PYT_IMAGE_DEFAULT=nvcr.io/nvidia/tao/tao-toolkit:7.3.0-pyt # versions-key: images.tao_toolkit.pyt
TAO_PYT_IMAGE="${TAO_PYT_IMAGE:-$TAO_PYT_IMAGE_DEFAULT}"
RUN_ROOT="${RUN_ROOT:-$PWD}"
DOCKER_COMMON=(
--rm --gpus all --shm-size=8g
--shm-size=8g
--ulimit memlock=-1
--ulimit stack=67108864
-v "$RUN_ROOT/data:/data:ro"
-v "$RUN_ROOT/specs:/specs:ro"
-v "$RUN_ROOT/results:/results"
)Train:
docker run "${DOCKER_COMMON[@]}" "$TAO_PYT_IMAGE" \
re_identification train -e /specs/train.yamlEvaluate:
docker run "${DOCKER_COMMON[@]}" "$TAO_PYT_IMAGE" \
re_identification evaluate -e /specs/evaluate.yamlInference:
docker run "${DOCKER_COMMON[@]}" "$TAO_PYT_IMAGE" \
re_identification inference -e /specs/inference.yamlExport:
docker run "${DOCKER_COMMON[@]}" "$TAO_PYT_IMAGE" \
re_identification export -e /specs/export.yamlEvery action takes its spec with -e; results_dir is set in the spec or
overridden on the command line. Mount any pretrained-weights directory the spec
references, and keep every in-container path consistent across actions.
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.
Supported Actions
The packaged Re-Identification PyT CLI supports train, evaluate, inference, export, and default_specs. This model skill exposes the runnable user actions train, evaluate, inference, and export; resume/retrain is performed through train with train.resume_training_checkpoint_path.
Do not advertise or synthesize dataset_convert, deploy, prune, quantize, gen_trt_engine, or standalone retrain for this model unless the packaged model skill and real CLI add those actions.
Training Requirements
Dataset type: re_identification
Formats: default
AutoML training metric:
cmc_rank_1(maximize). Train status files emit this retrieval KPI for trial ranking.Standalone evaluation metric:
mAP. The evaluate action writesmAPto its status KPI and prints the CMC ranks in its console table; do not expect standalone evaluate status to containcmc_rank_1.
Per-Action Dataset Requirements
| Action | Spec Key | Source | Files | List? |
|---|---|---|---|---|
| evaluate | evaluate.test_dataset | train_datasets | sample_test.tar.gz | No |
| evaluate | evaluate.query_dataset | train_datasets | sample_query.tar.gz | No |
| inference | inference.test_dataset | train_datasets | sample_test.tar.gz | No |
| inference | inference.query_dataset | train_datasets | sample_query.tar.gz | No |
| train | dataset.train_dataset_dir | train_datasets | sample_train.tar.gz | No |
| train | dataset.test_dataset_dir | train_datasets | sample_test.tar.gz | No |
| train | dataset.query_dataset_dir | train_datasets | sample_query.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"
CHECKPOINT = "/results/{train_job_id}/results_dir/model_epoch_000_step_00099.pth"train (mandatory data sources):
{
"train.num_epochs": 30,
"train.checkpoint_interval": 10,
"train.validation_interval": 10,
"train.num_gpus": 1,
"dataset.num_classes": 100,
"dataset.num_workers": 4,
"dataset.batch_size": 16,
"dataset.num_instances": 4,
"dataset.train_dataset_dir": f"{S3_TRAIN}/sample_train.tar.gz",
"dataset.test_dataset_dir": f"{S3_TRAIN}/sample_test.tar.gz",
"dataset.query_dataset_dir": f"{S3_TRAIN}/sample_query.tar.gz",
}resume train (mandatory checkpoint):
{
"train.num_epochs": 31,
"train.resume_training_checkpoint_path": CHECKPOINT,
"dataset.num_classes": 100,
"dataset.batch_size": 16,
"dataset.num_instances": 4,
"dataset.train_dataset_dir": f"{S3_TRAIN}/sample_train.tar.gz",
"dataset.test_dataset_dir": f"{S3_TRAIN}/sample_test.tar.gz",
"dataset.query_dataset_dir": f"{S3_TRAIN}/sample_query.tar.gz",
}evaluate (mandatory data sources and checkpoint):
{
"evaluate.test_dataset": f"{S3_TRAIN}/sample_test.tar.gz",
"evaluate.query_dataset": f"{S3_TRAIN}/sample_query.tar.gz",
"evaluate.checkpoint": CHECKPOINT,
"evaluate.output_cmc_curve_plot": "/results/{evaluate_job_id}/results_dir/cmc_curve.png",
"evaluate.output_sampled_matches_plot": "/results/{evaluate_job_id}/results_dir/sampled_matches.png",
}export (mandatory checkpoint and output):
{
"export.checkpoint": CHECKPOINT,
"export.onnx_file": "/results/{export_job_id}/results_dir/reid.onnx",
}inference (mandatory data sources and checkpoint):
{
"inference.test_dataset": f"{S3_TRAIN}/sample_test.tar.gz",
"inference.query_dataset": f"{S3_TRAIN}/sample_query.tar.gz",
"inference.checkpoint": CHECKPOINT,
"inference.output_file": "/results/{inference_job_id}/results_dir/reid_inference.json",
}For export and inference, provide explicit file paths for export.onnx_file and inference.output_file. For evaluate, provide explicit file paths for evaluate.output_cmc_curve_plot and evaluate.output_sampled_matches_plot. Keep these as spec values or spec_params mappings; do not declare them as file outputs in skill_info.yaml for local Docker until the runner distinguishes files from folders during output pre-creation.
Eval Dataset
Required. Evaluation requires test and query datasets for retrieval-based metrics (CMC, mAP).
Important Parameters
dataset.num_classes: Number of identities. Default 751. Must match the number of unique identities in training data.
model.backbone: Default resnet_50.
optim.base_lr: Base learning rate. Default 3.5e-4.
dataset.batch_size: Per-GPU batch size. Default 64. Re-ID benefits from large batches for better triplet/contrastive sampling.
dataset.num_instances: Number of instances per identity in a batch. Controls sampling strategy for metric learning.
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] |
Multi-GPU strategy:
ddp_find_unused_parameters_truesync_batchnormis always enabledPrecision forced to FP16 (
16-mixed)No explicit
num_nodesconfig — single-node oriented
Hardware
Minimum 1 GPU(s), recommended 2 GPU(s). 16GB+ VRAM per GPU. Re-ID models are relatively lightweight but benefit from large batch sizes for metric learning.
Error Patterns
num_classes mismatch: Ensure dataset.num_classes equals the number of unique identity folders in the training set.
Invalid triplet batch shape: dataset.batch_size must be compatible with dataset.num_instances so each mini-batch can be reshaped for hard-example mining. For local AutoML smoke runs, keep dataset.batch_size fixed to a known valid multiple such as 16 with dataset.num_instances: 4, and tune train.optim.base_lr instead of unconstrained batch size.
Query/gallery mismatch: Query and test (gallery) datasets must share the same identity namespace.
PyTorch 2.6 checkpoint load failure on checkpoint consumers: Current Re-ID
checkpoints include OmegaConf containers. For checkpoints produced by the same
trusted TAO train/AutoML workflow, set
TORCH_FORCE_NO_WEIGHTS_ONLY_LOAD=1 in downstream resume, evaluate, inference,
and export job env vars so Lightning/PyTorch can load the full checkpoint. Do
not use this env var for untrusted checkpoints.
AutoML metric extraction: Re-ID train status files report retrieval KPIs such as cmc_rank_1, cmc_rank_5, cmc_rank_10, and mAP, plus train loss. Default AutoML train launches must optimize cmc_rank_1 with direction: maximize; do not use val_loss as the metric for this model.
Checkpoint handoff: Use the checkpoint resolver on the best AutoML child job's results_dir/train/ folder and select the action-appropriate model_epoch_*.pth checkpoint. Re-ID also writes reid_model_latest.pth, but that is a latest symlink and should only be used when a caller explicitly requests latest. Preserve the same dataset identity count and query/gallery archives for downstream actions.
Default spec generation: The packaged default_specs CLI action does not
consume the normal -e <spec.yaml> experiment file for results_dir. Invoke it
with a Hydra override such as
re_identification default_specs results_dir=/workspace/run/results/default_specs.
Passing only -e leaves cfg.results_dir unset and fails with
MissingMandatoryValue: results_dir.
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 re_identification.config.json:
| Action | Spec Field | Inference Function | Meaning |
|---|---|---|---|
| evaluate | encryption_key | key | encryption key |
| evaluate | evaluate.checkpoint | parent_model | model file inferred from the parent job results folder |
| evaluate | evaluate.output_cmc_curve_plot | create_evaluate_cmc_plot_reid | ReID CMC plot path |
| evaluate | evaluate.output_sampled_matches_plot | create_evaluate_matches_plot_reid | ReID sampled matches plot path |
| evaluate | results_dir | output_dir | current job results directory |
| export | encryption_key | key | encryption key |
| 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 | encryption_key | key | encryption key |
| inference | inference.checkpoint | parent_model | model file inferred from the parent job results folder |
| inference | inference.output_file | create_inference_result_file_reid | ReID inference JSON path |
| inference | results_dir | output_dir | current job results directory |
| train | encryption_key | key | encryption key |
| 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.
Files
- ATTRIBUTION.mdAdded by AutoGineer912 B
- BENCHMARK.md6.9 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md14.1 KiB
- config/skillspector-baseline.yaml1.0 KiB
- evals/evals.json752 B
- references/skill_info.yaml4.4 KiB
- references/spec_template_evaluate.yaml2.4 KiB
- references/spec_template_export.yaml2.2 KiB
- references/spec_template_inference.yaml2.3 KiB
- references/spec_template_train.yaml2.2 KiB
- schemas/evaluate.schema.json37.4 KiB
- schemas/export.schema.json34.9 KiB
- schemas/inference.schema.json37.1 KiB
- schemas/manifest.json6.5 KiB
- schemas/train.schema.json33.7 KiB
- skill-card.md4.4 KiB
- skill.oms.sig7.1 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
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 a command-line tool, 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-reid · 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-reid.zip