data-formats-and-validation
Validate and prepare Chronos long-format data, covariates, timestamps, and preprocessing inputs before forecasting.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- data-formats-and-validation
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Validate and prepare Chronos long-format data, covariates, timestamps, and preprocessing inputs before forecasting.
- disable-model-invocation
- true
02 资源文件 4
- 参考文档references/data-formats.md3.7 KB
- 参考文档references/preprocessing-api-reference.md4.6 KB
- 参考文档references/troubleshooting.md3.8 KB
- 脚本scripts/validate_chronos_dataframe.py19.8 KB
03 SKILL.md 正文
Data Formats and Validation
Use this sub-skill when the task is about preparing Chronos inputs, checking DataFrame schemas, or debugging preprocessing before forecasting.
Covers
- Long-format pandas DataFrames for
Chronos2Pipeline.predict_df chronos.df_utilsnormalization, validation, and future-timestamp generationchronos.chronos2.preprocesshelpers for tensors, list-of-tensors, DataFrames, and list-of-dicts- Target and covariate alignment, timestamp frequency rules, categorical
covariates, and
validate_inputs=Falsehazards
Route elsewhere
- Model loading, forecasting, embeddings, or output interpretation:
../chronos-2-forecasting/or../chronos-bolt-and-original/ - Fine-tuning, evaluation, benchmark configs, or deployment:
../training-evaluation-deployment/
Read first
references/data-formats.mdreferences/preprocessing-api-reference.mdreferences/troubleshooting.mdscripts/validate_chronos_dataframe.py --help
Runtime files
references/data-formats.mdreferences/preprocessing-api-reference.mdreferences/troubleshooting.mdscripts/validate_chronos_dataframe.py
Use this sub-skill to answer
- Which columns Chronos expects in
dfandfuture_df - How
future_dfis matched to context rows - Which helper to use for DataFrame, list-of-dicts, or tensor inputs
- How Chronos handles categorical covariates and known-future values
- What breaks when validation is skipped
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).