AGENT SKILL

forecasting

Configure, run, and debug Time-Series-Library long-term, short-term/M4, exogenous/TimeXer, and zero-shot forecasting workflows.

License 许可
MIT
最近更新
2026-09-03
Stars
★ 351
Forks
27

01 前言 Front Matter

name
forecasting
license
MIT
metadata
{ "disco-role": "operating" }
description
Configure, run, and debug Time-Series-Library long-term, short-term/M4, exogenous/TimeXer, and zero-shot forecasting workflows.
disable-model-invocation
true

02 资源文件 4

03 SKILL.md 正文

TSLib Forecasting

Use this sub-skill for TSLib forecasting tasks: long-term forecasting on ETT/custom/ECL/Traffic/Weather/Exchange/ILI-style CSVs, short-term M4 forecasting, TimeXer/exogenous variable recipes, zero-shot forecasting with large time-series models, and forecasting metric/output interpretation.

Route Here

  • Build or revise python run.py --task_name long_term_forecast ... commands.
  • Configure --seq_len, --label_len, --pred_len, --features, --target, channel counts, and forecast model dimensions.
  • Use TimeXer or features MS for exogenous/target-only forecast settings.
  • Run or debug short_term_forecast with M4 seasonal patterns and SMAPE/OWA outputs.
  • Understand zero-shot --task_name zero_shot_forecast and optional LTSM model dependencies.
  • Interpret metrics.npy, pred.npy, true.npy, result text files, plot PDFs, and M4 forecast CSVs.

Reroute

  • Data file validation, UEA/anomaly layouts, generic CLI outputs, or CPU/GPU preflight: use ../data-and-cli/SKILL.md.
  • Imputation, anomaly detection, and classification: use ../imputation-anomaly-classification/SKILL.md.
  • Adding models, Mamba/LTSM dependency installation, and augmentation flags: use ../foundation-models-and-customization/SKILL.md.

Start Fast

Render a small command rather than copying a benchmark script verbatim:

python scripts/build_tslib_command.py long-term \
  --model DLinear --root-path ./dataset/tiny-custom/ --data-path tiny.csv \
  --model-id tiny_custom --features M --channels 3 \
  --seq-len 8 --label-len 4 --pred-len 4 --cpu-smoke

Then run the printed command from the TSLib checkout. Use real benchmark scripts only after paths, GPU, dependencies, and expected cost are clear.

Forecasting Modes

  • Long-term forecast: --task_name long_term_forecast; uses sliding windows and writes MAE/MSE/RMSE/MAPE/MSPE plus optional DTW.
  • Short-term/M4 forecast: --task_name short_term_forecast --data m4; uses M4 seasonal patterns and losses such as SMAPE. Final averaged M4 metrics print after all six seasonal forecast CSVs exist.
  • Exogenous/TimeXer forecast: still uses long_term_forecast; TimeXer recipes often set --model TimeXer and may use features MS when forecasting a target with exogenous inputs.
  • Zero-shot forecast: --task_name zero_shot_forecast --is_training 0; model files such as Chronos, Moirai, TimesFM, TiRex, Sundial, and TimeMoE can require optional packages, model downloads, and CUDA assumptions.

References and Helpers

  • references/forecasting-workflows.md gives long-term, M4, TimeXer, and zero-shot recipes.
  • references/metrics-and-results.md explains forecast metrics and result files.
  • references/troubleshooting.md covers forecasting-specific data/window/channel/model errors.
  • scripts/build_tslib_command.py renders safe starter commands for long-term, M4, TimeXer, and zero-shot workflows.
  • ../../references/model-catalog.md maps model names to optional dependency surfaces.

Avoid

  • Do not treat zero-shot LTSM source files as verified just because core TSLib imports work.
  • Do not run M4 or long-horizon benchmark scripts as a smoke check; use tiny data and short windows first.
  • Do not use features MS without confirming --target and output channel expectations.

04 同仓库更多 Skills

VectorSpaceLab
VectorSpaceLab/AREX-Skill

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.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

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.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

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.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

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.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

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.

★ 351
VectorSpaceLab
VectorSpaceLab/AREX-Skill

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).

★ 351