Tao Train Pointpillars
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
The tao-train-pointpillars skill provides a comprehensive workflow for managing the lifecycle of PointPillars models, which are used for 3D object detection in autonomous driving and robotics. It supports dataset conversion, training, pruning, retraining, evaluation, and export. The skill is AutoML-enabled and integrates with TAO Deploy for TensorRT engine generation and inference. It requires specific data structures for LiDAR point clouds and relies on consistent data path management across all stages of the model development pipeline.
What it does
- Converts raw LiDAR point cloud data into a format suitable for training.
- Trains PointPillars models with support for resume training and AutoML optimization.
- Prunes trained models to reduce size and complexity.
- Evaluates model performance using 3D detection metrics like mAP.
- Exports models to ONNX format for deployment.
- Supports TensorRT engine generation and inference through integration with TAO Deploy.
When to use it
- When developing 3D object detection systems for autonomous vehicles or robotics.
- When you need to train a PointPillars model from scratch or resume from a checkpoint.
- When optimizing a model for production deployment using pruning and TensorRT.
- When you need to perform inference on LiDAR data using a trained or deployed model.
Advantages
- Efficient pillar-based representation for processing LiDAR data.
- Integrated support for the entire model lifecycle from conversion to deployment.
- AutoML capabilities to simplify hyperparameter tuning.
- Supports distributed training across multiple GPUs.
Usage examples
- “Train a PointPillars model using my LiDAR dataset.”
- The agent initiates the training process, ensuring the dataset is converted and the training parameters are configured according to the provided spec.
- “Prune my trained PointPillars model.”
- The agent runs the pruning action on the specified checkpoint, producing an optimized model artifact for subsequent retraining.
- “Evaluate the accuracy of my PointPillars model.”
- The agent executes the evaluation workflow, calculating 3D mAP and other detection metrics on the validation set.
- “Export my model to ONNX for deployment.”
- The agent converts the trained model checkpoint into an ONNX file, ready for TensorRT engine generation.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/tao-train-pointpillars/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip tao-train-pointpillars.zip -d .agents/skills
Documentation by NVIDIA Corporation
PointPillars
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).
PointPillars for 3D object detection from LiDAR point clouds. Encodes point clouds into a pseudo-image via pillar-based representation, then applies 2D detection. Used in autonomous driving / robotics.
Typically trained from scratch. Provide train.resume_training_checkpoint_path to resume.
For TAO Deploy TensorRT actions (gen_trt_engine, TensorRT evaluate, and TensorRT inference), read references/tao-deploy-pointpillars.md first. Deploy spec templates live in this skill's references/ folder with the spec_template_deploy_*.yaml prefix.
The packaged PyTorch PointPillars CLI supports dataset_convert, train, evaluate, inference, export, and prune. It does not expose a parent-model gen_trt_engine action; TensorRT engine generation is deploy-only. It also does not expose a separate retrain subcommand. Retraining from a pruned model uses pointpillars train -e ... with train.pruned_model_path populated.
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: pointpillars
Formats: default
AutoML training metric:
loss(minimize). This is the per-epoch KPI emitted by the train action and is the metric AutoML must extract for trial ranking.Standalone evaluation metrics: the evaluate action emits recall KPIs plus dataset-specific detection metrics. For the general point-cloud dataset, verify
bev mAPand3d mAP; do not substitute an evaluation mAP for AutoML's emitted trainingloss.
Per-Action Dataset Requirements
| Action | Spec Key | Source | Files | List? |
|---|---|---|---|---|
| dataset_convert | dataset.data_path | id | No | |
| evaluate | dataset.data_path | train_datasets | No | |
| evaluate | dataset.data_info_path | train_datasets | /results/{dataset_convert_job_id}/results_dir/data_info/ | No |
| export | dataset.data_path | train_datasets | No | |
| export | dataset.data_info_path | train_datasets | /results/{dataset_convert_job_id}/results_dir/data_info/ | No |
| inference | dataset.data_path | train_datasets | No | |
| inference | dataset.data_info_path | train_datasets | /results/{dataset_convert_job_id}/results_dir/data_info/ | No |
| prune | dataset.data_path | train_datasets | No | |
| prune | dataset.data_info_path | train_datasets | /results/{dataset_convert_job_id}/results_dir/data_info/ | No |
| retrain | dataset.data_path | train_datasets | No | |
| retrain | dataset.data_info_path | train_datasets | /results/{dataset_convert_job_id}/results_dir/data_info/ | No |
| train | dataset.data_path | train_datasets | No | |
| train | dataset.data_info_path | train_datasets | /results/{dataset_convert_job_id}/results_dir/data_info/ | 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.
DATA_ROOT = "s3://bucket/data/pointpillars"
DATA_INFO = "/results/{dataset_convert_job_id}/results_dir/data_info"
CHECKPOINT = "/results/{train_job_id}/results_dir/checkpoint_epoch_1.pth"
PRUNED_MODEL = "/results/{prune_job_id}/results_dir/pruned_0.1.tlt"The raw PointPillars data root must be an extracted folder containing matching train/lidar, train/label, val/lidar, and val/label subfolders before dataset_convert runs. If the source dataset is packaged as separate train/val archives, extract both under the same mounted data root and point dataset.data_path at that root.
train (mandatory data sources):
{
"train.num_epochs": 30,
"train.checkpoint_interval": 10,
"train.validation_interval": 10,
"train.num_gpus": 1,
"dataset.data_path": DATA_ROOT,
"dataset.data_info_path": DATA_INFO,
}resume train (mandatory checkpoint):
{
"dataset.data_path": DATA_ROOT,
"dataset.data_info_path": DATA_INFO,
"train.resume_training_checkpoint_path": CHECKPOINT,
}evaluate (mandatory data sources):
{
"dataset.data_path": DATA_ROOT,
"dataset.data_info_path": DATA_INFO,
"evaluate.checkpoint": CHECKPOINT,
}export (mandatory data sources):
{
"dataset.data_path": DATA_ROOT,
"dataset.data_info_path": DATA_INFO,
"export.checkpoint": CHECKPOINT,
"export.onnx_file": "/results/{export_job_id}/results_dir/pointpillars.onnx",
}inference (mandatory data sources):
{
"dataset.data_path": DATA_ROOT,
"dataset.data_info_path": DATA_INFO,
"inference.checkpoint": CHECKPOINT,
}prune (mandatory data sources):
{
"dataset.data_path": DATA_ROOT,
"dataset.data_info_path": DATA_INFO,
"prune.model": CHECKPOINT,
}retrain (mandatory data sources):
{
"dataset.data_path": DATA_ROOT,
"dataset.data_info_path": DATA_INFO,
"train.pruned_model_path": PRUNED_MODEL,
}For local Docker, DATA_INFO must be visible inside every train/evaluate/export/prune/retrain container. Use the dataset_convert job from the same results root, or mount/copy the converted results_dir/data_info folder into the current run and set dataset.data_info_path to that mounted container path. If the host scratch root is mounted at /results and the conversion artifacts live under host scratch/results/<job_id>/results_dir/data_info, the direct-job container path is /results/results/<job_id>/results_dir/data_info. Do not reuse a /results/<job_id>/... path from another run root unless that folder is mounted into the current job.
For AutoML train workflows, perform this as a launch preflight before calling AutoMLRunner.run: create or materialize the dataset_convert output under the current run's RESULTS_ROOT, set dataset.data_info_path to that current-run container path, and verify dbinfos_train.pkl, infos_train.pkl, and infos_val.pkl are present from the train container's point of view. If a runner is cloned or adapted from a prior AutoML algorithm, update the conversion artifact in the new run root; a stale CONVERT_JOB_ID from another results mount is not valid.
Eval Dataset
Optional. Validation data (val.tar.gz) is separate from training. Used for mAP evaluation.
Important Parameters
train.num_epochs: Default 80 (much higher than other TAO models). PointPillars needs more epochs for convergence on 3D detection.
train.lr: Learning rate. Default 0.003 (adam_onecycle scheduler).
dataset.class_names: List of 3D object classes. Default 7 classes (KITTI-style). Modify to match your dataset.
dataset.data_path: Path to point cloud data directory.
dataset.data_info_path: Path to data info files from dataset_convert step.
dataset.point_cloud_range: Spatial extent of the point cloud to consider. Must match your sensor configuration.
model.dense_head.anchor_generator_config: Anchor configurations per class. Must be tuned for your object sizes and the point cloud range.
Multi-GPU / Multi-Node
Launch method: torchrun (LIGHTNING_EXCLUDED_NETWORK). Uses PyTorch native DistributedDataParallel (NOT Lightning Trainer).
| Spec Key | Description | Default |
|---|---|---|
train.num_gpus | Number of GPUs per node | 1 |
train.gpu_ids | GPU device indices | [0] |
train.num_nodes | Number of nodes | 1 |
CUDA_VISIBLE_DEVICESis explicitly set fromTAO_VISIBLE_DEVICESUses
nn.parallel.DistributedDataParalleldirectly (not Lightning strategy)NODE_RANKis copied toRANKifRANKis unset
Multi-node env vars (set by orchestrator):
| Variable | Purpose |
|---|---|
WORLD_SIZE | Number of nodes |
NODE_RANK | This node's rank |
MASTER_ADDR | Rank-0 node IP |
MASTER_PORT | Rank-0 port (default 29500) |
NUM_GPU_PER_NODE | GPUs per node |
Hardware
Minimum 1 GPU(s), recommended 4 GPU(s). 16GB+ (V100 or A100) VRAM per GPU. PointPillars is relatively efficient for 3D detection. The main bottleneck is data I/O for large point cloud datasets.
Error Patterns
dataset_convert required: Training will fail if dataset.data_info_path is not populated from a prior dataset_convert job. Always run convert first, and verify the train container can see dbinfos_train.pkl and infos_train.pkl under dataset.data_info_path. A common local-Docker failure is a stale /results/<old_job_id>/... path from a different results root.
Point cloud range mismatch: If point_cloud_range does not match the actual sensor data extent, detections will be poor or empty.
Epoch numbering: PointPillars checkpoint epoch numbers may be offset by 1 from status.json reported epochs.
Checkpoint selection: PointPillars training emits checkpoints named like checkpoint_epoch_1.pth. For evaluation, inference, export, prune, and resume, select the intended checkpoint through the model/job checkpoint resolver and pass that exact file to evaluate.checkpoint, inference.checkpoint, export.checkpoint, prune.model, or train.resume_training_checkpoint_path. Do not guess by taking the newest model.pth; this model does not use that filename.
Prune/retrain key: PointPillars prune writes an encrypted .tlt artifact. Keep a non-empty key in the prune and retrain specs; the packaged templates use the TAO default tlt_encode. If key is omitted or null, the toolkit can still exit with a container success code while logging a passphrase error and creating an empty pruned_0.1.tlt. Always verify the pruned model is nonzero before using it for retrain.
Status files matter: Some PointPillars failures can be followed by Execution status: PASS in the entrypoint footer and a Docker exit code of 0. Check results_dir/status.json and the expected artifact before marking an action as passed.
Local results_dir wiring: For direct local-Docker specs, set the top-level results_dir as well as any action-specific *.results_dir field. If only evaluate.results_dir is set and the top-level field is left blank, evaluate can try to write under /opt/nvidia/eval and then still print the generic PASS footer. Treat that as a failed action unless the expected result directory and status/artifact files exist.
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 pointpillars.config.json:
| Action | Spec Field | Inference Function | Meaning |
|---|---|---|---|
| dataset_convert | results_dir | output_dir | current job results directory |
| evaluate | evaluate.checkpoint | parent_model | model file inferred from the parent job results folder |
| evaluate | key | key | encryption key |
| 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 | export.save_engine | create_engine_file | output TensorRT engine path |
| export | key | key | encryption key |
| export | results_dir | output_dir | current job results directory |
| inference | inference.checkpoint | parent_model | model file inferred from the parent job results folder |
| inference | inference.trt_engine | parent_model | model file inferred from the parent job results folder |
| inference | key | key | encryption key |
| inference | results_dir | output_dir | current job results directory |
| prune | key | key | encryption key |
| prune | prune.model | parent_model | model file inferred from the parent job results folder |
| prune | results_dir | output_dir | current job results directory |
| retrain | key | key | encryption key |
| retrain | results_dir | output_dir | current job results directory |
| retrain | train.pruned_model_path | parent_model | model file inferred from the parent job results folder |
| train | 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.
Deployment
Files
- ATTRIBUTION.mdAdded by AutoGineer936 B
- BENCHMARK.md6.9 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md15.6 KiB
- config/skillspector-baseline.yaml834 B
- evals/evals.json813 B
- references/skill_info.yaml5.2 KiB
- references/spec_template_dataset_convert.yaml5.6 KiB
- references/spec_template_deploy_evaluate.yaml1.8 KiB
- references/spec_template_deploy_gen_trt_engine.yaml149 B
- references/spec_template_deploy_inference.yaml1.8 KiB
- references/spec_template_evaluate.yaml5.7 KiB
- references/spec_template_export.yaml5.7 KiB
- references/spec_template_gen_trt_engine.yaml5.7 KiB
- references/spec_template_inference.yaml5.7 KiB
- references/spec_template_prune.yaml5.6 KiB
- references/spec_template_retrain.yaml5.6 KiB
- references/spec_template_train.yaml5.6 KiB
- references/tao-deploy-pointpillars.md6.3 KiB
- references/tao-deploy-pointpillars.skill_info.yaml2.6 KiB
- schemas/dataset_convert.schema.json59.4 KiB
- schemas/evaluate.schema.json60.7 KiB
- schemas/export.schema.json62.0 KiB
- schemas/gen_trt_engine.schema.json62.0 KiB
- schemas/inference.schema.json61.3 KiB
- schemas/manifest.json13.7 KiB
- schemas/prune.schema.json60.0 KiB
- schemas/retrain.schema.json59.4 KiB
- schemas/train.schema.json59.4 KiB
- skill-card.md4.8 KiB
- skill.oms.sig10.4 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 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-pointpillars · 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-pointpillars.zip