training-workflows
Lightly SSL training recipes for PyTorch, Lightning, and gated distributed variants.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- training-workflows
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Lightly SSL training recipes for PyTorch, Lightning, and gated distributed variants.
- disable-model-invocation
- true
02 资源文件 5
- 参考文档references/distributed-training.md2.5 KB
- 参考文档references/lightning-workflows.md3.7 KB
- 参考文档references/training-recipes.md4.5 KB
- 参考文档references/troubleshooting.md2.7 KB
- 脚本scripts/tiny_simclr_training_step.py4.5 KB
03 SKILL.md 正文
training-workflows
Use this sub-skill when a task needs to turn a LightlySSL method example into a runnable training plan, choose a recipe family, adapt a training loop to local data, or debug PyTorch Lightning/distributed training behavior. It does not run long training by default; it helps future agents plan and validate safely first.
Use this sub-skill for
- Bare PyTorch Lightly recipes that wire a backbone, projection head, transform, dataloader, loss, optimizer, and training step.
- PyTorch Lightning module patterns,
Trainerknobs, checkpoint handling, precision/device choices, and batch-size/worker decisions. - Adapting repo-style CIFAR/download examples to local image folders or synthetic no-download smoke checks.
- Distributed or accelerator-aware training plans when the user explicitly asks for GPU, multi-GPU, DDP, or distributed losses.
- Troubleshooting feature-dimension mismatches, missing checkpoints, long-running data downloads,
drop_last/batch issues, and DDP hangs.
Start here
- Training recipes — method selection, bare PyTorch loop patterns, and local-folder adaptation.
- Lightning workflows —
LightningModule,Trainer, checkpointing, and batch/device knobs. - Distributed training — DDP settings, optional sync/gather caveats, and backend honesty.
- Troubleshooting — common failures, causes, and fixes.
- Synthetic SimCLR step — one no-download smoke step for backbone, feature-dimension, and contrastive-loss wiring.
Route elsewhere
- API component catalogs, transform/loss/head signatures, and tensor-only component debugging: use
ssl-building-blocks. lightly-ssl-train,lightly-embed,lightly-magic,lightly-crop, Hydra overrides, and data folder validation: usecli-data-embedding.- Maintainer tests, generated notebooks, docs, benchmarking utilities, and repository validation: use
evaluation-maintenance.
Safe workflow order
- Choose the method family and recipe style: bare PyTorch, Lightning, or distributed Lightning.
- Validate the low-level components with
ssl-building-blockswhen dimensions, transforms, or losses are uncertain. - Run
python scripts/tiny_simclr_training_step.py --device cpufrom this sub-skill before touching user data. - Replace example dataset downloads with a local folder or a user-provided dataset only after the smoke passes.
- Scale to CUDA or DDP only after checking hardware, package backends, output paths, and runtime budget.
- For repository edits to examples or docs, route to
evaluation-maintenancefor notebook/docs/test commands.
Guardrails
- Prefer local image folders or synthetic tensors; do not make future agents run download-heavy example scripts as the first validation step.
- Treat distributed training as optional and explicitly gated by hardware, process group setup, and user approval.
- Do not claim GPU or DDP verification from a CPU import; run a real backend smoke when those capabilities are required.
- Keep CLI train/embed/magic as artifact-writing workflows. Use
cli-data-embeddingto build commands and set output/checkpoint paths before execution.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).