[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CQVQ9NXSCDFBQJ2Y14FXEG":3,"skill-same:01M7CQVQ9NXSCDFBQJ2Y14FXEG":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M7CQVQ9NXSCDFBQJ2Y14FXEG","tao-train-pointpillars",null,"PointPillars for 3D object detection from LiDAR point clouds. Encodes point clouds into a pseudo-image via a pillar-based representation, then applies 2D detection — used in autonomous driving and robotics. Use when training, evaluating, exporting, pruning, retraining, or running inference for a TAO PointPillars model. Trigger phrases include \"train PointPillars\", \"LiDAR 3D detection\", \"point-cloud object detection\", \"pillar-based 3D detector\".","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Ftao-train-pointpillars\u002Fskills\u002Ftao-train-pointpillars\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tao-train-pointpillars\ndescription: PointPillars for 3D object detection from LiDAR point clouds. Encodes point clouds into a pseudo-image via a\n  pillar-based representation, then applies 2D detection — used in autonomous driving and robotics. Use when training,\n  evaluating, exporting, pruning, retraining, or running inference for a TAO PointPillars model. Trigger phrases include\n  \"train PointPillars\", \"LiDAR 3D detection\", \"point-cloud object detection\", \"pillar-based 3D detector\".\nlicense: Apache-2.0\ncompatibility: Requires docker + nvidia-container-toolkit.\nmetadata:\n  version: \"0.1.0\"\n  author: NVIDIA Corporation\nallowed-tools: Read Bash\ntags:\n- point\n- cloud\n- 3d\n- detection\n---\n\n# PointPillars\n\nPointPillars 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 \u002F robotics.\n\nTypically trained from scratch. Provide train.resume_training_checkpoint_path to resume.\n\nFor TAO Deploy TensorRT actions (`gen_trt_engine`, TensorRT `evaluate`, and TensorRT `inference`), read `references\u002Ftao-deploy-pointpillars.md` first. Deploy spec templates live in this skill's `references\u002F` folder with the `spec_template_deploy_*.yaml` prefix.\n\nThe 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.\n\n## Dataclass Schemas\n\nGenerated TAO Core schemas are packaged in `schemas\u002F\u003Caction>.schema.json`, with `schemas\u002Fmanifest.json` listing available actions. Each generated schema also emits `references\u002Fspec_template_\u003Caction>.yaml` from the schema top-level `default` field. AutoML enablement is declared at the model layer in `references\u002Fskill_info.yaml` via `automl_enabled`. Runnable AutoML still requires `schemas\u002Ftrain.schema.json` and `references\u002Fspec_template_train.yaml` to exist and parse. Use the packaged train schema for `automl_default_parameters`, `automl_disabled_parameters`, defaults, min\u002Fmax bounds, enums, option weights, math conditions, dependencies, and popular parameters. Do not expect `~\u002Ftao-core` at runtime; maintainers regenerate schemas\u002Ftemplates before packaging the skill bank.\n\n## Train Action Policy\n\nThis model is AutoML-enabled at the model layer. Before handling any train-stage request, read `references\u002Fskill_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` \u002F `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\u002Ftrain.schema.json` and `references\u002Fspec_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\u002Fapplication overrides for datasets, specs, output directories, GPU\u002Fplatform settings, parent checkpoints, and `automl_policy`. Use direct model training only when `automl_policy: off` or the packaged train schema\u002Ftemplate is missing; in the missing-schema case, report that AutoML is enabled but not runnable for this model until schemas are generated.\n\nNon-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.\n\n## Training Requirements\n\n- **Dataset type:** pointpillars\n- **Formats:** default\n- **Monitoring metric:** loss\n\n### Per-Action Dataset Requirements\n\n| Action | Spec Key | Source | Files | List? |\n|---|---|---|---|---|\n| dataset_convert | dataset.data_path | id |  | No |\n| evaluate | dataset.data_path | train_datasets |  | No |\n| evaluate | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n| export | dataset.data_path | train_datasets |  | No |\n| export | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n| inference | dataset.data_path | train_datasets |  | No |\n| inference | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n| prune | dataset.data_path | train_datasets |  | No |\n| prune | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n| retrain | dataset.data_path | train_datasets |  | No |\n| retrain | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n| train | dataset.data_path | train_datasets |  | No |\n| train | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n\n### Typical Spec Overrides\n\nData 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`.\n\n```python\nDATA_ROOT = \"s3:\u002F\u002Fbucket\u002Fdata\u002Fpointpillars\"\nDATA_INFO = \"\u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\"\nCHECKPOINT = \"\u002Fresults\u002F{train_job_id}\u002Fresults_dir\u002Fcheckpoint_epoch_1.pth\"\nPRUNED_MODEL = \"\u002Fresults\u002F{prune_job_id}\u002Fresults_dir\u002Fpruned_0.1.tlt\"\n```\n\nThe raw PointPillars data root must be an extracted folder containing matching `train\u002Flidar`, `train\u002Flabel`, `val\u002Flidar`, and `val\u002Flabel` subfolders before `dataset_convert` runs. If the source dataset is packaged as separate train\u002Fval archives, extract both under the same mounted data root and point `dataset.data_path` at that root.\n\n**train (mandatory data sources):**\n```python\n{\n    \"train.num_epochs\": 30,\n    \"train.checkpoint_interval\": 10,\n    \"train.validation_interval\": 10,\n    \"train.num_gpus\": 1,\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n}\n```\n\n**resume train (mandatory checkpoint):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"train.resume_training_checkpoint_path\": CHECKPOINT,\n}\n```\n\n**evaluate (mandatory data sources):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"evaluate.checkpoint\": CHECKPOINT,\n}\n```\n\n**export (mandatory data sources):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"export.checkpoint\": CHECKPOINT,\n    \"export.onnx_file\": \"\u002Fresults\u002F{export_job_id}\u002Fresults_dir\u002Fpointpillars.onnx\",\n}\n```\n\n**inference (mandatory data sources):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"inference.checkpoint\": CHECKPOINT,\n}\n```\n\n**prune (mandatory data sources):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"prune.model\": CHECKPOINT,\n}\n```\n\n**retrain (mandatory data sources):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"train.pruned_model_path\": PRUNED_MODEL,\n}\n```\n\nFor local Docker, `DATA_INFO` must be visible inside every train\u002Fevaluate\u002Fexport\u002Fprune\u002Fretrain container. Use the dataset_convert job from the same results root, or mount\u002Fcopy the converted `results_dir\u002Fdata_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 `\u002Fresults` and the conversion artifacts live under host `scratch\u002Fresults\u002F\u003Cjob_id>\u002Fresults_dir\u002Fdata_info`, the direct-job container path is `\u002Fresults\u002Fresults\u002F\u003Cjob_id>\u002Fresults_dir\u002Fdata_info`. Do not reuse a `\u002Fresults\u002F\u003Cjob_id>\u002F...` path from another run root unless that folder is mounted into the current job.\n\nFor 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.\n## Eval Dataset\n\nOptional. Validation data (val.tar.gz) is separate from training. Used for mAP evaluation.\n\n## Important Parameters\n\n- **train.num_epochs**: Default 80 (much higher than other TAO models). PointPillars needs more epochs for convergence on 3D detection.\n- **train.lr**: Learning rate. Default 0.003 (adam_onecycle scheduler).\n- **dataset.class_names**: List of 3D object classes. Default 7 classes (KITTI-style). Modify to match your dataset.\n- **dataset.data_path**: Path to point cloud data directory.\n- **dataset.data_info_path**: Path to data info files from dataset_convert step.\n- **dataset.point_cloud_range**: Spatial extent of the point cloud to consider. Must match your sensor configuration.\n- **model.dense_head.anchor_generator_config**: Anchor configurations per class. Must be tuned for your object sizes and the point cloud range.\n\n## Multi-GPU \u002F Multi-Node\n\n**Launch method:** `torchrun` (LIGHTNING_EXCLUDED_NETWORK). Uses PyTorch native `DistributedDataParallel` (NOT Lightning Trainer).\n\n| Spec Key | Description | Default |\n|----------|-------------|---------|\n| `train.num_gpus` | Number of GPUs per node | 1 |\n| `train.gpu_ids` | GPU device indices | [0] |\n| `train.num_nodes` | Number of nodes | 1 |\n\n- `CUDA_VISIBLE_DEVICES` is explicitly set from `TAO_VISIBLE_DEVICES`\n- Uses `nn.parallel.DistributedDataParallel` directly (not Lightning strategy)\n- `NODE_RANK` is copied to `RANK` if `RANK` is unset\n\n**Multi-node env vars** (set by orchestrator):\n\n| Variable | Purpose |\n|----------|---------|\n| `WORLD_SIZE` | Number of nodes |\n| `NODE_RANK` | This node's rank |\n| `MASTER_ADDR` | Rank-0 node IP |\n| `MASTER_PORT` | Rank-0 port (default 29500) |\n| `NUM_GPU_PER_NODE` | GPUs per node |\n\n## Hardware\n\nMinimum 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\u002FO for large point cloud datasets.\n\n## Error Patterns\n\n**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 `\u002Fresults\u002F\u003Cold_job_id>\u002F...` path from a different results root.\n\n**Point cloud range mismatch**: If point_cloud_range does not match the actual sensor data extent, detections will be poor or empty.\n\n**Epoch numbering**: PointPillars checkpoint epoch numbers may be offset by 1 from status.json reported epochs.\n\n**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\u002Fjob 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.\n\n**Prune\u002Fretrain 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.\n\n**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\u002Fstatus.json` and the expected artifact before marking an action as passed.\n\n**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 `\u002Fopt\u002Fnvidia\u002Feval` and then still print the generic PASS footer. Treat that as a failed action unless the expected result directory and status\u002Fartifact files exist.\n\n## Spec Param \u002F Parent Model Inference\n\nModel-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.\n\nInference mappings from TAO Core `pointpillars.config.json`:\n\n| Action | Spec Field | Inference Function | Meaning |\n|---|---|---|---|\n| dataset_convert | `results_dir` | `output_dir` | current job results directory |\n| evaluate | `evaluate.checkpoint` | `parent_model` | model file inferred from the parent job results folder |\n| evaluate | `key` | `key` | encryption key |\n| evaluate | `results_dir` | `output_dir` | current job results directory |\n| export | `export.checkpoint` | `parent_model` | model file inferred from the parent job results folder |\n| export | `export.onnx_file` | `create_onnx_file` | output ONNX path |\n| export | `export.save_engine` | `create_engine_file` | output TensorRT engine path |\n| export | `key` | `key` | encryption key |\n| export | `results_dir` | `output_dir` | current job results directory |\n| inference | `inference.checkpoint` | `parent_model` | model file inferred from the parent job results folder |\n| inference | `inference.trt_engine` | `parent_model` | model file inferred from the parent job results folder |\n| inference | `key` | `key` | encryption key |\n| inference | `results_dir` | `output_dir` | current job results directory |\n| prune | `key` | `key` | encryption key |\n| prune | `prune.model` | `parent_model` | model file inferred from the parent job results folder |\n| prune | `results_dir` | `output_dir` | current job results directory |\n| retrain | `key` | `key` | encryption key |\n| retrain | `results_dir` | `output_dir` | current job results directory |\n| retrain | `train.pruned_model_path` | `parent_model` | model file inferred from the parent job results folder |\n| train | `key` | `key` | encryption key |\n| train | `model.pretrained_model_path` | `ptm_if_no_resume_model` | PTM when no resume checkpoint exists |\n| train | `results_dir` | `output_dir` | current job results directory |\n| train | `train.resume_training_checkpoint_path` | `resume_model` | model file inferred from the current job results folder |\n\nFor `parent_model` or `parent_model_folder`, pass the upstream train\u002Fexport\u002FAutoML 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.\n\n## Deployment\n\n- [tao-deploy-pointpillars](references\u002Ftao-deploy-pointpillars.md)\n","# PointPillars\n\nPointPillars 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 \u002F robotics.\n\nTypically trained from scratch. Provide train.resume_training_checkpoint_path to resume.\n\nFor TAO Deploy TensorRT actions (`gen_trt_engine`, TensorRT `evaluate`, and TensorRT `inference`), read `references\u002Ftao-deploy-pointpillars.md` first. Deploy spec templates live in this skill's `references\u002F` folder with the `spec_template_deploy_*.yaml` prefix.\n\nThe 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.\n\n## Dataclass Schemas\n\nGenerated TAO Core schemas are packaged in `schemas\u002F\u003Caction>.schema.json`, with `schemas\u002Fmanifest.json` listing available actions. Each generated schema also emits `references\u002Fspec_template_\u003Caction>.yaml` from the schema top-level `default` field. AutoML enablement is declared at the model layer in `references\u002Fskill_info.yaml` via `automl_enabled`. Runnable AutoML still requires `schemas\u002Ftrain.schema.json` and `references\u002Fspec_template_train.yaml` to exist and parse. Use the packaged train schema for `automl_default_parameters`, `automl_disabled_parameters`, defaults, min\u002Fmax bounds, enums, option weights, math conditions, dependencies, and popular parameters. Do not expect `~\u002Ftao-core` at runtime; maintainers regenerate schemas\u002Ftemplates before packaging the skill bank.\n\n## Train Action Policy\n\nThis model is AutoML-enabled at the model layer. Before handling any train-stage request, read `references\u002Fskill_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` \u002F `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\u002Ftrain.schema.json` and `references\u002Fspec_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\u002Fapplication overrides for datasets, specs, output directories, GPU\u002Fplatform settings, parent checkpoints, and `automl_policy`. Use direct model training only when `automl_policy: off` or the packaged train schema\u002Ftemplate is missing; in the missing-schema case, report that AutoML is enabled but not runnable for this model until schemas are generated.\n\nNon-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.\n\n## Training Requirements\n\n- **Dataset type:** pointpillars\n- **Formats:** default\n- **Monitoring metric:** loss\n\n### Per-Action Dataset Requirements\n\n| Action | Spec Key | Source | Files | List? |\n|---|---|---|---|---|\n| dataset_convert | dataset.data_path | id |  | No |\n| evaluate | dataset.data_path | train_datasets |  | No |\n| evaluate | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n| export | dataset.data_path | train_datasets |  | No |\n| export | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n| inference | dataset.data_path | train_datasets |  | No |\n| inference | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n| prune | dataset.data_path | train_datasets |  | No |\n| prune | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n| retrain | dataset.data_path | train_datasets |  | No |\n| retrain | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n| train | dataset.data_path | train_datasets |  | No |\n| train | dataset.data_info_path | train_datasets | \u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\u002F | No |\n\n### Typical Spec Overrides\n\nData 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`.\n\n```python\nDATA_ROOT = \"s3:\u002F\u002Fbucket\u002Fdata\u002Fpointpillars\"\nDATA_INFO = \"\u002Fresults\u002F{dataset_convert_job_id}\u002Fresults_dir\u002Fdata_info\"\nCHECKPOINT = \"\u002Fresults\u002F{train_job_id}\u002Fresults_dir\u002Fcheckpoint_epoch_1.pth\"\nPRUNED_MODEL = \"\u002Fresults\u002F{prune_job_id}\u002Fresults_dir\u002Fpruned_0.1.tlt\"\n```\n\nThe raw PointPillars data root must be an extracted folder containing matching `train\u002Flidar`, `train\u002Flabel`, `val\u002Flidar`, and `val\u002Flabel` subfolders before `dataset_convert` runs. If the source dataset is packaged as separate train\u002Fval archives, extract both under the same mounted data root and point `dataset.data_path` at that root.\n\n**train (mandatory data sources):**\n```python\n{\n    \"train.num_epochs\": 30,\n    \"train.checkpoint_interval\": 10,\n    \"train.validation_interval\": 10,\n    \"train.num_gpus\": 1,\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n}\n```\n\n**resume train (mandatory checkpoint):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"train.resume_training_checkpoint_path\": CHECKPOINT,\n}\n```\n\n**evaluate (mandatory data sources):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"evaluate.checkpoint\": CHECKPOINT,\n}\n```\n\n**export (mandatory data sources):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"export.checkpoint\": CHECKPOINT,\n    \"export.onnx_file\": \"\u002Fresults\u002F{export_job_id}\u002Fresults_dir\u002Fpointpillars.onnx\",\n}\n```\n\n**inference (mandatory data sources):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"inference.checkpoint\": CHECKPOINT,\n}\n```\n\n**prune (mandatory data sources):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"prune.model\": CHECKPOINT,\n}\n```\n\n**retrain (mandatory data sources):**\n```python\n{\n    \"dataset.data_path\": DATA_ROOT,\n    \"dataset.data_info_path\": DATA_INFO,\n    \"train.pruned_model_path\": PRUNED_MODEL,\n}\n```\n\nFor local Docker, `DATA_INFO` must be visible inside every train\u002Fevaluate\u002Fexport\u002Fprune\u002Fretrain container. Use the dataset_convert job from the same results root, or mount\u002Fcopy the converted `results_dir\u002Fdata_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 `\u002Fresults` and the conversion artifacts live under host `scratch\u002Fresults\u002F\u003Cjob_id>\u002Fresults_dir\u002Fdata_info`, the direct-job container path is `\u002Fresults\u002Fresults\u002F\u003Cjob_id>\u002Fresults_dir\u002Fdata_info`. Do not reuse a `\u002Fresults\u002F\u003Cjob_id>\u002F...` path from another run root unless that folder is mounted into the current job.\n\nFor 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.\n## Eval Dataset\n\nOptional. Validation data (val.tar.gz) is separate from training. Used for mAP evaluation.\n\n## Important Parameters\n\n- **train.num_epochs**: Default 80 (much higher than other TAO models). PointPillars needs more epochs for convergence on 3D detection.\n- **train.lr**: Learning rate. Default 0.003 (adam_onecycle scheduler).\n- **dataset.class_names**: List of 3D object classes. Default 7 classes (KITTI-style). Modify to match your dataset.\n- **dataset.data_path**: Path to point cloud data directory.\n- **dataset.data_info_path**: Path to data info files from dataset_convert step.\n- **dataset.point_cloud_range**: Spatial extent of the point cloud to consider. Must match your sensor configuration.\n- **model.dense_head.anchor_generator_config**: Anchor configurations per class. Must be tuned for your object sizes and the point cloud range.\n\n## Multi-GPU \u002F Multi-Node\n\n**Launch method:** `torchrun` (LIGHTNING_EXCLUDED_NETWORK). Uses PyTorch native `DistributedDataParallel` (NOT Lightning Trainer).\n\n| Spec Key | Description | Default |\n|----------|-------------|---------|\n| `train.num_gpus` | Number of GPUs per node | 1 |\n| `train.gpu_ids` | GPU device indices | [0] |\n| `train.num_nodes` | Number of nodes | 1 |\n\n- `CUDA_VISIBLE_DEVICES` is explicitly set from `TAO_VISIBLE_DEVICES`\n- Uses `nn.parallel.DistributedDataParallel` directly (not Lightning strategy)\n- `NODE_RANK` is copied to `RANK` if `RANK` is unset\n\n**Multi-node env vars** (set by orchestrator):\n\n| Variable | Purpose |\n|----------|---------|\n| `WORLD_SIZE` | Number of nodes |\n| `NODE_RANK` | This node's rank |\n| `MASTER_ADDR` | Rank-0 node IP |\n| `MASTER_PORT` | Rank-0 port (default 29500) |\n| `NUM_GPU_PER_NODE` | GPUs per node |\n\n## Hardware\n\nMinimum 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\u002FO for large point cloud datasets.\n\n## Error Patterns\n\n**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 `\u002Fresults\u002F\u003Cold_job_id>\u002F...` path from a different results root.\n\n**Point cloud range mismatch**: If point_cloud_range does not match the actual sensor data extent, detections will be poor or empty.\n\n**Epoch numbering**: PointPillars checkpoint epoch numbers may be offset by 1 from status.json reported epochs.\n\n**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\u002Fjob 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.\n\n**Prune\u002Fretrain 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.\n\n**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\u002Fstatus.json` and the expected artifact before marking an action as passed.\n\n**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 `\u002Fopt\u002Fnvidia\u002Feval` and then still print the generic PASS footer. Treat that as a failed action unless the expected result directory and status\u002Fartifact files exist.\n\n## Spec Param \u002F Parent Model Inference\n\nModel-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.\n\nInference mappings from TAO Core `pointpillars.config.json`:\n\n| Action | Spec Field | Inference Function | Meaning |\n|---|---|---|---|\n| dataset_convert | `results_dir` | `output_dir` | current job results directory |\n| evaluate | `evaluate.checkpoint` | `parent_model` | model file inferred from the parent job results folder |\n| evaluate | `key` | `key` | encryption key |\n| evaluate | `results_dir` | `output_dir` | current job results directory |\n| export | `export.checkpoint` | `parent_model` | model file inferred from the parent job results folder |\n| export | `export.onnx_file` | `create_onnx_file` | output ONNX path |\n| export | `export.save_engine` | `create_engine_file` | output TensorRT engine path |\n| export | `key` | `key` | encryption key |\n| export | `results_dir` | `output_dir` | current job results directory |\n| inference | `inference.checkpoint` | `parent_model` | model file inferred from the parent job results folder |\n| inference | `inference.trt_engine` | `parent_model` | model file inferred from the parent job results folder |\n| inference | `key` | `key` | encryption key |\n| inference | `results_dir` | `output_dir` | current job results directory |\n| prune | `key` | `key` | encryption key |\n| prune | `prune.model` | `parent_model` | model file inferred from the parent job results folder |\n| prune | `results_dir` | `output_dir` | current job results directory |\n| retrain | `key` | `key` | encryption key |\n| retrain | `results_dir` | `output_dir` | current job results directory |\n| retrain | `train.pruned_model_path` | `parent_model` | model file inferred from the parent job results folder |\n| train | `key` | `key` | encryption key |\n| train | `model.pretrained_model_path` | `ptm_if_no_resume_model` | PTM when no resume checkpoint exists |\n| train | `results_dir` | `output_dir` | current job results directory |\n| train | `train.resume_training_checkpoint_path` | `resume_model` | model file inferred from the current job results folder |\n\nFor `parent_model` or `parent_model_folder`, pass the upstream train\u002Fexport\u002FAutoML 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.\n\n## Deployment\n\n- [tao-deploy-pointpillars](references\u002Ftao-deploy-pointpillars.md)\n",{"name":5,"tags":24,"license":15,"metadata":29,"description":7,"allowed-tools":32,"compatibility":33},[25,26,27,28],"point","cloud","3d","detection",{"author":30,"version":31},"NVIDIA Corporation","0.1.0","Read Bash","Requires docker + nvidia-container-toolkit.","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fnvidia-skills\u002Ftao-train-pointpillars\u002Fskills\u002Ftao-train-pointpillars",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill tao-train-pointpillars",{"tool":48,"command":49},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill tao-train-pointpillars",{"tool":51,"command":52},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill tao-train-pointpillars","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Ftao-train-pointpillars\u002Fskills\u002Ftao-train-pointpillars\u002FSKILL.md",true,[],[57,65,70,77,82,89],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":66,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":78,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":90,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]