计划执行与检查节点
executing-plans
按既定实施计划完成工作,保持过程检查和反馈。
torch-and-foundation-models【效率与协作】Use Darts PyTorch forecasting models and foundation wrappers with explicit backend, checkpoint, and cache/download boundaries.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this sub-skill when the user needs Darts neural forecasting models, darts[torch], PyTorch Lightning trainer kwargs, CPU/GPU verification, checkpoints, or foundation model wrapper planning.
references/backend-and-training.md for install checks, CPU/GPU/TPU boundaries, trainer kwargs, chunk lengths, and checkpoint discipline.references/model-overview.md for torch/foundation model family routing and optional dependencies.references/workflows.md for tiny CPU TCNModel patterns and staged backend escalation.references/troubleshooting.md for torch import, CUDA, covariates/chunks, checkpoints, and foundation cache/no-network failures.scripts/torch_model_smoke.py for safe import/model-construction and optional one-epoch CPU training smoke.darts[torch], torch, and pytorch_lightning; run torch_model_smoke.py before real training.input_chunk_length, output_chunk_length, n_epochs, and CPU pl_trainer_kwargs.../data-processing-and-covariates/, then map them to model-specific chunk/covariate support here.../evaluation-and-explainability/.python scripts/torch_model_smoke.py # imports and constructs a tiny CPU TCNModel
python scripts/torch_model_smoke.py --train # optional one-epoch generated-data CPU training smoke
Use an explicit temporary or user-approved work directory for checkpoints/logs. Do not write training artifacts into the skill directory.
This sub-skill documents optional CUDA/foundation behavior but the baseline verification only proved CPU torch. Do not claim accelerator or foundation model execution until separately verified with the required hardware, wheel, cache, and memory in the user's environment.