Add the R6 pipeline inputs

README.md

@@ -45,15 +45,10 @@ The IDs are the pipeline's input IDs.
 | R14-meta | `phase2/eval_responses_meta.parquet` | 2 MB | `59872f7e7a31…` | The small columns of R14's answer file (model, stage, task, question, seed, correctness, checkpoint folder, token limit). `mvpt fetch-phase2-records` writes the same file from R14. |
 | R14-lengths | `phase2/answer_lengths.parquet` | 6 MB | `9863758e52d1…` | One row per Phase 2 answer of R14, without its text: its length, and whether the grader found an answer and a code block. `mvpt measure-phase2-answers` writes the same file from R14 in about two hours. |
 | S1 | `snapshots/hf_checkpoints.json` | 87 kB | `3e0a2a818b6f…` | A snapshot of the Hugging Face records of every checkpoint the paper evaluates (repos, weight hashes, model cards, training summaries, context settings), taken on 2026-10-12 and 2026-10-13. It gives each checkpoint's parent in the results manifest. |
+| R6 | `older/logs_without_gpqa_items.zip` | 416 MB | `2f9db28c0e7a…` | LM Evaluation Harness and Evalchemy results files of the older evaluations, January to May 2026, without the GPQA Diamond items (see below). No table of the paper prints them, but the results manifest keeps them. |
 
 The full SHA-256 of each file is in `inputs.json`, which checks every download.
 
-**Not here yet: R6** (`logs.zip`, 629 MB), the LM Evaluation Harness and
-Evalchemy results files of the older evaluations, January to May 2026. No table
-of the paper prints them, but the results manifest keeps them. Their results
-files hold every GPQA Diamond item in full, and GPQA asks that its items not be
-published in plain text, so R6 is added once that is resolved.
-
 ## Formats
 
 **Protocol A records** (R15, R18 to R21) have one row per checkpoint, decoding
@@ -68,8 +63,16 @@ the LM Evaluation Harness writes, zipped as received. R8 and R8-fineweb also
 hold its per-question files, which contain the benchmark questions and the
 models' answers.
 
-The paths with `/e/scratch/jureap59/` in the language results files are the
-working directory of the cluster the evaluations ran on.
+**Older evaluations** (R6) are the results files as received, except for
+GPQA Diamond. GPQA asks that its items not be published in plain text, and
+Evalchemy saves every item it scores with the results, so here each GPQA item
+keeps only its GPQA record ID, the letter of the correct choice, and the model's
+answer in each repetition if it is a letter (otherwise an empty string). The
+scores and every other file are unchanged. `release/records/strip_gpqa.py` of
+the pipeline writes this copy from the original.
+
+The paths with `/e/scratch/jureap59/` in the results files are the working
+directory of the cluster the evaluations ran on.
 
 ## Versions
 

older/logs_without_gpqa_items.zip

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2f9db28c0e7a8485606846c0bd66f523e792a4a38691c057349884fbcb4361d9
+size 415919319