tao-train-mask-auto-encoder

bởi nvidia

Bộ mã hóa tự động có mặt nạ (MAE) dùng cho tiền huấn luyện tự giám sát và tinh chỉnh. Che các mảng ngẫu nhiên và tái tạo chúng để học biểu diễn thị giác; hỗ trợ…

npx skills add https://github.com/nvidia/skills --skill tao-train-mask-auto-encoder

MAE

Standalone install? If this session was not initialized by the TAO skill bank plugin, run the tao-setup skill first (host preflight, credentials, cross-skill discovery).

MAE (Masked Autoencoder) for self-supervised pretraining and fine-tuning. Masks random patches and reconstructs them to learn visual representations. Supports pretrain and finetune stages.

Set train.pretrained_model_path for pretrained MAE weights when fine-tuning.

For TAO Deploy TensorRT actions (gen_trt_engine), read references/tao-deploy-mask-auto-encoder.md first. Deploy spec templates live in this skill's references/ folder with the spec_template_deploy_*.yaml prefix.

The parent PyTorch mae CLI supports train, evaluate, inference, and export. Build TensorRT engines through the deploy workflow, not the model skill.

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: image_classification
  • Formats: ssl
  • Accepted dataset intents: training, evaluation, testing
  • Monitoring metric: train_loss

Per-Action Dataset Requirements

ActionSpec KeySourceFilesList?
traindataset.train_data_sourcestrain_datasetsimages_train.tar.gzNo
traindataset.val_data_sourceseval_datasetimages_val.tar.gzNo
evaluatedataset.val_data_sourceseval_datasetimages_val.tar.gzNo
inferencedataset.test_data_sourcesinference_datasetimages_test.tar.gzNo

For SDK/app job inputs, the images_*.tar.gz archives are uploaded as the action inputs. For direct local Docker runs against host-mounted data, extract the archives first and point dataset.train_data_sources, dataset.val_data_sources, and dataset.test_data_sources at the extracted images_train, images_val, and images_test folders. Passing a local tar path directly to the MAE CLI can produce a zero-sample dataloader because the local dataloader does not unpack that archive path.

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.

S3_TRAIN = "s3://bucket/data/train"
S3_EVAL = "s3://bucket/data/eval"

train (mandatory data sources):

{
    "dataset.train_data_sources": f"{S3_TRAIN}/images_train.tar.gz",
    "dataset.val_data_sources": f"{S3_EVAL}/images_val.tar.gz",
    "train.num_epochs": 10,
    "train.optim.lr": 2e-4,
}

evaluate (mandatory data sources):

{
    "dataset.val_data_sources": f"{S3_EVAL}/images_val.tar.gz",
    "evaluate.checkpoint": "<selected train/AutoML checkpoint>",
    "train.stage": "finetune",
}

inference (mandatory data sources):

{
    "dataset.test_data_sources": f"{S3_EVAL}/images_test.tar.gz",
    "inference.checkpoint": "<selected train/AutoML checkpoint>",
    "train.stage": "finetune",
}

Eval Dataset

Optional. Pretraining does not need eval data. Fine-tuning optionally uses val set.

Important Parameters

  • train.stage: Training stage. Options: pretrain, finetune. Pretrain learns representations via masking. Finetune adds a classification head.
  • model.arch: Architecture. Default convnextv2_base. For local smoke AutoML, use convnextv2_atto rather than unsupported names such as vit_tiny_patch16. Supported families include vit_base_patch16 and larger ViTs, ConvNeXtV2 atto/femto/pico/nano/tiny/base/large/huge, and Hiera tiny/small/base/large/huge.
  • model.num_classes: Number of classes for fine-tuning. Default 1000 (ImageNet). Only relevant in finetune stage.
  • model.mask_ratio: Fraction of patches to mask during pretraining. Typically 0.75.
  • model.norm_pix_loss: Whether to normalize pixel values in reconstruction loss.
  • dataset.augmentation.input_size: Keep the local smoke profile at 224 for ConvNeXtV2 MAE. Reducing to 112 can make the MAE mask grid incompatible with feature-map dimensions.
  • MAE does not expose a dataset.workers spec field. Do not add it to smoke-test overrides; Hydra rejects unknown dataset keys before training.
  • train.optim.lr: Learning rate. Default 2e-4.
  • dataset.augmentation: Augmentation settings including mixup, cutmix for fine-tuning.

Multi-GPU / Multi-Node

Launch method: Lightning-managed (single python process, Lightning spawns workers).

Spec KeyDescriptionDefault
train.num_gpusNumber of GPUs1
train.gpu_idsGPU device indices[0]
train.num_nodesNumber of nodes1
train.distributed_strategyddp or fsdpddp
  • ddp uses find_unused_parameters=True
  • fsdp forces FP16
  • Multi-GPU strongly recommended for pretraining (large batch sizes needed)

