brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
moe-and-accelerationUse this repo skill for Swin-Transformer optional Swin-MoE, Tutel, Apex, fused window-process CUDA extension, distributed checkpoint, and backend probe workflows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task involves Swin-MoE, Tutel, optional Apex fused layernorm/optimizers, --fused_window_process, the CUDA window-process extension, or distributed MoE checkpoint behavior.
main_moe.py command shape and distributed expectations.MODEL.SWIN_MOE config fields: experts, top-k, capacity factor, router type, aux loss, and MoE block placement.swin_window_process CUDA extension build/probe guidance.fused_adam, fused_lamb.core-models.main.py commands: training-eval-cli.data-and-checkpoints.simmim-workflows.scripts/check_optional_backends.py to see which optional backends are actually available.references/moe-and-acceleration.md for command and config rules.scripts/swin_cli_command_builder.py --workflow moe-train or moe-eval.references/troubleshooting.md and avoid claiming runtime verification.CPU import checks are not evidence that Tutel MoE, Apex fused ops, or the custom CUDA extension works. Treat those as optional backend capabilities that require compatible CUDA/PyTorch/toolkit/runtime evidence.
references/moe-and-acceleration.md - MoE and optional acceleration workflow details.references/troubleshooting.md - missing Tutel/Apex/fused-kernel and distributed checkpoint issues.scripts/check_optional_backends.py - safe optional backend probe.