Scoolar commited on
Commit
287c337
·
verified ·
1 Parent(s): b4747e3

Card: name all four pooled searches, describe the samples exactly, compute every number

Browse files
Files changed (1) hide show
  1. README.md +14 -14
README.md CHANGED
@@ -30,7 +30,8 @@ The [CodeSearchNet Challenge](https://github.com/github/CodeSearchNet) (Husain e
30
  dataset treats every rated function of a language as one codebase and searches all of it: for each
31
  search, every function in its language is a candidate. The experts' ratings are kept, and the
32
  pairs they never rated but a search tool returned were rated on the same scale by a judge model,
33
- validated against the experts first. Random samples of the pairs no tool returned were rated too.
 
34
 
35
  | Language | Searches | Functions | Rated by experts | Rated by the judge | Relevant |
36
  |---|---:|---:|---:|---:|---:|
@@ -50,21 +51,21 @@ which describes the method, the judge's validation and the results in full.
50
  searches used to tune the benchmark's tools, `test` for all others).
51
  - `corpus`: one row per function: `id`, `language`, `code` (the rated lines at the rated commit),
52
  `url`, `repository`, `commit`, `path`, `first_line`, `last_line`, `license` (the repository's
53
- SPDX license id as GitHub reports it in September 2026, `NOASSERTION` or `null`) and `sha256`
54
  of `code`.
55
  - `qrels`: one row per rated search-function pair: `relevance` (the experts' mean rating, else the
56
  judge's rating, 0 to 3), `relevant` (`relevance` of 2 or more), `source` (`expert` or `judge`),
57
  `expert_ratings`, `judge_rating` (also given for expert-rated pairs, to check the judge), and
58
- `rated_because` (`expert`, `pooled`: a search tool returned it, or `sample`: a random sample of
59
- what the tools did not return).
60
 
61
  ## How the judge rated
62
 
63
- GPT-6 Astra through the Codex CLI, low reasoning effort, no tools, in batches of 40 pairs mixed
64
- across searches, seeing an opaque id, the search and the code (cut at 20,000 characters), never
65
- which tool returned the pair. The prompt gave the Challenge's 0-3 scale and its description of each
66
- level. Before any of its ratings were used, it rated every expert-rated pair of the language; the
67
- gate, set in advance, was an F1 of 0.67 on "relevant" against the experts:
68
 
69
  | Language | Expert-rated pairs | Same verdict as the experts | F1 | Gate |
70
  |---|---:|---:|---:|---|
@@ -75,12 +76,11 @@ gate, set in advance, was an F1 of 0.67 on "relevant" against the experts:
75
  | Ruby | 300 | 83% | 0.709 | passed |
76
  | Go | 162 | 80% | 0.629 | **missed** |
77
 
78
- Where two experts rated the same pair (848 Python pairs), they agree on 70% of verdicts, F1 0.711.
79
- In Go the judge agrees on most verdicts but calls more pairs relevant than Go's experts did, and it
80
- missed the gate on only 40 relevant expert pairs; use Go's judge ratings with that in mind.
81
 
82
- Pooled pairs came from three tools: grep with a pattern a coding agent wrote per search, jevpipe and
83
- DeepSeek V4.1 Flash.
 
84
 
85
  ## Use it with care
86
 
 
30
  dataset treats every rated function of a language as one codebase and searches all of it: for each
31
  search, every function in its language is a candidate. The experts' ratings are kept, and the
32
  pairs they never rated but a search tool returned were rated on the same scale by a judge model,
33
+ validated against the experts first. Random samples of the pairs only a loose any-keyword grep
34
+ returned, and of the pairs nothing returned, were rated too.
35
 
36
  | Language | Searches | Functions | Rated by experts | Rated by the judge | Relevant |
37
  |---|---:|---:|---:|---:|---:|
 
51
  searches used to tune the benchmark's tools, `test` for all others).
52
  - `corpus`: one row per function: `id`, `language`, `code` (the rated lines at the rated commit),
53
  `url`, `repository`, `commit`, `path`, `first_line`, `last_line`, `license` (the repository's
54
+ SPDX license id as GitHub reported it in September 2026, `NOASSERTION` or `null`) and `sha256`
55
  of `code`.
56
  - `qrels`: one row per rated search-function pair: `relevance` (the experts' mean rating, else the
57
  judge's rating, 0 to 3), `relevant` (`relevance` of 2 or more), `source` (`expert` or `judge`),
58
  `expert_ratings`, `judge_rating` (also given for expert-rated pairs, to check the judge), and
59
+ `rated_because` (`expert`, `pooled`: a search tool returned it, or `sample`: one of the random
60
+ samples above).
61
 
62
  ## How the judge rated
63
 
64
+ GPT-6 Astra through the Codex CLI, low reasoning effort, no tools, in batches of 40 pairs
65
+ mixed across searches, seeing an opaque id, the search and the code (cut at 20,000 characters),
66
+ never which tool returned the pair. The prompt gave the Challenge's 0-3 scale and its description of
67
+ each level. Before any of its ratings were used, it rated every expert-rated pair of the language;
68
+ the gate, set in advance, was an F1 of 0.67 on "relevant" against the experts:
69
 
70
  | Language | Expert-rated pairs | Same verdict as the experts | F1 | Gate |
71
  |---|---:|---:|---:|---|
 
76
  | Ruby | 300 | 83% | 0.709 | passed |
77
  | Go | 162 | 80% | 0.629 | **missed** |
78
 
79
+ Where two experts rated the same pair (848 Python pairs), they agree on 70% of verdicts, F1 0.711. In Go the judge missed the gate on only 40 relevant expert pairs, and calls more pairs relevant (49) than its experts did (40); use its ratings there with that in mind.
 
 
80
 
81
+ Pooled pairs came from four searches: grep with a pattern a coding agent wrote per search, grep
82
+ for all of the search's keywords, jevpipe with a probability of 0.3 or more, and DeepSeek V4.1
83
+ Flash answering yes or with a probability of 0.3 or more.
84
 
85
  ## Use it with care
86