Individual skill
tao-train-sparse4d
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.
skills/tao-train-sparse4d/SKILL.md
Source commit fce3cca4170be75e82c64920654d56ee2811b005
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,913
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- coding-agents Repository topic
- cuda Repository topic
- developer-tools Repository topic
- llm Repository topic
- omniverse Repository topic
- temporal Declared skill tag
- 3d Declared skill tag
- detection Declared skill tag
- tracking Declared skill tag
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
.gitleaks.tomlasset · 252 bytes.gitleaksignoreasset · 8,245 bytesBENCHMARK.mddoc · 8,403 bytesSKILL.mdcore · 13,089 bytesSKILL.mdcore · 13,089 bytesSKILL.mdcore · 13,089 bytesSKILL.mdcore · 13,089 bytesconfig/skillspector-baseline.yamlasset · 834 bytesevals/evals.jsonasset · 7,356 bytesreferences/geometric_distillation.mddoc · 9,704 bytesreferences/geometric_distillation_train.yamlasset · 926 bytesreferences/local_docker_conversion.mddoc · 7,000 bytesreferences/skill_info.yamlasset · 7,468 bytesreferences/spec_param_inference.mddoc · 2,092 bytesreferences/spec_template_dataset_convert.yamlasset · 1,751 bytesreferences/spec_template_evaluate.yamlasset · 8,850 bytesreferences/spec_template_export.yamlasset · 8,866 bytesreferences/spec_template_inference.yamlasset · 8,903 bytesreferences/spec_template_quantize.yamlasset · 8,650 bytesreferences/spec_template_train.yamlasset · 8,650 bytesschemas/dataset_convert.schema.jsonasset · 14,710 bytesschemas/evaluate.schema.jsonasset · 139,413 bytesschemas/export.schema.jsonasset · 138,992 bytesschemas/inference.schema.jsonasset · 139,903 bytesschemas/manifest.jsonasset · 17,288 bytesschemas/quantize.schema.jsonasset · 135,446 bytesschemas/train.schema.jsonasset · 135,440 bytesscripts/normalize_depth_paths.pyruns · 3,478 bytesskill-card.mddoc · 5,068 bytesskill.oms.sigasset · 10,001 bytes
Read excerpt
# 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](https://docs.nvidia.com/tao/tao-toolkit/latest/text/cv_finetuning/pytorch/sparse4d/sparse4d.html) covers the model workflow.
## Instructions
1. Identify the requested action, data supervision, selected checkpoint, and platform. Read [the action contract](references/skill_info.yaml) and the selected platform skill. Preserve the user's platform, model, data, and training-budget choices.
2. 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.
3. Use existing compatible info PKLs when supplied. For raw data, follow [local conversion and artifact checks](references/local_docker_conversion.md). For calibrated real scenes with 2D targets, read [geometric distillation](references/geometric_distillation.md); that route does not require 3D annotations or conversion-generated anchors.
4. 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.
5. 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.
6. 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.