dpo_sequence_logprob_accounting
Compute response-only sequence log probabilities for DPO by masking prompts and padding before summing token log probabilities.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- dpo_sequence_logprob_accounting
- description
- Compute response-only sequence log probabilities for DPO by masking prompts and padding before summing token log probabilities.
02 资源文件 2
- 脚本scripts/logprob_accounting.py2.2 KB
- 脚本tests/test_logprob_accounting.py1.2 KB
03 SKILL.md 正文
DPO Sequence Log Probability Accounting
Use this skill when converting model token scores into the log pi(y|x) values consumed by DPO. It is appropriate for full model recovery and for deterministic tests of the DPO objective. Do not use it to normalize preference records or to compute the DPO loss itself.
Inputs
- Per-position token log-probability tables or logits converted to log probabilities.
- Label token ids for next-token prediction.
- Ignored positions marked as
-100for prompt and padding tokens. - Optional
averageflag.
Outputs
- Response-only summed or averaged sequence log probabilities.
- Token counts and selected token log-probabilities when diagnostics are requested.
Workflow
- Ensure each example has aligned per-position token distributions and labels.
- Shift labels one position to match next-token prediction if using full prompt+response sequences.
- Ignore labels equal to
-100so prompt and padding positions do not affect the response probability. - Gather the log probability assigned to each unmasked label token.
- Sum by default; average only when the caller explicitly requests length normalization.
Validation
Run:
python scripts/logprob_accounting.py --self-test
python tests/test_logprob_accounting.py
Limitations
The script uses standard-library math and expects log-probability inputs for reduced tests. Full tensor implementations should preserve the same mask semantics.
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).