Tao Train Sparse4d

NVIDIAOfficialCreated by NVIDIA Corporation

Skill
Workflow
Software development
Apache-2.0
Medium risk
Has scripts

From the author

Prepare calibrated multi-camera data and train, evaluate, run inference, export, or quantize TAO Sparse4D 3D detection and tracking models. Includes 2D-to-3D geometric distillation with released LTT weights. Use for Sparse4D adaptation and temporal multi-camera perception workflows.

— the description by NVIDIA Corporation

AutoGineer summary

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

The tao-train-sparse4d skill provides a structured workflow for preparing multi-camera data and managing the full lifecycle of Sparse4D 3D detection and tracking models within the NVIDIA TAO ecosystem. It supports data conversion, training, evaluation, inference, model export, and quantization. The skill includes specialized support for 2D-to-3D geometric distillation using released LTT weights, enabling temporal multi-camera perception workflows.

What it does

Converts raw multi-camera scene data into OVPKL format for model training.
Executes training, evaluation, and inference for Sparse4D models.
Supports 2D-to-3D geometric distillation for enhanced perception.
Exports trained models to ONNX format and performs model quantization.
Integrates with AutoML policies for optimized training runs.
Provides guidance on backbone selection and checkpoint management.

When to use it

When developing 3D detection or tracking systems using multi-camera inputs.
When adapting Sparse4D models to new datasets or specific camera configurations.
When performing geometric distillation to leverage 2D annotations for 3D tasks.
When preparing models for deployment through export and quantization.

Advantages

Standardized workflow for complex multi-camera perception tasks.
Automated handling of geometric distillation and temporal data.
Direct integration with TAO Toolkit runtime and data services.
Consistent artifact management across training, evaluation, and export.

Usage examples

“Convert my raw multi-camera dataset for Sparse4D training.”: The agent will trigger the dataset_convert action using the specified experiment template and data root, producing the necessary OVPKL files.
“Train a Sparse4D model using ResNet-50 and geometric distillation.”: The agent will configure the training job with the ResNet-50 backbone, apply the LTT weights, and initiate the training process on the allocated infrastructure.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/tao-train-sparse4d/download

Unzip it into the cross-client skills folder of your project:

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

Documentation by NVIDIA Corporation

Sparse4D

Standalone install? If the TAO skill bank plugin did not initialize the session, run tao-setup for host preflight, credentials, and cross-skill discovery.

Sparse4D predicts 3D boxes and tracking IDs from synchronized, calibrated multi-camera images. Start with the selected model's experiment specification and checkpoint. The canonical TAO documentation covers the model workflow.

Instructions

Identify the requested action, data supervision, selected checkpoint, and platform. Read the action contract and the selected platform skill. Preserve the user's platform, model, data, and training-budget choices.
Match the backbone, ordered classes, image preprocessing, anchors, and temporal dimensions to the selected checkpoint. Follow Backbone and checkpoint selection below before preparing the specification.
Use existing compatible info PKLs when supplied. For raw data, follow local conversion and artifact checks. For calibrated real scenes with 2D targets, read geometric distillation; that route does not require 3D annotations or conversion-generated anchors.
Start from references/spec_template_<action>.yaml and the selected release's experiment specification. Resolve paths against actual staged artifacts. Bind results_dir and any action-specific results_dir to the current job output directory; released specifications can contain old output paths. Write nested YAML, not flat dotted keys; do not fabricate train/val/test files or scene suffixes. Check the installed runtime exposes the fields used by the requested workflow.
Resolve the model-level image for model actions and the action-level Data Services image for dataset_convert. For a requested TAO release, use the matching skill-bank release branch and its image pins; do not substitute the default branch's release. Follow tao-launch-workflow and the chosen platform's submit / status / logs / cancel contract, retaining its job record and explicit output directory. Existing user authorization applies; request missing launch approval only for work not already authorized.
Verify the produced artifacts and model metrics. A successful process or short training run is a smoke result, not evidence of improved 3D accuracy. Do not report unpublished experimental fixes or another run's results as validation of the selected image.

Backbone and checkpoint selection

Respect an explicit ResNet-50 or ResNet-101 choice. For an existing Sparse4D checkpoint, use the accompanying experiment specification and release metadata to determine model.backbone.type (resnet_50 or resnet_101). If they conflict with the requested backbone, resolve that mismatch before launch; do not change the architecture to make a checkpoint load partially.
If no checkpoint/backbone has been selected, ask which compatible released model to use. The schema default resnet_101 is a configuration default, not a recommendation or evidence about the user's checkpoint.
Preserve the selected checkpoint's class order, anchors, input dimensions, and temporal/query dimensions. A filename alone is insufficient when its provenance is unclear.
The LTT MLP is a separate geometry adapter. Downloading it from the ResNet-50 bundle does not select the Sparse4D backbone. Its ordered taxonomy must match the training data and model.
Fine-tuning uses train.pretrained_model_path. Continuing a run uses train.resume_training_checkpoint_path and a compatible saved training state. Random initialization with an empty pretrained path is suitable only when explicitly requested, for example a wiring smoke test.

