executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
trainingConstruct safe MUNIT and UNIT training commands and diagnose outputs, checkpoints, resume, and config tuning.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the user needs to plan or run a MUNIT repository training job, choose between the MUNIT and UNIT trainers, understand output/checkpoint layout, resume a stopped run, or tune training/config/loss surfaces before launching a long GPU job.
This sub-skill is self-contained operating knowledge distilled from the repository training entrypoint, trainer classes, utility helpers, configs, tutorial/manual training sections, and demo shell workflows. It intentionally does not depend on reopening source files.
Use this sub-skill for:
train.py CLI and the infinite-until-max_iter training loop.MUNIT versus UNIT and checking trainer-specific config keys.gen_*.pt, dis_*.pt, and optimizer.pt checkpoint directories.Reroute instead:
../data-and-configuration/.../environment-and-setup/.../model-internals/.../inference-and-evaluation/..cuda() on the trainer, sampled display tensors, each input batch, MUNIT style tensors, VAE noise tensors, and VGG preprocessing tensors. There is no CLI flag for CPU-only training.--config, --output_path, --resume, and --trainer (MUNIT|UNIT).MUNIT. UNIT is selectable by CLI but needs UNIT-specific KL loss weights (recon_kl_w, recon_kl_cyc_w) that are not present in the bundled MUNIT demo configs.<output_path>/logs/<model_name> and <output_path>/outputs/<model_name>.The bundled helper performs static checks and prints a command without executing training:
python scripts/munit_train_command.py --help
python scripts/munit_train_command.py \
--repo-root /path/to/user/munit-checkout \
--config configs/demo_edges2handbags_folder.yaml \
--output-path runs/demo_edges2handbags \
--trainer MUNIT
Only after the user explicitly authorizes a real run, use the printed command from the repository root in a suitable legacy CUDA runtime. Do not treat the helper as a launcher; it never downloads data, starts CUDA, or imports the repository package.
references/workflows.md - staged training and resume workflows, including the distilled training loop and demo-script adaptation notes.references/cli-reference.md - training CLI arguments, trainer selection, trainer update methods, and config/loss tuning surfaces.references/checkpoints-and-outputs.md - output tree, image/log/checkpoint filenames, resume behavior, and monitoring expectations.references/troubleshooting.md - failure-mode lookup for CUDA, config, display sampling, resume, VGG, logging, tensorboardX, and legacy warnings.scripts/munit_train_command.py - self-contained dry-run command builder and static validator.