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
model-configurationRoute config parsing, SR3/DDPM selection, conditional inputs, beta schedules, checkpoints, GPU ids, and model API facts.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a request is about the repo's comment-bearing JSON configs, model family choice, noise schedules, checkpoint resume, GPU selection, or the diffusion model object's public API.
config/.which_model_G switch between ddpm and sr3.resume_state, gpu_ids, and W&B project metadata.model/.config/*.json as JSON-with-comments, not strict JSON.-p/--phase and -gpu/--gpu_ids flags override config values at runtime.phase is only the default input; core.logger.parse rewrites it from the CLI.path.resume_state names the checkpoint stem only; the loader appends _gen.pth and _opt.pth.conditional=true implies a 6-channel UNet input in this repo; conditional=false uses 3 channels.gpu_ids controls CUDA_VISIBLE_DEVICES and distributed wrapping; verify the rendered GPU string before assuming multi-GPU behavior.norm_groups must divide every UNet stage width.wandb.project field and CLI flags such as -enable_wandb, -log_wandb_ckpt, -log_eval, and -log_infer.This router is grounded in the project README, the config/*.json families, core/logger.py, model/networks.py, model/model.py, model/ddpm_modules/*, and model/sr3_modules/*.