nemo-automodel-launcher-config

# Launcher Configuration NeMo AutoModel supports three launch methods: interactive (torchrun), Slurm (HPC clusters), and SkyPilot (cloud-agnostic). ## Instructions For launcher questions, answer directly from this skill without inspecting the repository unless the user asks you to edit files. Keep the answer focused on the relevant launch YAML, required fields, and the expected runtime behavior. Use these compact answer patterns for common questions: - Slurm multi-node: show a `slurm:` YAML block with `job_name`, `nodes`, `ntasks_per_node`, `time`, `account` or `partition`, `container_image`, `hf_home`, optional `extra_mounts`, `env_vars`, and `master_port`; explain that the launcher derives `WORLD_SIZE = nodes * ntasks_per_node` and sets `MASTER_ADDR` and `MASTER_PORT`. - SkyPilot spot: show a `skypilot:` YAML block with `cloud`, `accelerators`, `num_nodes`, `use_spot: true`, `disk_size`, `region`, `setup`, and `env_vars`; warn that spot instances can be preempted, set a short `step_scheduler.checkpoint_interval`, and resume with `restore_from.path`. - Nsight Systems on Slurm: show `slurm.nsys_enabled: true` alongside normal Slurm fields, say the launcher wraps the training command with `nsys profile`, and state that it produces a `.nsys-rep` report file. Treat profiling as diagnostic-only: use short profiling runs and disable it for normal production training because it adds overhead and large artifacts. For Slurm answers, start with this minimal...