BEVFusion
BEVFusion for multi-sensor 3D object detection. Fuses LiDAR point clouds and camera images in bird's-eye-view (BEV) space. Used in autonomous driving for robust 3D perception.
Set pretrained backbone paths for Swin image backbone.
Dataclass Schemas
Generated TAO Core schemas are packaged in
schemas/<action>.schema.json
, with
listing available actions. Each generated schema also emits
references/spec_template_<action>.yaml
from the schema top-level
field. AutoML enablement is declared at the model layer in
references/skill_info.yaml
via
. Runnable AutoML still requires
schemas/train.schema.json
and
references/spec_template_train.yaml
to exist and parse. Use the packaged train schema for
automl_default_parameters
,
automl_disabled_parameters
, defaults, min/max bounds, enums, option weights, math conditions, dependencies, and popular parameters. Do not expect
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
value or the user's workflow request. Treat phrases like "turn off AutoML", "disable AutoML", "no HPO", or "plain training" as
for this run only; otherwise default to
. When
,
, 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
. Preserve workflow/application overrides for datasets, specs, output directories, GPU/platform settings, parent checkpoints, and
. Use direct model training only when
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
,
,
, and deploy flows stay in this model skill. The per-run
override does not change model metadata.
Training Requirements
- Dataset type: bevfusion
- Formats: default
- Monitoring metric: AP11
Per-Action Dataset Requirements
| Action | Spec Key | Source | Files | List? |
|---|
| dataset_convert | root_dir | id | | No |
| evaluate | dataset.test_dataset | train_datasets | ann_file: results/{dataset_convert_job_id}/kitti_person_infos_val.pkl | No |
| inference | dataset.root_dir | train_datasets | | No |
| inference | dataset.test_dataset | train_datasets | ann_file: results/{dataset_convert_job_id}/kitti_person_infos_val.pkl | No |
| train | dataset.train_dataset | train_datasets | ann_file: results/{dataset_convert_job_id}/kitti_person_infos_train.pkl | No |
| train | dataset.val_dataset | train_datasets | ann_file: results/{dataset_convert_job_id}/kitti_person_infos_val.pkl | No |
| train | dataset.test_dataset | train_datasets | ann_file: results/{dataset_convert_job_id}/kitti_person_infos_val.pkl | 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
.
python
S3_TRAIN = "s3://bucket/data/train"
train (mandatory data sources):
python
{
"train.num_epochs": 30,
"train.checkpoint_interval": 10,
"train.validation_interval": 10,
"train.num_gpus": 1,
"dataset.train_dataset": {"ann_file": f"{S3_TRAIN}/results/{dataset_convert_job_id}/kitti_person_infos_train.pkl"},
"dataset.val_dataset": {"ann_file": f"{S3_TRAIN}/results/{dataset_convert_job_id}/kitti_person_infos_val.pkl"},
"dataset.test_dataset": {"ann_file": f"{S3_TRAIN}/results/{dataset_convert_job_id}/kitti_person_infos_val.pkl"},
}
evaluate (mandatory data sources):
python
{
"dataset.test_dataset": {"ann_file": f"{S3_TRAIN}/results/{dataset_convert_job_id}/kitti_person_infos_val.pkl"},
}
inference (mandatory data sources):
python
{
"dataset.root_dir": f"{S3_TRAIN}",
"dataset.test_dataset": {"ann_file": f"{S3_TRAIN}/results/{dataset_convert_job_id}/kitti_person_infos_val.pkl"},
}
Eval Dataset
Optional. Val dataset split is configured via ann_file in dataset config.
Important Parameters
- dataset.classes: List of detection classes. Default ["person"]. Must match the annotation categories.
- dataset.type: Dataset type. Options: KittiPersonDataset, TAO3DSyntheticDataset, TAO3DDataset.
- dataset.root_dir: Root directory of the KITTI-style dataset.
- dataset.box_type_3d: 3D box coordinate frame. Options: lidar, camera. Default lidar.
- train.optimizer.lr: Learning rate. Default 2e-4 (AdamW). Use AmpOptimWrapper for mixed precision via optimizer.wrapper_type.
- input_modality: Dict controlling sensor modalities. Keys: use_lidar (True), use_camera (True), use_radar (False), use_map (False).
- model.img_backbone: Image backbone. Default mmdet.SwinTransformer (Swin-Tiny). embed_dims=96, depths=[2,2,6,2].
- model.view_transform.type: View transform for BEV projection. Options: DepthLSSTransform, LSSTransform. Default DepthLSSTransform.
- model.point_cloud_range: Spatial extent of LiDAR. Default [0,-40,-3,70.4,40,1].
- model.voxel_size: Voxel dimensions. Default [0.05, 0.05, 0.1].
- dataset.train_dataset.batch_size: Per-GPU batch size. Default 4.
Multi-GPU / Multi-Node
Launch method: (LIGHTNING_EXCLUDED_NETWORK). The entrypoint runs
torchrun --nnodes=N --nproc-per-node=M train.py
, NOT plain
.
| Spec Key | Description | Default |
|---|
| Number of GPUs per node | 1 |
| GPU device indices | [0] |
| Number of nodes | 1 |
- is explicitly set from
- BEVFusion uses mmdet3d-based distributed training, not Lightning DDP
- is copied to if is unset
Multi-node env vars (set by orchestrator):
| Variable | Purpose |
|---|
| Number of nodes |
| This node's rank |
| Rank-0 node IP |
| Rank-0 port (default 29500) |
| GPUs per node |
Hardware
Minimum 2 GPU(s), recommended 4 GPU(s). 24GB+ (A100 recommended) VRAM per GPU. BEVFusion is memory-intensive due to multi-sensor fusion. A100 GPUs strongly recommended. Multi-GPU training expected.
Error Patterns
dataset_convert required: Run dataset_convert before training to produce info pickle files.
Missing modality data: Ensure both camera images and LiDAR point clouds are present if using multi-modal fusion.
Epoch numbering: BEVFusion checkpoint epoch numbers may not follow standard zero-padded format.
Spec Param / Parent Model Inference
Model-specific inference mappings belong in this MD file, not in
. Generated runners should read this section and apply the mappings with SDK helpers before
. This mirrors the old microservices
flow.
Inference mappings from TAO Core
:
| Action | Spec Field | Inference Function | Meaning |
|---|
| dataset_convert | | | current job results directory |
| evaluate | | | encryption key |
| evaluate | | | model file inferred from the parent job results folder |
| evaluate | | | current job results directory |
| inference | | | encryption key |
| inference | | | model file inferred from the parent job results folder |
| inference | | | current job results directory |
| train | | | encryption key |
| train | | | current job results directory |
| train | train.pretrained_checkpoint
| | PTM when no resume checkpoint exists |
| train | train.resume_training_checkpoint_path
| | model file inferred from the current job results folder |
For
or
, pass the upstream train/export/AutoML child job id as
. 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
and do not patch generated runner scripts to guess checkpoint paths.