npx skills add nvidia/skills --skill tao-train-action-recognition
promptingcompany/nv-skills
tao-train-action-recognition
Action recognition from video sequences. Supports RGB, optical flow, and joint (multi-stream) input types for classifying temporal actions in video clips. Use when training, evaluating, exporting, or running inference on a TAO action-recognition model. Trigger phrases include "train action recognition", "video action classification", "RGB + optical flow action model", "TAO ActionRecognition".
Installation
npx skills add promptingcompany/nv-skills --skill tao-train-action-recognition
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Action recognition from video sequences. Supports RGB, optical flow, and joint (multi-stream) i…
1.6K installsMetric-learning recognition (ml-recog) for fine-grained visual recognition. Learns embeddings f…
1.5K installs>- Use this skill whenever the user wants text extracted from images, photos, scans, screenshot…
4K installsTranscribe speech to text using Apple's Speech framework.
3.2K installs>- Use this skill whenever the user wants text extracted from images, photos, scans, screenshot…
562 installsSpot patterns appearing in 3+ domains to find universal principles
426 installsAlso in this package
Other skills from promptingcompany/nv-skills · top by installs.
npx skills add promptingcompany/nv-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
Read BashMore metadata
- version
- 0.1.0
- author
- NVIDIA Corporation
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md9,554 B -
docs
SUMMARY.md431 B
History
- First seen on skills.sh
- First recorded snapshot · 39 installs
SKILL.md
Action Recognition
Action recognition from video sequences. Supports RGB, optical flow, and joint (multi-stream) input types for classifying temporal actions in video clips.
Set model.pretrainedmodelpath for pretrained backbone weights.
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/spectemplate<action>.yaml from the schema top-level default field. AutoML enablement is declared at the model layer in references/skillinfo.yaml via automlenabled. Runnable AutoML still requires schemas/train.schema.json and references/spectemplatetrain.yaml to exist and parse. Use the packaged train schema for automldefaultparameters, automldisabledparameters, 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/skillinfo.yaml and resolve the run override from either an explicit automlpolicy value or the user's workflow request. Use automlpolicy: 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 automlpolicy: off for this run only. When automlpolicy: on, automlenabled: true, and both schemas/train.schema.json and references/spectemplatetrain.yaml are packaged, route the train action through tao-skill-bank:tao-run-automl by default with this model's skilldir. Preserve workflow/application overrides for datasets, specs, output directories, GPU/platform settings, parent checkpoints, and automlpolicy. 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: action_recognition
- Formats: default
- Monitoring metric: val_loss
Per-Action Dataset Requirements
| Action | Spec Key | Source | Files | List? |
|---|---|---|---|---|
| evaluate | evaluate.testdatasetdir | train_datasets | test/ extracted from test.tar.gz | No |
| inference | inference.inferencedatasetdir | train_datasets | test/smile/ extracted from test/smile.tar.gz | No |
| train | dataset.traindatasetdir | train_datasets | train/ extracted from train.tar.gz | No |
| train | dataset.valdatasetdir | train_datasets | test/ extracted from test.tar.gz | 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.
LOCAL_DATA = "/workspace/data/extracted"
If the source dataset is provided as the TAO sample archives train.tar.gz, test.tar.gz, or test/smile.tar.gz, download and extract them before launching the TAO container. The action-recognition entrypoints expect directory paths and fail with NotADirectoryError when these spec keys point at .tar.gz files.
train (mandatory data sources):
{
"train.num_epochs": 30,
"train.checkpoint_interval": 10,
"train.validation_interval": 10,
"train.num_gpus": 1,
"dataset.label_map": {
"catch": 0,
"smile": 1
},
"dataset.batch_size": 2,
"dataset.train_dataset_dir": f"{LOCAL_DATA}/train",
"dataset.val_dataset_dir": f"{LOCAL_DATA}/test",
}
evaluate (mandatory data sources):
{
"dataset.label_map": {
"catch": 0,
"smile": 1
},
"evaluate.test_dataset_dir": f"{LOCAL_DATA}/test",
}
inference (mandatory data sources):
{
"dataset.label_map": {
"catch": 0,
"smile": 1
},
"inference.inference_dataset_dir": f"{LOCAL_DATA}/smile_infer/smile",
}
export (mandatory checkpoint + output path):
{
"export.checkpoint": "<selected train checkpoint>",
"export.onnx_file": "<results_dir>/action_recognition.onnx",
}
For direct local-docker chaining without the SDK resolver, select the concrete checkpoint produced by training, for example modelepoch000step00005.pth, and pass that exact file to evaluate, inference, and export. Do not use the armodellatest.pth symlink unless the user explicitly requests latest-checkpoint behavior. For resume training, set train.resumetrainingcheckpoint_path to the exact epoch/step checkpoint being resumed.
Eval Dataset
Optional. Test dataset may be distributed as test.tar.gz separate from training; extract it and point the spec to the extracted test/ directory. TAO training emits valloss as the validation scalar for the packaged sample data; use valloss with minimize direction for AutoML selection unless a custom evaluator supplies an accuracy metric.
Important Parameters
- model.model_type: Input type: rgb, of (optical flow), or joint (multi-stream).
- model.backbone: Default resnet_18. Used as the spatial feature extractor.
- dataset.label_map: Dictionary mapping class names to indices.
- model.rgbseqlength: Number of frames per clip for RGB input.
- model.ofseqlength: Number of frames for optical flow input.
- train.optim.lr: Learning rate. Default 5e-4.
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] |
- Strategy:
auto(Lightning picks best strategy automatically) - No explicit
numnodesordistributedstrategyconfig — single-node oriented
Hardware
Minimum 1 GPU(s), recommended 2 GPU(s). 16GB+ VRAM per GPU. Memory depends on sequence length and input resolution. batch_size=2 is conservative for video data.
Error Patterns
Sequence length mismatch: Ensure video clips have enough frames for the configured rgbseqlength or ofseqlength.
Evaluate/inference missing label map: Downstream actions rebuild the ActionRecognitionModel before loading the checkpoint, so they need the same dataset.label_map used during training. Include it with every evaluate or inference spec; otherwise model construction fails before the checkpoint can be validated.
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 createjob(). This mirrors the old microservices inferparams.py flow.
Inference mappings from TAO Core action_recognition.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 | 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 |
createonnxfile |
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 | results_dir |
output_dir |
current job results directory |
| train | encryption_key |
key |
encryption key |
| train | model.ofpretrainedmodel_path |
ptmifnoresumemodel |
PTM when no resume checkpoint exists |
| train | model.rgbpretrainedmodel_path |
ptmifnoresumemodel |
PTM when no resume checkpoint exists |
| train | results_dir |
output_dir |
current job results directory |
| train | train.resumetrainingcheckpoint_path |
resume_model |
model file inferred from the current job results folder |
For parentmodel or parentmodelfolder, pass the upstream train/export/AutoML child job id as parentjob_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.