otheiner commited on
Commit
0f6834f
·
verified ·
1 Parent(s): 47a40c3

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +64 -1
README.md CHANGED
@@ -1,4 +1,67 @@
1
  ---
2
  license: mit
3
  ---
4
- # PARAMETR-Bench Dataset
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
  ---
2
  license: mit
3
  ---
4
+
5
+ <div style="overflow: hidden; height: 390px; text-align: center;">
6
+ <img src="https://otheiner.github.io/PARAMETR-Bench-blog/assets/images/PARAMETR-Bench/heading.png" width="100%">
7
+ </div>
8
+ <br>
9
+
10
+ # 📊 PARAMETR-Bench
11
+
12
+ <div style="text-align: justify">
13
+
14
+ PARAMETR-Bench is a procedurally generated benchmarking framework for evaluating AI agents on multi-step scientific data
15
+ analysis tasks. Each task instance is produced by a seeded generator, so every run yields fresh input data — addressing
16
+ the dataset contamination and saturation problems that affect static benchmarks. The key methodological contribution is
17
+ [**metarubrics**](https://otheiner.github.io/PARAMETR-Bench-blog/#metarubrics-and-rubrics): rubric templates that are auto-populated by the same generator that produces the task data, so grading criteria
18
+ stay aligned with the ground truth without any manual effort per run.
19
+
20
+ To learn more about the framework, read the [blog post](https://otheiner.github.io/PARAMETR-Bench-blog/).
21
+ </div>
22
+
23
+ # About This Dataset
24
+
25
+ <div style="text-align: justify">
26
+ Seeded procedural task generation mitigates the risk of benchmark data leaking into model training sets. The blog post describes
27
+ a contamination detection experiment built on this property. The experiment compares model performance on two sets of seeds —
28
+ public and private — evaluated at the same difficulty level. At the time of initial evaluation, both sets are statistically
29
+ equivalent. By publishing the public seed set together with the generated input data and ground-truth artifacts, we maximize
30
+ the probability that this data is crawled and ingested by future model training pipelines. If a subsequent model generation has
31
+ been trained on this data, it should show measurably higher performance on the public seeds than on the withheld private seeds.
32
+ A statistically significant gap between the two would suggest contamination.
33
+
34
+ Even though the probability of detectable leakage is uncertain, and PARAMETR-Bench is currently a personal proof-of-concept
35
+ project rather than an established benchmark, the experiment is worth running — the cost is low and the potential signal is
36
+ informative regardless of outcome.
37
+ </div>
38
+
39
+ # Dataset Structure
40
+
41
+ <div style="text-align: justify">
42
+ The dataset contains evaluation instances for four tasks across four public seeds (10, 11, 12, 13) at hard difficulty. Each
43
+ instance consists of:
44
+
45
+ - **Input data** — multimodal files (images, CSV tables, text files) provided to the agent
46
+ - **Task prompt** — the task definition presented to the model
47
+ - **Rubrics** — populated grading criteria (JSON) with correct answers, instantiated from metarubrics using the generator's
48
+ ground truth. To understand metarubric, check the [blog post](https://otheiner.github.io/PARAMETR-Bench-blog/#metarubrics-and-rubrics)
49
+
50
+ The dataset is organized by task and seed:
51
+
52
+ ```
53
+ task_name/
54
+ seed_N/
55
+ input/ ← multimodal input files provided to the agent
56
+ prompt.md ← task definition
57
+ rubrics.json ← populated rubrics with correct answers
58
+ ```
59
+
60
+ This dataset is not intended to be loaded programmatically as a training dataset. It is an evaluation artifact meant to be used
61
+ with the PARAMETR-Bench framework or inspected manually.
62
+ </div>
63
+
64
+ # Limitations
65
+
66
+ This dataset covers four physics tasks in one domain. It is a proof-of-concept release. See the
67
+ [limitations section](https://otheiner.github.io/PARAMETR-Bench-blog/#limitations-and-whats-next) of the blog post for a full discussion.