Train action policy

Read references/skill_info.yaml before train requests. This model is AutoML-enabled. Preserve an explicit automl_policy: on / off; requests for plain training, no HPO, a fixed-specification reproduction, a bounded wiring smoke test, or an exact continuation mean off for that run. Otherwise default to on and route through tao-skill-bank:tao-run-automl when both schemas/train.schema.json and references/spec_template_train.yaml are available. Preserve dataset, checkpoint, specification, GPU/platform, and budget overrides. If the schema/template is missing, report that AutoML is unavailable and use direct training within the user's request.

AutoML's monitoring name is val_mAP; Sparse4D emits img_bbox_NuScenes/mAP and mAP as aliases. A promoted resume job may carry the source rung's metric without a new evaluation: report its provenance and verify the resumed checkpoint independently. Follow the AutoML skill's baseline-evaluation requirement. Evaluate, inference, export, and quantize remain in this skill.

Training Requirements

Training needs converted OVPKL data, held-out labeled validation data, matching anchors, and the selected pretrained checkpoint or resume state. Preserve the selected backbone and ordered taxonomy. Geometric distillation additionally needs the released LTT checkpoint and prepared supervision caches. Choose the GPU count and training budget from the user's request and available resources.

Per-Action Dataset Requirements

The model uses OVPKL annotations. The action contract declares staged inputs, commands, outputs, and optional artifacts. Paths embedded in info PKLs, split lists, and lazy indexes must also remain visible inside the selected runtime; staging a split file alone does not stage its referenced data.

Action	Runtime command	Required data / model artifacts
`dataset_convert`	`annotations convert -e SPEC` (Data Services)	Raw scene root, calibration, images; 3D annotations for labeled conversion only
`train`	`sparse4d train -e SPEC`	Training and held-out validation PKLs/splits, image root, matching anchors, selected pretrained or resume checkpoint; optional LTT/cache artifacts for the chosen supervision route
`evaluate`	`sparse4d evaluate -e SPEC`	`evaluate.checkpoint`, matching anchors, labeled held-out PKLs at `dataset.test_dataset.ann_file`, image root
`inference`	`sparse4d inference -e SPEC`	`inference.checkpoint`, matching anchors, input PKLs at `dataset.test_dataset.ann_file`, image root
`export`	`sparse4d export -e SPEC`	`export.checkpoint`, matching anchors and architecture, explicit `export.onnx_file`; no training datasets or external LTT checkpoint
`quantize`	`sparse4d quantize -e SPEC`	`quantize.model_path` and the selected backend's calibration inputs; check runtime backend support

The evaluation CLI calls the test dataloader. Setting only dataset.val_dataset.ann_file does not select its evaluation data; that field is used during training validation. Keep the unused dataset sections from the complete specification without inventing or staging unused annotation files.

Resolve model.head.instance_bank.anchor as an explicit model artifact from the selected bundle or a compatible labeled conversion. It is not inferred from a mandatory training dataset for evaluation or export.

Use checkpoint and output resolution for exact artifact handoff. Do not choose the first checkpoint found or rely on a removed SDK job resolver.

Typical Spec Overrides

For AutoML, construct spec_overrides from concrete staged paths in the table above and skill_info.yaml's data_sources; dotted keys are an AutoML override map, not the container YAML format. Set only the inputs needed by the selected action.

Scope	Overrides to resolve
Training data	`dataset.data_root`, `dataset.train_dataset.ann_file`, `dataset.val_dataset.ann_file`
Model initialization	`model.backbone.type`, `model.head.instance_bank.anchor`, `dataset.classes`, and `train.pretrained_model_path` or `train.resume_training_checkpoint_path`
Training resources	`train.num_gpus`, `train.num_epochs`, `dataset.batch_size`, and `dataset.num_workers`, preserving the requested budget
Geometric distillation	The LTT/cache paths and route fields in the training fragment; preserve their validated class order and supervision policy during HPO
Evaluation and inference	`dataset.data_root`, `dataset.test_dataset.ann_file`, matching anchors, and the action's checkpoint
Output	`results_dir` and the action-specific output paths bound to the current job

With dataset.lazy_load: true, stage the split's parent directory as a folder, including <split>_lazy_index.pkl beside the split and _pkl_cam_counts.pkl when used. Point ann_file into that staged directory; do not let file-only staging relocate it away from its index. Keep referenced PKLs and images visible, and rebuild the index after relocation. dataset.pkl_cam_counts_path is an optional camera-count override, not the lazy index.

