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
distributedRoutes ChainerMN distributed training, MPI, communicator, and model-parallel workflows.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill for ChainerMN workflows: multi-process data parallelism, MPI launch issues, communicator selection, distributed optimizers, dataset scattering, multi-node evaluators, and model-parallel links.
create_communicator fail?"MultiNodeChainList or model-parallel seq2seq?"references/workflows.md for distributed training patterns.references/api-reference.md for communicators, optimizers, datasets, links, and extensions.references/troubleshooting.md for MPI, mpi4py, NCCL, and launch failures.../../scripts/chainermn_probe.py for a safe MPI / ChainerMN prerequisite check.chainermn.create_communicator(...)chainermn.create_multi_node_optimizer(...)chainermn.scatter_dataset(...)chainermn.create_multi_node_evaluator(...)chainermn.MultiNodeChainListmpi4py, NCCL, CUDA-aware MPI, and CPU-only naive communicator guidance../training/../export/../chainerx/ChainerMN runtime verification requires MPI and usually mpi4py; GPU-scale workflows also require CuPy, NCCL, and CUDA-aware MPI.
If those dependencies are unavailable, treat distributed execution as environment-blocked rather than disproven.