mcpField
T
tao-train-action-recognition

tao-train-action-recognition

github.com/promptingcompanyData & databases039 installsUpdated 17w ago
Repository

About tao-train-action-recognition

tao-train-action-recognition is an NVIDIA TAO skill for classifying actions in video sequences. It supports RGB, optical-flow, and joint multi-stream inputs, and includes workflows for training, evaluation, inference, and export.

Key features

  1. 01RGB, optical-flow, and joint inputs
  2. 02Temporal action classification in video clips
  3. 03Training and evaluation
  4. 04Inference and model export
  5. 05AutoML training policy support

Use cases

  1. 01Train a video action classification model
  2. 02Classify video actions from RGB or optical flow
  3. 03Evaluate and export an action recognition model

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/promptingcompany/nv-skills --skill tao-train-action-recognition

After installing, type/tao-train-action-recognitionin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

BENCHMARK.md
skill-card.md
skill.oms.sig
evals/
evals.json
references/
skill_info.yaml
spec_template_evaluate.yaml
spec_template_export.yaml
spec_template_inference.yaml
spec_template_train.yaml
schemas/
evaluate.schema.json
export.schema.json
inference.schema.json
manifest.json
train.schema.json

Details

From the project README

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.pretrained_model_path 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/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 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 ~/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. Treat phrases like "turn off AutoML", "disable AutoML", "no HPO", or "plain training" as automl_policy: off for this run only; otherwise default to auto. When automl_policy: auto, 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: action_recognition
  • Formats: default
  • Monitoring metric: val_acc
Per-Action Dataset Requirements
ActionSpec KeySourceFilesList?
evaluateevaluate.test_dataset_dirtrain_datasetstest.tar.gzNo
inferenceinference.inference_dataset_dirtrain_datasetstest/smile.tar.gzNo
traindataset.train_dataset_dirtrain_datasetstrain.tar.gzNo
traindataset.val_dataset_dirtrain_datasetstest.tar.gzNo
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"

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"{S3_TRAIN}/train.tar.gz",
    "dataset.val_dataset_dir": f"{S3_TRAIN}/test.tar.gz",
}

evaluate (mandatory data sources):

{
    "evaluate.test_dataset_dir": f"{S3_TRAIN}/test.tar.gz",
}

inference (mandatory data sources):

{
    "inference.inference_dataset_dir": f"{S3_TRAIN}/test/smile.tar.gz",
}

Eval Dataset

Optional. Test dataset is provided as test.tar.gz separate from training.

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.rgb_seq_length: Number of frames per clip for RGB input.
  • model.of_seq_length: 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 KeyDescriptionDefault
train.num_gpusNumber of GPUs1
train.gpu_idsGPU device indices[0]
  • Strategy: auto (Lightning picks best strategy automatically)
  • No explicit num_nodes or distributed_strategy config — 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 rgb_seq_length or of_seq_length.

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

ActionSpec FieldInference FunctionMeaning
evaluateencryption_keykeyencryption key
evaluateevaluate.checkpointparent_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
inferenceresults_diroutput_dircurrent job results directory
trainencryption_keykeyencryption key
trainmodel.of_pretrained_model_pathptm_if_no_resume_modelPTM when no resume checkpoint exists
trainmodel.rgb_pretrained_model_pathptm_if_no_resume_modelPTM when no resume checkpoint exists
trainresults_diroutput_dircurrent job results directory
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.

Comments

Markdown supported