configuration-data
Route Snakemake configuration, sample metadata, schema validation, pathvars, envvars, YTE, PEP, and data-driven helper tasks.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- configuration-data
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Route Snakemake configuration, sample metadata, schema validation, pathvars, envvars, YTE, PEP, and data-driven helper tasks.
- disable-model-invocation
- true
02 资源文件 4
- 参考文档references/configuration-reference.md10.2 KB
- 参考文档references/data-validation.md4.3 KB
- 参考文档references/troubleshooting.md5.8 KB
- 脚本scripts/validate_config_schema.py4.9 KB
03 SKILL.md 正文
Configuration Data
Use this sub-skill when a Snakemake task involves configfile, CLI config overrides, profile-provided config, JSON/YAML config loading, config mutation, sample tables, snakemake.utils.validate, PEP metadata, envvars, pathvars, YTE-templated YAML, or data-driven helpers such as lookup, branch, evaluate, collect, subpath, and exists.
Route by Need
- Config sources, precedence, CLI quoting, profiles, YTE,
envvars,pathvars, PEP, and helper patterns: read configuration-reference.md. - JSON Schema validation for dictionaries, pandas tables, Polars tables, defaults, and relative
$ref: read data-validation.md. - Common failures and diagnostic signals for invalid config, schema errors, optional dependencies, pathvar cycles, and helper misuse: read troubleshooting.md.
- Standalone preflight for config/sample schemas before a full run: use validate_config_schema.py.
Fast Workflow
- Inventory every config source: Snakefile
configfile, included files, CLI--configfile, CLI--config, profiles, workflow profile, and any top-level Pythonupdate_config(config, ...). - Resolve precedence before editing rules: later config files recursively extend earlier files,
--configwins over config files, and--replace-workflow-configdiscards workflow-defined config keys not provided by CLI config files. - Validate early, before rule definitions consume values:
from snakemake.utils import validate; thenvalidate(config, "schemas/config.schema.yaml")and validate any sample tables. - Keep secrets out of config files: assert names with
envvars:and pass required values explicitly throughparamsrather than assuming shell commands receive them. - Run
snakemake --cores 1 --dry-run --printshellcmdsafter config/pathvar/schema changes. Do not add--reason; it is not a valid Snakemake 9.23.1 flag.
Boundaries
- Route rule graph syntax, wildcard design, module structure, and rule directives to
../workflow-authoring/SKILL.md; this sub-skill only owns the data/config semantics feeding them. - Route command execution strategy, profile selection, cores, dry-runs, and executor flags to
../execution-cli/SKILL.md; this sub-skill covers only config-related CLI arguments. - Route storage-provider setup to deployment/storage guidance; this sub-skill only notes that
exists()respects Snakemake storage settings. - Route report rendering and metadata display to debugging/reporting guidance unless the issue is config data feeding report metadata.
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).