--- license: apache-2.0 language: - en pretty_name: "The Null Edit: per-token edit hazards of Gemma 4 on SWE-bench files" size_categories: - 1K/*.npz` | Per-token log-probabilities of one scored file (`offsets`, `lp_R`, and where run `lp_RX`, `lp_RB`, `lp_R0`). | | `*/conflict_/log.jsonl` | Index of the run: instance id, file path, token count, the wrong issue used, timings. | | `*/gen_/gen.jsonl` | The model's generated answers (line ranges; `_quote`: quoted lines) used as the asking baseline. | | `*/edit_/gen.jsonl` | Search/replace edits written with no hint, the map's top-5 lines, wrong-issue lines, or the gold lines. | | `*/noprefill_*/gen.jsonl` | Replies without the prefilled code fence, on the files greedy rewriting leaves unchanged. | | `*/an_.json` | Per-file analysis rows and summary for one run (source of the parquet table). | | `*/report_*.md`, `scaling.md` | The generated reports every number in the paper is taken from. | | `*/test_ids.txt`, `conf_ids.txt`, `live_ids.txt` | Instance lists: held-out order, pre-registered confirmation set, post-cutoff set. | | `dgx_bf16/runner.progress` | Start, end and exit status of every DGX run. | | `figures/` | The paper's figures. | ### Runs | Run | Model | Data | Files | |---|---|---|---| | `e4b_test` | E4B | SWE-bench Verified, held-out | 300 | | `e4b_live` | E4B | SWE-bench-Live, issues created on or after 2025-03-01 | 278 | | `e4b_ctrl` | E4B | controls: copy instruction (`RB`), no issue (`R0`) | 111 | | `e4b_q4_test` | E4B, community 4-bit weights run through the DGX code | held-out | 98 | | `e2b_test`, `g12b_test`, `g26b_test` | E2B, 12B, 26B A4B | held-out issues 1–100 | 111 each | | `g31b_test` | 31B (files up to 11,000 tokens: memory limit) | held-out issues 1–100 | 74 | | `g12b_conf`, `g26b_conf` | 12B, 26B A4B | pre-registered confirmation, issues 101–200 | 113 each | | `e4b_dev` | E4B | development set (every 20th instance) | 33 | Frames: `R` right issue + fix instruction (the probe); `RX` wrong issue; `RB` right issue + "print the file unchanged"; `R0` no issue. ### Main columns of `per_file` | Column | Meaning | |---|---| | `arm`, `run`, `iid`, `path`, `repo` | Which machine/weights, which run, SWE-bench instance, file, repository | | `n_tok`, `n_lines`, `n_units` | File size in tokens, lines, and functions | | `lrank_surp_R_sum` | Rank of the best-ranked gold line under the one-pass map **S** (1 = top) | | `lrank_drop_R_RX_pos` | Same under the issue-specific map **H** | | `lrank_surp_RX_sum` | Same under the wrong-issue control | | `lrank_gen`, `lrank_gen2` | Same for the generated answers (line ranges; quoted lines) | | `lrank_bm25` | Same for BM25 between issue and line | | `urank_*` | The same ranks at function level | | `total_surp_R_sum` | File total `S = −log P(no edit)` in nats | | `min_p_R` | Smallest token probability in the file; ≥ 0.5 means greedy rewriting reproduces the file | `hit@k` in the paper is the share of files with rank ≤ k; intervals use 10,000 instance-clustered bootstrap resamples. ## Limits you should know - **Oracle file.** Scored files are the ones the human patch touches; this is line and function localization inside a known file, not repository-level retrieval, and no test is executed. - **Memorization.** SWE-bench Verified predates the model. The post-cutoff set supports a within-set comparison, not a proof of no leakage. - **Labels.** A human patch is one valid fix among several. - **Python only**, files up to 32k tokens (31B: 11,000). One prompt, designed on E4B, with a prefilled code fence. - **Two arms are not interchangeable:** 4-bit and bf16 weights differ by 12 points on the same files. - The 31B asking baseline and the 31B confirmation run did not complete (memory); they are absent, not zero. - Ten early DGX command lines were not saved; the repository's run list marks them rather than reconstructing them. ## Provenance and licence Derived from [SWE-bench Verified](https://www.swebench.com/verified.html) (Jimenez et al., 2024) and [SWE-bench-Live](https://arxiv.org/abs/2505.23419) (Zhang et al., 2025); instance ids and file paths refer to those benchmarks, and generated answers may quote short fragments of the upstream source files, which remain under their own licences. Models: Google Gemma 4, used under the Gemma terms. The measurements, tables and figures in this dataset are released under Apache 2.0. ## Citation ```bibtex @misc{nulledit2026, title = {The Null Edit: Reading where a small model wants to change code, without letting it write}, year = {2026}, note = {Kaggle writeup, Google -- The Gemma 4 Developer Agent Paper Track}, howpublished = {\url{https://github.com/moncifem/null-edit}} } ```