Multi-node env vars (set by orchestrator): WORLD_SIZE, NODE_RANK, MASTER_ADDR, MASTER_PORT, NUM_GPU_PER_NODE.

Hardware

Minimum 2 GPU(s), recommended 8 GPU(s). 24GB+ (A100 recommended) VRAM per GPU. MAE pretraining benefits from large batch sizes across many GPUs. Fine-tuning is more modest in resource requirements.

Error Patterns

Stage mismatch: Ensure train.stage matches your intent (pretrain vs finetune). Fine-tuning without a pretrained_model_path trains from scratch.

Inference with pretrain checkpoints: The MAE predict dataloader raises NotImplementedError for train.stage: pretrain. Use a finetune checkpoint for inference and classification-style evaluation, or restrict a pretrain-only run to train/evaluate/export.

num_classes mismatch (finetune only): Ensure model.num_classes matches your dataset class count when fine-tuning.

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 mae.config.json:

ActionSpec FieldInference FunctionMeaning
evaluateencryption_keykeyencryption key
evaluateevaluate.checkpointparent_modelmodel file inferred from the parent job results folder
evaluateevaluate.trt_engineparent_modelmodel file inferred from the parent job results folder
evaluateresults_diroutput_dircurrent job results directory
exportencryption_keykeyencryption key
exportexport.checkpointparent_modelmodel file inferred from the parent job results folder
exportexport.onnx_filecreate_onnx_fileoutput ONNX path
exportresults_diroutput_dircurrent job results directory
inferenceencryption_keykeyencryption key
inferenceinference.checkpointparent_modelmodel file inferred from the parent job results folder
inferenceinference.trt_engineparent_modelmodel file inferred from the parent job results folder
inferenceresults_diroutput_dircurrent job results directory
trainencryption_keykeyencryption key
trainresults_diroutput_dircurrent job results directory
traintrain.pretrained_model_pathptm_if_no_resume_modelPTM when no resume checkpoint exists
traintrain.resume_training_checkpoint_pathresume_modelmodel 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.

When resolving checkpoints outside the SDK resolver, select the intended epoch/step artifact exactly, for example model_epoch_000_step_00099.pth. Use the convnextv2_atto_latest.pth or other latest symlink only when latest is explicitly requested. Carry train.stage, model.arch, model.num_classes, and export input size forward into evaluate, inference, export, and deploy specs so the checkpoint and ONNX/engine shapes match.

Deployment

Thêm skills từ nvidia

compileiq-debug
nvidia
Sử dụng khi có điều gì đó không ổn: Search() bị treo, tất cả các đánh giá đều trả về INVALID_SCORE, điểm số không cải thiện, mọi cấu hình đều trả về cùng một số, lỗi ptxas…
create-github-pr
nvidia
Tạo pull request GitHub bằng cách sử dụng gh CLI. Sử dụng khi người dùng muốn tạo PR mới, gửi mã để xem xét, hoặc mở pull request. Từ khóa kích hoạt -…
nemoclaw-maintainer-cross-issue-sweep
nvidia
Quét các vấn đề đang mở khác để tìm những vấn đề mà một PR nhất định có thể sửa hoặc vô tình làm hỏng. Đưa ra các cơ hội sửa lỗi liền kề và rủi ro mâu thuẫn với file:dòng…
fhir-basics
nvidia
Dạy các tác nhân cách hoạt động của API FHIR R4, những tài nguyên có sẵn, cách truy vấn chúng với tham số tìm kiếm, và cách phân tích chính xác tất cả các định dạng phản hồi…
compileiq-validate-result
nvidia
Sử dụng SAU KHI tìm kiếm hoàn tất và TRƯỚC KHI yêu cầu tăng tốc hoặc gửi ACF. Tải tệp CSV dump_results, trích xuất các ứng viên top-K (đơn mục tiêu)…
changelog-audit
nvidia
Kiểm tra Warp CHANGELOG.md trước khi phát hành: khôi phục các mục bị mất, sắp xếp theo tác động người dùng, tinh chỉnh ngôn ngữ mục, xuống dòng và (chế độ nhánh phát hành) so sánh bump…
maintain-dynamic-plugins
nvidia
Duy trì các bộ nạp plugin động NeMo Relay, tệp kê khai, SDK gốc Rust, giao thức worker gRPC, SDK worker Python, tài liệu, kiểm thử và phạm vi quy trình phát hành
dgx-diagnose
nvidia
Chẩn đoán các sự cố thường gặp của DGX Station GB300 — lỗi CUDA, nhắm sai GPU, lỗi container vLLM/SGLang, vấn đề trạng thái MIG, lỗi NVLink/Fabric Manager,…