tao-train-segformer
SegFormer for semantic segmentation. Lightweight transformer-based architecture with hierarchical feature
- 0
- Installs
- —
- Rating
- —
- Success rate
- 22
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 2de1035f672b3bba… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
SegFormer
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).
SegFormer for semantic segmentation. Lightweight transformer-based architecture with hierarchical feature extraction. Efficient for real-time segmentation tasks.
Set model.backbone.pretrained_backbone_path for backbone weights.
For TAO Deploy TensorRT actions (gen_trt_engine, TensorRT evaluate, and TensorRT inference), read references/tao-deploy-segformer.md first. Deploy spec templates live in this skill's references/ folder with the spec_template_deploy_*.yaml prefix.
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.
Supported Actions
The packaged SegFormer PyT CLI supports train, evaluate, export, inference, quantize, and default_specs. This model skill exposes train, evaluate, export, inference, and quantize; resume/retrain is performed through train with train.resume_training_checkpoint_path.
The parent PyT CLI does not expose gen_trt_engine. Use models/segformer/deploy for TensorRT engine generation, TensorRT evaluation, and TensorRT inference.
Training Requirements
- Dataset type: segmentation
- Formats: unet
- AutoML training metric:
val_miou(maximize). - Standalone evaluation metric:
test_miou. Use the train-statusval_mioufor AutoML ranking and the evaluator'stest_miouonly for checkpoint verification.
Per-Action Dataset Requirements
| Action | Spec Key | Source | Files | List? |
|---|---|---|---|---|
| evaluate | dataset.segment.root_dir | eval_dataset | extracted root containing images/<split> and masks/<split> | No |
| export | dataset.segment.root_dir | train_datasets | extracted root containing images/<split> and masks/<split> | No |
| inference | dataset.segment.root_dir | inference_dataset | extracted root containing images/<split> and masks/<split> | No |
| quantize | dataset.segment.root_dir | train_datasets | extracted root containing images/<split> and masks/<split> | No |
| quantize | dataset.segment.quant_calibration_dataset.images_dir | calibration_dataset | extracted image directory | No |
| train | dataset.segment.root_dir | train_datasets | extracted root containing images/<split> and masks/<split> | 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.
SEG_TRAIN_ROOT = "/data/segformer/train"
SEG_EVAL_ROOT = "/data/segformer/eval"
SEG_INFER_ROOT = "/data/segformer/infer"
CAL_IMAGES = f"{SEG_TRAIN_ROOT}/images/train"
train (mandatory data sources):
{
"train.num_gpus": 1,
"train.num_epochs": 10,
"train.checkpoint_interval": 10,
"train.validation_interval": 10,
"dataset.segment.batch_size": 4,
"dataset.segment.root_dir": SEG_TRAIN_ROOT,
}
evaluate (mandatory data sources):
{
"evaluate.batch_size": 4,
"dataset.segment.root_dir": SEG_EVAL_ROOT,
"evaluate.checkpoint": CHECKPOINT,
}
inference (mandatory data sources):
{
"dataset.segment.batch_size": 1,
"dataset.segment.root_dir": SEG_INFER_ROOT,
"inference.checkpoint": CHECKPOINT,
}
export (mandatory data sources):
{
"dataset.segment.root_dir": SEG_TRAIN_ROOT,
"export.checkpoint": CHECKPOINT,
"export.input_height": 256,
"export.input_width": 256,
"export.onnx_file": ONNX_FILE,
}
quantize (mandatory data sources):
{
"dataset.segment.root_dir": SEG_TRAIN_ROOT,
"dataset.segment.quant_calibration_dataset.images_dir": CAL_IMAGES,
"quantize.model_path": CHECKPOINT,
}
If the source dataset is delivered as separate images/*.tar.gz and
masks/*.tar.gz archives, extract them before launch so root_dir contains
directories such as images/train, images/val, images/test, masks/train,
and masks/val. Do not point dataset.segment.root_dir at an archive staging
folder that still contains only tarballs.
Eval Dataset
Optional. Validation data is typically part of the root_dir structure.
Important Parameters
- dataset.segment.num_classes: Number of segmentation classes. Default 2 (binary). Must match the number of classes in your mask annotations.
- model.backbone.type: Default fan_small_12_p4_hybrid. Supported includes FAN variants, SegFormer MIT variants, and others.
- dataset.segment.root_dir: Root directory of the segmentation dataset.
- dataset.segment.img_size: Input image size. Default 256. Increase for finer segmentation at the cost of memory.
- train.optim.lr: Learning rate. Default 6e-5.
- model.freeze_backbone: Whether to freeze the backbone during training. Useful for fine-tuning with limited data.
- dataset.segment.batch_size: Per-GPU batch size. Default 8.
- dataset.segment.label_transform: Use the string
"None"when no label transform is desired. Do not set this to JSON/YAML null; strict schema merge treats the field as a string enum. - dataset.segment.palette: For grayscale masks, use one integer per RGB
entry, for example
rgb: [85]. Preserve the dataset's actual label ids and class names rather than normalizing them unless the user explicitly asks for a conversion.
Multi-GPU / Multi-Node
Launch method: Lightning-managed (single python process, Lightning spawns workers).
| Spec Key | Description | Default |
|---|---|---|
train.num_gpus | Number of GPUs | 1 |
train.gpu_ids | GPU device indices | [0] |
train.num_nodes | Number of nodes | 1 |
train.sync_batchnorm | Sync BN across GPUs | configurable |
train.use_distributed_sampler | Use distributed sampler | configurable |
- Multi-GPU strategy:
ddp_find_unused_parameters_true - No fsdp support
Multi-node env vars (set by orchestrator): WORLD_SIZE, NODE_RANK, MASTER_ADDR, MASTER_PORT, NUM_GPU_PER_NODE.
Hardware
Minimum 1 GPU(s), recommended 2 GPU(s). 16GB+ (V100 or A100) VRAM per GPU. SegFormer is relatively lightweight. Default img_size=256 is memory-friendly. Increase img_size for higher resolution at the cost of memory and speed.
Error Patterns
CUDA out of memory: Reduce batch_size or img_size. SegFormer memory scales quadratically with image size.
num_classes mismatch: Ensure dataset.segment.num_classes matches the actual number of classes in your mask annotations.
TensorBoard unsupported for segmentation training: Keep train.tensorboard.enabled: false. The SegFormer training entrypoint asserts that TensorBoard visualization is not supported for segmentation, so do not enable TensorBoard just to extract AutoML metrics; use log parsing or a post-train evaluator instead.
AutoML metric extraction: SegFormer train status files report val_miou alongside val_loss, val_acc, and other validation KPIs. Default AutoML train launches must optimize val_miou with direction: maximize; do not optimize val_loss for default model invocations.
For AutoML or long segmentation sweeps, read val_miou from
results_dir/train/status.json first. If the wrapper reports a terminal
failure but the structured status file reached the configured training budget
and contains finite val_miou, report the recovered metric with the wrapper
failure noted instead of discarding the measurement.
For high-resolution custom segmentation targets, keep dataset paths as per-run
inputs. Do not add customer/user-specific roots to this reusable skill. When the
user asks for a fixed full-budget search, remember that bracket algorithms
(asha, bohb, dehb, hyperband, hyperband_es, pbt) may intentionally
lower train.num_epochs for some recommendations; use Bayesian/BFBO or lock the
budget if every recommendation must run the full epoch count.
Checkpoint handoff: For evaluate/export/inference/quantize/resume, use the checkpoint resolver on the best AutoML child job's results_dir/train/ folder and select the action-appropriate model_epoch_*.pth checkpoint, such as model_epoch_000_step_00010.pth. SegFormer may also write segformer_model_latest.pth, but that should only be used when a caller explicitly requests latest. Preserve dataset.segment.num_classes, dataset.segment.img_size, and dataset.segment.root_dir overrides for downstream actions.
Resume/retrain checkpoint: Resume uses train.resume_training_checkpoint_path.
Pass the exact resolved checkpoint from the previous train output, not a guessed
model.pth path. A resumed one-epoch run should produce the next checkpoint in
the new results directory, for example model_epoch_001_step_00020.pth.
Export / TensorRT shape alignment: Keep export.input_height and
export.input_width aligned with dataset.segment.img_size unless the trained
model and deploy specs have been validated at another resolution. The packaged
fresh-install path is validated at 256x256, matching the default SegFormer
dataset and deploy templates.
Parent segformer gen_trt_engine rejected by the PyT CLI: In the validated 7.0.0 PyT container, segformer gen_trt_engine is not a valid parent-model subtask. Use the SegFormer deploy workflow (references/tao-deploy-segformer.md) for TensorRT engine generation, TensorRT evaluation, and TensorRT inference.
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 segformer.config.json:
| Action | Spec Field | Inference Function | Meaning |
|---|---|---|---|
| evaluate | encryption_key | key | encryption key |
| evaluate | evaluate.checkpoint | parent_model | model file inferred from the parent job results folder |
| evaluate | evaluate.trt_engine | parent_model | model file inferred from the parent job results folder |
| evaluate | results_dir | output_dir | current job results directory |
| export | encryption_key | key | encryption key |
| 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 | results_dir | output_dir | current job results directory |
| inference | encryption_key | key | encryption key |
| 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 | results_dir | output_dir | current job results directory |
| quantize | encryption_key | key | encryption key |
| quantize | quantize.model_path | parent_model | model file inferred from the parent job results folder |
| quantize | results_dir | output_dir | current job results directory |
| train | encryption_key | key | encryption key |
| train | model.backbone.pretrained_backbone_path | ptm_if_no_resume_model | PTM when no resume checkpoint exists |
| train | results_dir | output_dir | current job results directory |
| train | train.pretrained_model_path | ptm_if_no_resume_model | PTM when no resume checkpoint exists |
| 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
22- BENCHMARK.md
0e23a434986.9 KB - SKILL.md
de667087c314.5 KB - config/skillspector-baseline.yaml
8b379b90c3834 B - evals/evals.json
560cb2bdc5776 B - references/skill_info.yaml
64c5c6e8824.4 KB - references/spec_template_deploy_evaluate.yaml
f0c101dba7748 B - references/spec_template_deploy_gen_trt_engine.yaml
9d044e455c1.4 KB - references/spec_template_deploy_inference.yaml
c26f0a2a5b749 B - references/spec_template_evaluate.yaml
cf3013d2432.8 KB - references/spec_template_export.yaml
dd7c1a16452.9 KB - references/spec_template_inference.yaml
b7941eb08a2.8 KB - references/spec_template_quantize.yaml
594b7436b42.6 KB - references/spec_template_train.yaml
594b7436b42.6 KB - references/tao-deploy-segformer.md
de7a4457926.0 KB - references/tao-deploy-segformer.skill_info.yaml
a5cbac16b12.8 KB - schemas/evaluate.schema.json
0486c3595448.4 KB - schemas/export.schema.json
093615d91c49.3 KB - schemas/inference.schema.json
f974157edb48.4 KB - schemas/manifest.json
04377a43ea17.7 KB - schemas/quantize.schema.json
3608cfe32c45.6 KB - schemas/train.schema.json
caf3a10e8645.6 KB - skill-card.md
f142c3c6724.0 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from NVIDIA/skills8
Official NVIDIA-authored guidance for NVIDIA cuDF GPU DataFrames, pandas acceleration, dask-cuDF, ETL, joins, groupby, CSV/Parquet I/O, nullable semantics, and multi-GPU DataFrame workloads.
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
Customize NVIDIA Nemotron Voice Agent's Generic Pipecat example for healthcare appointment, five-field patient intake, or custom tool-calling workflows without a separate backend.
Calibrate a new dataset from live RTSP camera streams via the AutoMagicCalib REST API. Use when the user provides RTSP URLs or asks to calibrate live cameras; VIOS records clips, AMC ingests them, then runs calibration.
Run end-to-end calibration on the shipped sample dataset (sdg_08_2_sample_data_010926.zip) against a running AMC microservice. Use when user says 'test sample dataset', 'run sample calibration', 'verify AMC install', or 'launch and test'.
Calibrates pre-recorded `cam_*.mp4` datasets through the AutoMagicCalib REST API. Use for user-supplied local MP4s; route live RTSP streams to `amc-run-rtsp-calibration`.
Launch AutoMagicCalib microservice and web UI from NGC release images via Docker Compose. Use when user says 'deploy auto calibration', 'launch auto calibration', 'launch AMC', 'start MS+UI', or 'set up auto-magic-calib'. Requires NGC API key.
Related ai-ml skillsscan passed
Prevent AI style drift on legacy projects by scanning the codebase for implicit conventions, resolving conflicts with the operator one at a time, and writing an enforceable .ai-style-rules.md (Golden Files, naming rules, DONTs) plus an optional CLAUDE.md hook. Use when onboarding an AI agent onto a
Pair a remote AI agent with your browser. (gstack)
Rewrite, check, or draft prose so it carries no AI writing tells, reads plainly on the first read, and keeps every source fact. Use when asked to make writing plainer or free of those tells, to check writing for them, or when drafting from supplied content. Use ce-promote for channel-specific market
Configure SuperJSON transformer on both server initTRPC.create({ transformer: superjson }) and every client terminating link (httpBatchLink, httpLink, wsLink, httpSubscriptionLink) to support Date, Map, Set, BigInt over the wire. Transformer must match on both sides. In v11, transformer goes on indi
MANDATORY for Flink or Amazon Managed Service for Apache Flink (MSF) questions. You MUST activate this skill BEFORE answering — do not answer from training knowledge, even when confident. MSF has service-specific constraints (KPU model, prohibited checkpoint and parallelism config in app code, the v
Validates the user's environment for SageMaker AI operations — checks SDK version, AWS region, and execution role. Use when the user says "set up", "getting started", "check my environment", "configure SDK", or as the first step in any plan involving SageMaker/Bedrock training, evaluation, or deploy