Datasets:
Describe planned results.parquet layout
Browse files
README.md
CHANGED
|
@@ -32,6 +32,14 @@ Datasets repaired and filtered using the [OT-next-data validation protocol](http
|
|
| 32 |
- **V3:** newly solved tasks absent from v2, with the new evaluation's traces and statistics. Combine v2 and v3 for the full solved set.
|
| 33 |
- **V2:** keep tasks solved at least once by an evaluated model. Includes partial results where a success is already recorded; each README lists models, attempt counts and coverage.
|
| 34 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 35 |
## Incremental v3 releases
|
| 36 |
|
| 37 |
V3 task files contain only newly solved tasks, with no task-ID overlap with the corresponding v2 task file. Historical traces remain in v2; v3 includes every attempt from its new evaluation, successful and failed. These subsets were harder for the earlier evaluated models, not necessarily for every future model.
|
|
|
|
| 32 |
- **V3:** newly solved tasks absent from v2, with the new evaluation's traces and statistics. Combine v2 and v3 for the full solved set.
|
| 33 |
- **V2:** keep tasks solved at least once by an evaluated model. Includes partial results where a success is already recorded; each README lists models, attempt counts and coverage.
|
| 34 |
|
| 35 |
+
## Planned layout
|
| 36 |
+
|
| 37 |
+
We plan to reorganize this repository so each dataset stores its tasks once. Results from every validation stage and evaluation will go in one table instead of separate v1, v2 and v3 folders. This is not in place yet; the folders below still describe the current layout.
|
| 38 |
+
|
| 39 |
+
- **`results.parquet`:** one row per task revision and one column per check, with the value `pass`, `fail`, `warning`, `not_run` or `not_recorded`. Some checks add a details column, for example the model and settings for pass@k or the failed criteria for an LLM review. New checks and evaluations add new columns.
|
| 40 |
+
- **`tasks/`:** `r1.parquet` holds all original tasks. Later revision files hold only the tasks that changed.
|
| 41 |
+
- **Changed tasks:** a changed task gets a new row with a new `content_sha256` and a `change_reason`, and its checks start as `not_run` until rerun. Filter on `latest = true` for the current dataset.
|
| 42 |
+
|
| 43 |
## Incremental v3 releases
|
| 44 |
|
| 45 |
V3 task files contain only newly solved tasks, with no task-ID overlap with the corresponding v2 task file. Historical traces remain in v2; v3 includes every attempt from its new evaluation, successful and failed. These subsets were harder for the earlier evaluated models, not necessarily for every future model.
|