rouge_l_evaluation
Compute deterministic ROUGE-L style generation metrics for Natural Instructions recovery outputs and ablations.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- rouge_l_evaluation
- description
- Compute deterministic ROUGE-L style generation metrics for Natural Instructions recovery outputs and ablations.
02 资源文件 3
- 参考文档calibration_rules.json104 B
- 脚本scripts/rouge_l.py1.3 KB
- 脚本tests/test_rouge_l_evaluation.py435 B
03 SKILL.md 正文
Rouge L Evaluation
Use this skill when reconstructing the BART0/Natural Instructions cross-task generalization workflow without relying on the original paper repository. Do not use it for unrelated instruction-following papers unless the task uses a Natural-Instructions-style schema, task-level held-out evaluation, and generation metrics.
Inputs
- Paper-derived module document and
module_plan.json. - Small task records or instruction items supplied by the current recovery attempt.
- Optional output paths for deterministic JSON artifacts.
Outputs
- Deterministic JSON or Python return values that can be consumed by downstream recovery scripts.
- Validation evidence from the included tests.
Workflow
- Read the current attempt inputs and keep source use inside the allowed recovery boundary.
- Apply the module contract exactly as described by the paper-derived module document.
- Write machine-readable artifacts when a CLI output path is provided.
- Cross-check downstream consumers with tests before accepting recovery evidence.
Validation
Run python <distiller>/module-to-skill/scripts/validate_skill_tree.py <skill_dir> --run-tests from any working directory. The included tests are standard-library compatible and do not require the original source repository.
Limitations
This skill preserves a reusable mechanism from the paper but does not by itself reproduce full BART-base training on all 61 Natural Instructions tasks. Full recovery requires a resolved dataset and model runtime; reduced recovery must remain explicitly marked as proxy evidence.
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).