Configuration and resource checks

Generated schemas and templates describe the packaged contract; schemas/manifest.json lists actions. Do not require a TAO Core checkout on the user's machine. Use the runtime's matching release specification for launch: a schema that knows a new field does not make an older image support it.

model.backbone.type: match the selected checkpoint.
train.optim.lr, train.optim.lr_scheduler, and train.optim.grad_clip: optimizer settings are nested under optim.
dataset.batch_size: per-GPU batch size. dataset.max_cameras can reduce sampled training cameras when supported; validate the resulting supervision coverage.
train.precision: bf16, fp16, or fp32, subject to hardware/runtime support. BF16 is not mandatory.
train.num_gpus, train.gpu_ids, train.num_nodes: use the selected platform's allocation. One-GPU smoke training is supported; memory needs depend on the backbone, resolution, cameras, batch size, and temporal configuration.
dataset.num_frames and dataset.num_bev_groups are scheduling/data-size settings, not an activation-memory sequence-length knob. Inspect actual dataloader length and iteration counts before comparing training budgets across datasets or GPU counts.
dataset.eval_dist_fcn and dataset.eval_hota: select supported detection/tracking evaluation. Keep thresholds, class order, dataset, and raw-versus-EMA checkpoint choice identical for comparisons.

Lightning manages the local workers. Do not add a second distributed launcher. Use the platform's multi-node environment contract; TAO's WORLD_SIZE launcher variable denotes node count, not the global GPU count. Mixed 3D/2D distributed training additionally needs the synchronized route settings in the geometric-distillation reference.

Error patterns

Missing annotation or image: inspect the converter outputs and embedded paths. Preserve the emitted BEV-group suffix, camera IDs, frame IDs, and mount roots. A conversion of train does not also create val and test outputs.
Missing anchor: reuse the selected pretrained bundle's matching anchors, or use labeled conversion's generated anchors when compatible. Annotation-free conversion intentionally skips anchor initialization.
Legacy HDF5 depth tuple: inspect the affected labeled PKL and use the optional normalization helper in the conversion reference only when its documented layout matches. Unlabeled scenes have no depth paths to normalize.
Temporal OOM: first reduce per-GPU batch size or supported camera sampling; preserve checkpoint architecture. Do not blindly shrink anchor/temporal dimensions or treat num_frames as a memory fix.
LTT or teacher cache mismatch: verify ordered classes, scene/camera/frame joins, and container paths. The released LTT route supports its original seven classes; changing class names does not adapt the weights.
Export reshape: check the exporter contract in the conversion reference before training a reduced smoke model. Current export uses 20 dummy cameras and 600 cached temporal instances; successful inference alone does not establish export compatibility.
Unsupported quantize backend/image: report the selected image, backend, exact checkpoint, and failure. Do not claim a result from a historical validation image proves the current runtime works, or remove the action to hide the failure.

Files

.gitleaks.toml252 B
.gitleaksignore8.1 KiB
ATTRIBUTION.mdAdded by AutoGineer924 B
BENCHMARK.md8.2 KiB
LICENSELicence file added by AutoGineer11.2 KiB
SKILL.md12.8 KiB
config/skillspector-baseline.yaml834 B
evals/evals.json7.2 KiB
references/geometric_distillation.md9.5 KiB
references/geometric_distillation_train.yaml926 B
references/local_docker_conversion.md6.8 KiB
references/skill_info.yaml7.3 KiB
references/spec_param_inference.md2.0 KiB
references/spec_template_dataset_convert.yaml1.7 KiB
references/spec_template_evaluate.yaml8.6 KiB
references/spec_template_export.yaml8.7 KiB
references/spec_template_inference.yaml8.7 KiB
references/spec_template_quantize.yaml8.4 KiB
references/spec_template_train.yaml8.4 KiB
schemas/dataset_convert.schema.json14.4 KiB
schemas/evaluate.schema.json136.1 KiB
schemas/export.schema.json135.7 KiB
schemas/inference.schema.json136.6 KiB
schemas/manifest.json16.9 KiB
schemas/quantize.schema.json132.3 KiB
schemas/train.schema.json132.3 KiB
scripts/normalize_depth_paths.pyScript3.4 KiB
skill-card.md4.9 KiB
skill.oms.sig9.8 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 Python, Needs Node.js

The author says: Requires a compatible TAO runtime; Docker execution requires docker and nvidia-container-toolkit.

Security

What our scanner noticed· Medium risk

Large base64-encoded blobs
Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

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-sparse4d · commit fce3cca

Licence

Apache License 2.0 (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE-APACHE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-09

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-sparse4d.zip