Datasets:
Release [run release-20261111T153845Z]
#21
by Battam - opened
This view is limited to 50 files because it contains too many changes. See the raw diff here.
- CHANGELOG.md +18 -0
- README.md +27 -27
- README.zh.md +27 -27
- campaign_files/2026-10-c-repros-2/mertens-ap-constants-repro/README.md +0 -2
- campaign_files/2026-10-c-repros-2/mertens-zeta-reciprocal-repro/README.md +0 -2
- campaign_files/2026-10-g-solver-instances-2/maze-curriculum-dataset/README.md +0 -4
- campaign_files/2026-10-g-solver-instances-2/minlplib/README.md +0 -4
- campaign_files/2026-10-gt-browser-tests-2/mblaze-mflag/README.md +0 -4
- campaign_files/2026-10-gt-browser-tests-2/mergecal-calendar-colours/README.md +0 -4
- campaign_files/2026-10-gt-browser-tests-2/mergecal-no-uids/README.md +0 -4
- campaign_files/2026-10-gt-browser-tests-2/mergecal-recurring-with-override/README.md +0 -4
- campaign_files/2026-10-gt-browser-tests-2/mergecal-two-vcalendars/README.md +0 -4
- campaign_files/2026-10-gt-browser-tests-2/mimekit-mbox/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/mcgills-passenger-gtfs/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/mcgillsse-passenger-gtfs/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/mdot-mta-marc-gtfs/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/metrobus-passenger-gtfs/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/metrolink-gtfs/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/metzdowd-cryptography/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/mit-kerberos/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/mc-zen-pillar-tests/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/mc-zen-quill-tests/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/mc-zen-tidy-tests/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/mc-zen-zero-tests/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/md4c-spec-wiki-links/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/mdformat/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/mdit-py-plugins-fixtures-field-list/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/ml150-06/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/ml150-07/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/ml150-08/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/ml198-01/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/ml198-11/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/ml198-12/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/ml247-01/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/ml247-02/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/ml293-06/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/ml293-09/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/ml341-02/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/medusa-inventory-module-tests/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/minethatdata-hillstrom-email-challenge/README.md +0 -4
- campaign_files/2026-10-s-security-detection-2/mitre-brawl-public-game-001/README.md +0 -4
- campaign_files/2026-10-sc-science-reference-data-2/metoffice-cru-crutem5/README.md +0 -4
- campaign_files/2026-10-sc-science-reference-data-2/metoffice-hadisdh-land-q/README.md +0 -4
- campaign_files/2026-10-sc-science-reference-data-2/metoffice-haduk-regional-england-rainfall/README.md +0 -4
- campaign_files/2026-10-sc-science-reference-data/meteoswiss-ogd-smn-ber/README.md +0 -4
- campaign_files/2026-10-sc-science-reference-data/metoffice-hadcrut5/README.md +0 -4
- campaign_files/2026-10-sw-tests-and-exercises-2/medallion-dbt-starter-unit-tests/README.md +0 -4
- campaign_files/2026-10-sw-tests-and-exercises-2/medicare-cclf-connector-unit-tests/README.md +0 -4
- campaign_files/2026-10-sw-tests-and-exercises-2/minibude/README.md +0 -4
- campaign_files/2026-10-sw-tests-and-exercises-2/ml-preprocessing-k-bins-50/README.md +0 -4
CHANGELOG.md
CHANGED
|
@@ -3177,3 +3177,21 @@ Changes to the content of this index, oldest first. There is one entry for each
|
|
| 3177 |
- hf-training-records: refused
|
| 3178 |
- npm: refused
|
| 3179 |
- stackexchange-api-posts: refused
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 3177 |
- hf-training-records: refused
|
| 3178 |
- npm: refused
|
| 3179 |
- stackexchange-api-posts: refused
|
| 3180 |
+
|
| 3181 |
+
## 2026-11-11: sources held back
|
| 3182 |
+
|
| 3183 |
+
- Each source below keeps its newest version that passed every check; its newer batch waits until it passes them:
|
| 3184 |
+
- borealis-dataverse-workbooks-cc-by: changed pointer group file data/borealis-dataverse-workbooks-cc-by/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 2 key(s) of the old version are in no data file of source borealis-dataverse-workbooks-cc-by after the commit (row 4 from batch 2026-10-a-spreadsheets-with-answers, row 5 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3185 |
+
- borealis-dataverse-workbooks-cc0: changed pointer group file data/borealis-dataverse-workbooks-cc0/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source borealis-dataverse-workbooks-cc0 after the commit (row 7 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3186 |
+
- cfpb-complaints: refused
|
| 3187 |
+
- data-gov-uk-workbooks: changed pointer group file data/data-gov-uk-workbooks/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 4 key(s) of the old version are in no data file of source data-gov-uk-workbooks after the commit (row 5 from batch 2026-10-a-spreadsheets-with-answers, row 6 from batch 2026-10-a-spreadsheets-with-answers, row 12 from batch 2026-10-a-spreadsheets-with-answers, 1 more); the removal record holds none of them, and none fails a publish check now
|
| 3188 |
+
- data-gov-uk-workbooks-noassertion: changed pointer group file data/data-gov-uk-workbooks-noassertion/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source data-gov-uk-workbooks-noassertion after the commit (row 6 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3189 |
+
- dataversenl-workbooks-cc-by: changed pointer group file data/dataversenl-workbooks-cc-by/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source dataversenl-workbooks-cc-by after the commit (row 17 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3190 |
+
- dataversenl-workbooks-cc0: changed pointer group file data/dataversenl-workbooks-cc0/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 3 key(s) of the old version are in no data file of source dataversenl-workbooks-cc0 after the commit (row 7 from batch 2026-10-a-spreadsheets-with-answers, row 13 from batch 2026-10-a-spreadsheets-with-answers, row 16 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3191 |
+
- dvn-fvhlgg-repro: changed pointer group file data/dvn-fvhlgg-repro/2026-10-c-repros/part-00000.parquet: 3 key(s) of the old version are in no data file of source dvn-fvhlgg-repro after the commit (row 5 from batch 2026-10-c-repros, row 7 from batch 2026-10-c-repros, row 16 from batch 2026-10-c-repros); the removal record holds none of them, and none fails a publish check now
|
| 3192 |
+
- eu-institution-workbooks-cc-by: changed pointer group file data/eu-institution-workbooks-cc-by/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 3 key(s) of the old version are in no data file of source eu-institution-workbooks-cc-by after the commit (row 2 from batch 2026-10-a-spreadsheets-with-answers, row 4 from batch 2026-10-a-spreadsheets-with-answers, row 5 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3193 |
+
- hdx-workbooks-cc0: changed pointer group file data/hdx-workbooks-cc0/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 2 key(s) of the old version are in no data file of source hdx-workbooks-cc0 after the commit (row 4 from batch 2026-10-a-spreadsheets-with-answers, row 5 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3194 |
+
- hdx-workbooks-odbl: changed pointer group file data/hdx-workbooks-odbl/2026-10-a-spreadsheets-with-answers/part-00000.parquet: 1 key(s) of the old version are in no data file of source hdx-workbooks-odbl after the commit (row 4 from batch 2026-10-a-spreadsheets-with-answers); the removal record holds none of them, and none fails a publish check now
|
| 3195 |
+
- hf-training-records: refused
|
| 3196 |
+
- npm: refused
|
| 3197 |
+
- stackexchange-api-posts: refused
|
README.md
CHANGED
|
@@ -24,25 +24,25 @@ configs:
|
|
| 24 |
<!-- artifact-pointer-layout: v2 -->
|
| 25 |
<!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
|
| 26 |
|
| 27 |
-
<img class="not-prose" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 28 |
|
| 29 |
This dataset is the public index of the **Training Data Foundation**: find public files to build agent tasks and environments from, and fetch them with one command.
|
| 30 |
|
| 31 |
English | [简体中文](README.zh.md) · [Data page](https://huggingface.co/spaces/Battam/training-data-foundation) · [Usage video](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 32 |
|
| 33 |
<picture class="not-prose">
|
| 34 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 35 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 36 |
</picture>
|
| 37 |
<picture class="not-prose">
|
| 38 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 39 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 40 |
</picture>
|
| 41 |
|
| 42 |
## Get data in one command
|
| 43 |
|
| 44 |
```sh
|
| 45 |
-
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 46 |
```
|
| 47 |
|
| 48 |
This fetches 3 units of every spreadsheet material set into `./data`, one folder per unit, and checks each file against the size and hashes its row records.
|
|
@@ -52,7 +52,7 @@ the same command takes the same units of this release.
|
|
| 52 |
<details>
|
| 53 |
<summary>What the command takes, and in which order</summary>
|
| 54 |
|
| 55 |
-
The command and the queries below are pinned to the release tag `release-2026-11-11.
|
| 56 |
[uv](https://docs.astral.sh/uv/) reads the script's dependencies, at the versions published before the day of this release.
|
| 57 |
|
| 58 |
The command returns units: 3 units from each material set whose form is `spreadsheets`, each in a folder of its own named after its `unit_id`.
|
|
@@ -79,7 +79,7 @@ Choose material sets from the catalog with [DuckDB](https://duckdb.org/):
|
|
| 79 |
|
| 80 |
```sql
|
| 81 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 82 |
-
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 83 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 84 |
ORDER BY collection, units DESC;
|
| 85 |
```
|
|
@@ -90,7 +90,7 @@ with `kind = 'corpus'` it returns corpora instead, counted in rows (`files`).
|
|
| 90 |
Choose files in one corpus:
|
| 91 |
|
| 92 |
```sql
|
| 93 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 94 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 95 |
FROM read_parquet(getvariable('files'))
|
| 96 |
WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
@@ -112,12 +112,12 @@ A data file may hold the rows of several sources, so the query keeps this one's
|
|
| 112 |
### Task material: units by collection
|
| 113 |
|
| 114 |
<picture class="not-prose">
|
| 115 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 116 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 117 |
</picture>
|
| 118 |
<picture class="not-prose">
|
| 119 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 120 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 121 |
</picture>
|
| 122 |
|
| 123 |
1,805 material sets with 4,190 units, in 14 collections (1 of them with no material set yet); 1 of the material sets are in no collection.
|
|
@@ -136,7 +136,7 @@ A data file may hold the rows of several sources, so the query keeps this one's
|
|
| 136 |
| Hardware design (EDA) tests | 81 | 258 | 651 | 75 | 80.8 MB | 80.8 MB |
|
| 137 |
| Issue trackers | 212 | 258 | 682 | 212 | 196 MB | 196 MB |
|
| 138 |
| Media and documents | 276 | 391 | 1,088 | 269 | 569 MB | 569 MB |
|
| 139 |
-
| Model serving configurations | 102 | 397 | 1,
|
| 140 |
| Rule calculations | 177 | 329 | 727 | 154 | 196 MB | 186 MB |
|
| 141 |
| Security detection | 110 | 328 | 983 | 77 | 684 MB | 652 MB |
|
| 142 |
| Science reference data | 161 | 342 | 671 | 157 | 63.8 MB | 63.8 MB |
|
|
@@ -150,12 +150,12 @@ Upstreams are the upstream works the material sets of a collection come from.
|
|
| 150 |
### Corpora: rows by main domain
|
| 151 |
|
| 152 |
<picture class="not-prose">
|
| 153 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 154 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 155 |
</picture>
|
| 156 |
<picture class="not-prose">
|
| 157 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 158 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 159 |
</picture>
|
| 160 |
|
| 161 |
139 corpora with 1,216,362,128 rows.
|
|
@@ -188,12 +188,12 @@ Every material set and every corpus, with its counts, size, license tier and log
|
|
| 188 |
## How it is made
|
| 189 |
|
| 190 |
<picture class="not-prose">
|
| 191 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 192 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 193 |
</picture>
|
| 194 |
<picture class="not-prose">
|
| 195 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 196 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 197 |
</picture>
|
| 198 |
|
| 199 |
The terms, each step and how every number is made are folded below.
|
|
@@ -247,9 +247,9 @@ only their sizes add up to the size of the whole index.
|
|
| 247 |
|
| 248 |
| Level | Recorded size | Deduplicated size | Rows read | Rows compared | Rows that match | Rows read, not compared | Rows without a recorded size | Their estimated size |
|
| 249 |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
|
| 250 |
-
| Whole index | 4.45 PB | 4.11 PB | 35,
|
| 251 |
| Corpora | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610 (99.6%) | 871: address unreachable 449, file gone 80, login needed 322, no size from the server 19, other error 1 | 312,300,338 | 202 TB, an estimate (95% range 171 TB to 245 TB), for 215,326,513 of them, from 14,161 rows read |
|
| 252 |
-
| Task material | 2.
|
| 253 |
|
| 254 |
Rows read are the sample of rows the check reads in `meta/sizes.parquet`;
|
| 255 |
a row compared matched its recorded size or did not, and a row read but not compared never reached its file.
|
|
@@ -444,9 +444,9 @@ Every row field and every column of the catalog: [`docs/fields.md`](docs/fields.
|
|
| 444 |
<details>
|
| 445 |
<summary>Releases</summary>
|
| 446 |
|
| 447 |
-
- Latest release: `release-2026-11-11.
|
| 448 |
- Releases are listed in [CHANGELOG.md](CHANGELOG.md);
|
| 449 |
-
each one is a commit with its own release tag (this one is [`release-2026-11-11.
|
| 450 |
so any earlier state stays readable at its tag.
|
| 451 |
- `meta/projection.json` records the release tag and the version of the program and templates that generated this card.
|
| 452 |
- Croissant metadata: [generated by the Hub](https://huggingface.co/api/datasets/Battam/training-data-foundation/croissant);
|
|
@@ -479,7 +479,7 @@ A removal covers the current version of this repository (the main branch) and th
|
|
| 479 |
@misc{training_data_foundation,
|
| 480 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 481 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 482 |
-
note = {Release release-2026-11-11.
|
| 483 |
year = {2026}
|
| 484 |
}
|
| 485 |
```
|
|
|
|
| 24 |
<!-- artifact-pointer-layout: v2 -->
|
| 25 |
<!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
|
| 26 |
|
| 27 |
+
<img class="not-prose" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/banner.svg" alt="Public web, in two layers (task material in collections; corpora), one row per file (address, size, SHA-256, license), your selection, fetched and verified">
|
| 28 |
|
| 29 |
This dataset is the public index of the **Training Data Foundation**: find public files to build agent tasks and environments from, and fetch them with one command.
|
| 30 |
|
| 31 |
English | [简体中文](README.zh.md) · [Data page](https://huggingface.co/spaces/Battam/training-data-foundation) · [Usage video](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 32 |
|
| 33 |
<picture class="not-prose">
|
| 34 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/numbers-narrow-light.svg">
|
| 35 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/numbers-wide-light.svg" alt="1,805 material sets with 4,190 units in 14 collections; 139 corpora with 1,216,362,128 rows; 4.45 PB pointed to, as the index holds addresses, not copies; 99.6% of the 34,707 rows compared match their recorded size.">
|
| 36 |
</picture>
|
| 37 |
<picture class="not-prose">
|
| 38 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/numbers-narrow-dark.svg">
|
| 39 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/numbers-wide-dark.svg" alt="1,805 material sets with 4,190 units in 14 collections; 139 corpora with 1,216,362,128 rows; 4.45 PB pointed to, as the index holds addresses, not copies; 99.6% of the 34,707 rows compared match their recorded size.">
|
| 40 |
</picture>
|
| 41 |
|
| 42 |
## Get data in one command
|
| 43 |
|
| 44 |
```sh
|
| 45 |
+
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/tools/fetch.py --form spreadsheets --sample 3 --out ./data
|
| 46 |
```
|
| 47 |
|
| 48 |
This fetches 3 units of every spreadsheet material set into `./data`, one folder per unit, and checks each file against the size and hashes its row records.
|
|
|
|
| 52 |
<details>
|
| 53 |
<summary>What the command takes, and in which order</summary>
|
| 54 |
|
| 55 |
+
The command and the queries below are pinned to the release tag `release-2026-11-11.14`.
|
| 56 |
[uv](https://docs.astral.sh/uv/) reads the script's dependencies, at the versions published before the day of this release.
|
| 57 |
|
| 58 |
The command returns units: 3 units from each material set whose form is `spreadsheets`, each in a folder of its own named after its `unit_id`.
|
|
|
|
| 79 |
|
| 80 |
```sql
|
| 81 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 82 |
+
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.14/meta/catalog.parquet'
|
| 83 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 84 |
ORDER BY collection, units DESC;
|
| 85 |
```
|
|
|
|
| 90 |
Choose files in one corpus:
|
| 91 |
|
| 92 |
```sql
|
| 93 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.14/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.14/meta/catalog.parquet' WHERE source = 'if-archive'));
|
| 94 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 95 |
FROM read_parquet(getvariable('files'))
|
| 96 |
WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
|
|
| 112 |
### Task material: units by collection
|
| 113 |
|
| 114 |
<picture class="not-prose">
|
| 115 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/material-narrow-light.svg">
|
| 116 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/material-wide-light.svg" alt="Units by collection, longest bar first: Spreadsheets 536; Browser tests 439; Tests and exercises 425; Model serving configurations 397; Media and documents 391; Science reference data 342; Rule calculations 329; Security detection 328; Hardware design (EDA) tests 258; Issue trackers 258; Solver instances 193; Disk images 179; Reproduction packages and runs 106; In no collection 9; SEC filing reviews 0.">
|
| 117 |
</picture>
|
| 118 |
<picture class="not-prose">
|
| 119 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/material-narrow-dark.svg">
|
| 120 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/material-wide-dark.svg" alt="Units by collection, longest bar first: Spreadsheets 536; Browser tests 439; Tests and exercises 425; Model serving configurations 397; Media and documents 391; Science reference data 342; Rule calculations 329; Security detection 328; Hardware design (EDA) tests 258; Issue trackers 258; Solver instances 193; Disk images 179; Reproduction packages and runs 106; In no collection 9; SEC filing reviews 0.">
|
| 121 |
</picture>
|
| 122 |
|
| 123 |
1,805 material sets with 4,190 units, in 14 collections (1 of them with no material set yet); 1 of the material sets are in no collection.
|
|
|
|
| 136 |
| Hardware design (EDA) tests | 81 | 258 | 651 | 75 | 80.8 MB | 80.8 MB |
|
| 137 |
| Issue trackers | 212 | 258 | 682 | 212 | 196 MB | 196 MB |
|
| 138 |
| Media and documents | 276 | 391 | 1,088 | 269 | 569 MB | 569 MB |
|
| 139 |
+
| Model serving configurations | 102 | 397 | 1,165 | 82 | 250 MB | 221 MB |
|
| 140 |
| Rule calculations | 177 | 329 | 727 | 154 | 196 MB | 186 MB |
|
| 141 |
| Security detection | 110 | 328 | 983 | 77 | 684 MB | 652 MB |
|
| 142 |
| Science reference data | 161 | 342 | 671 | 157 | 63.8 MB | 63.8 MB |
|
|
|
|
| 150 |
### Corpora: rows by main domain
|
| 151 |
|
| 152 |
<picture class="not-prose">
|
| 153 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/corpora-narrow-light.svg">
|
| 154 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/corpora-wide-light.svg" alt="Corpus rows by main domain, longest bar first: Data science 750,815,212; System administration 185,826,217; Many domains 109,262,742; Software engineering 45,267,701; Science 44,633,675; Operations 39,404,642; Media 12,751,612; Machine learning 9,636,889; Hardware 8,716,520; Unclassified 5,284,162; Security 4,521,631; Misc 241,125.">
|
| 155 |
</picture>
|
| 156 |
<picture class="not-prose">
|
| 157 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/corpora-narrow-dark.svg">
|
| 158 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/corpora-wide-dark.svg" alt="Corpus rows by main domain, longest bar first: Data science 750,815,212; System administration 185,826,217; Many domains 109,262,742; Software engineering 45,267,701; Science 44,633,675; Operations 39,404,642; Media 12,751,612; Machine learning 9,636,889; Hardware 8,716,520; Unclassified 5,284,162; Security 4,521,631; Misc 241,125.">
|
| 159 |
</picture>
|
| 160 |
|
| 161 |
139 corpora with 1,216,362,128 rows.
|
|
|
|
| 188 |
## How it is made
|
| 189 |
|
| 190 |
<picture class="not-prose">
|
| 191 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/steps-narrow-light.svg">
|
| 192 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/steps-wide-light.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole upstreams into corpora, one row per file or record. 2, admit: works the search found upstream and groups of corpus rows become material sets. 3, check: licenses, personal data, overlap with benchmarks and sizes are checked before release. 4, release: one commit with its own tag, release-2026-11-11.14.">
|
| 193 |
</picture>
|
| 194 |
<picture class="not-prose">
|
| 195 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/steps-narrow-dark.svg">
|
| 196 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/steps-wide-dark.svg" alt="How the index is made, in four steps. 1, collect: collectors read whole upstreams into corpora, one row per file or record. 2, admit: works the search found upstream and groups of corpus rows become material sets. 3, check: licenses, personal data, overlap with benchmarks and sizes are checked before release. 4, release: one commit with its own tag, release-2026-11-11.14.">
|
| 197 |
</picture>
|
| 198 |
|
| 199 |
The terms, each step and how every number is made are folded below.
|
|
|
|
| 247 |
|
| 248 |
| Level | Recorded size | Deduplicated size | Rows read | Rows compared | Rows that match | Rows read, not compared | Rows without a recorded size | Their estimated size |
|
| 249 |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
|
| 250 |
+
| Whole index | 4.45 PB | 4.11 PB | 35,586 | 34,707 | 34,578 (99.6%) | 879: address unreachable 449, file gone 80, login needed 329, no size from the server 19, other error 2 | 312,300,338 | 202 TB, an estimate (95% range 171 TB to 245 TB), for 215,326,513 of them, from 14,161 rows read |
|
| 251 |
| Corpora | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610 (99.6%) | 871: address unreachable 449, file gone 80, login needed 322, no size from the server 19, other error 1 | 312,300,338 | 202 TB, an estimate (95% range 171 TB to 245 TB), for 215,326,513 of them, from 14,161 rows read |
|
| 252 |
+
| Task material | 2.88 GB | 2.81 GB | 3,992 | 3,984 | 3,968 (99.6%) | 8: login needed 7, other error 1 | 0 | none |
|
| 253 |
|
| 254 |
Rows read are the sample of rows the check reads in `meta/sizes.parquet`;
|
| 255 |
a row compared matched its recorded size or did not, and a row read but not compared never reached its file.
|
|
|
|
| 444 |
<details>
|
| 445 |
<summary>Releases</summary>
|
| 446 |
|
| 447 |
+
- Latest release: `release-2026-11-11.14` (its newest CHANGELOG entry is dated 2026-11-11).
|
| 448 |
- Releases are listed in [CHANGELOG.md](CHANGELOG.md);
|
| 449 |
+
each one is a commit with its own release tag (this one is [`release-2026-11-11.14`](https://huggingface.co/datasets/Battam/training-data-foundation/tree/release-2026-11-11.14)),
|
| 450 |
so any earlier state stays readable at its tag.
|
| 451 |
- `meta/projection.json` records the release tag and the version of the program and templates that generated this card.
|
| 452 |
- Croissant metadata: [generated by the Hub](https://huggingface.co/api/datasets/Battam/training-data-foundation/croissant);
|
|
|
|
| 479 |
@misc{training_data_foundation,
|
| 480 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 481 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 482 |
+
note = {Release release-2026-11-11.14},
|
| 483 |
year = {2026}
|
| 484 |
}
|
| 485 |
```
|
README.zh.md
CHANGED
|
@@ -11,25 +11,25 @@ tags:
|
|
| 11 |
---
|
| 12 |
<!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
|
| 13 |
|
| 14 |
-
<img class="not-prose" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 15 |
|
| 16 |
本数据集是**数据基座**的公开索引:在这里找到可以用来构建智能体任务和环境的公开文件,并用一条命令把它们取下来。
|
| 17 |
|
| 18 |
[English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/training-data-foundation) · [使用示例视频](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 19 |
|
| 20 |
<picture class="not-prose">
|
| 21 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 22 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 23 |
</picture>
|
| 24 |
<picture class="not-prose">
|
| 25 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 26 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 27 |
</picture>
|
| 28 |
|
| 29 |
## 一条命令取数据
|
| 30 |
|
| 31 |
```sh
|
| 32 |
-
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 33 |
```
|
| 34 |
|
| 35 |
这条命令从每个电子表格材料集各取 3 个单元放进 `./data`,每个单元一个文件夹,并按每个文件所在行记录的大小和哈希值校验它。
|
|
@@ -39,7 +39,7 @@ uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/r
|
|
| 39 |
<details>
|
| 40 |
<summary>命令取什么、按什么顺序取</summary>
|
| 41 |
|
| 42 |
-
这条命令和下面的查询都固定在发布标签 `release-2026-11-11.
|
| 43 |
[uv](https://docs.astral.sh/uv/) 会读取脚本声明的依赖,取这个发布当天之前发布的版本。
|
| 44 |
|
| 45 |
命令返回单元:形式为 `spreadsheets` 的每个材料集各 3 个单元,每个单元放在以它的 `unit_id` 命名的单独文件夹里。
|
|
@@ -66,7 +66,7 @@ uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/r
|
|
| 66 |
|
| 67 |
```sql
|
| 68 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 69 |
-
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 70 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 71 |
ORDER BY collection, units DESC;
|
| 72 |
```
|
|
@@ -77,7 +77,7 @@ ORDER BY collection, units DESC;
|
|
| 77 |
在一个语料库里挑选文件:
|
| 78 |
|
| 79 |
```sql
|
| 80 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.
|
| 81 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 82 |
FROM read_parquet(getvariable('files'))
|
| 83 |
WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
@@ -99,12 +99,12 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 99 |
### 任务材料:按合集的单元数
|
| 100 |
|
| 101 |
<picture class="not-prose">
|
| 102 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 103 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 104 |
</picture>
|
| 105 |
<picture class="not-prose">
|
| 106 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 107 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 108 |
</picture>
|
| 109 |
|
| 110 |
1,805 个材料集,共 4,190 个单元,分在 14 个合集中(其中 1 个合集还没有材料集);其中 1 个材料集不属于任何合集。
|
|
@@ -123,7 +123,7 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 123 |
| 硬件设计(EDA)测试 | 81 | 258 | 651 | 75 | 80.8 MB | 80.8 MB |
|
| 124 |
| 问题跟踪系统 | 212 | 258 | 682 | 212 | 196 MB | 196 MB |
|
| 125 |
| 媒体和文档 | 276 | 391 | 1,088 | 269 | 569 MB | 569 MB |
|
| 126 |
-
| 模型服务配置 | 102 | 397 | 1,
|
| 127 |
| 规则计算 | 177 | 329 | 727 | 154 | 196 MB | 186 MB |
|
| 128 |
| 安全检测 | 110 | 328 | 983 | 77 | 684 MB | 652 MB |
|
| 129 |
| 科学参考数据 | 161 | 342 | 671 | 157 | 63.8 MB | 63.8 MB |
|
|
@@ -137,12 +137,12 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 137 |
### 语料库:按主要领域的行数
|
| 138 |
|
| 139 |
<picture class="not-prose">
|
| 140 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 141 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 142 |
</picture>
|
| 143 |
<picture class="not-prose">
|
| 144 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 145 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 146 |
</picture>
|
| 147 |
|
| 148 |
139 个语料库,共 1,216,362,128 行。
|
|
@@ -175,12 +175,12 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 175 |
## 怎样做成
|
| 176 |
|
| 177 |
<picture class="not-prose">
|
| 178 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 179 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 180 |
</picture>
|
| 181 |
<picture class="not-prose">
|
| 182 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 183 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.
|
| 184 |
</picture>
|
| 185 |
|
| 186 |
术语、每一步,以及每个数字怎样得出,都折叠在下面。
|
|
@@ -234,9 +234,9 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 234 |
|
| 235 |
| 层级 | 记录的大小 | 去重后大小 | 读过的行 | 比对过的行 | 一致的行 | 读过但未比对的行 | 没有记录大小的行 | 这些行的估计大小 |
|
| 236 |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
|
| 237 |
-
| 整个索引 | 4.45 PB | 4.11 PB | 35,
|
| 238 |
| 语料库 | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610(99.6%) | 871:地址无法访问 449 行、文件已不存在 80 行、需要登录 322 行、服务器未给出大小 19 行、其他错误 1 行 | 312,300,338 | 202 TB,这是估计值(95% 范围 171 TB 到 245 TB),针对其中 215,326,513 行,依据读过的 14,161 行 |
|
| 239 |
-
| 任务材料 | 2.
|
| 240 |
|
| 241 |
读过的行是核对在 `meta/sizes.parquet` 中读取的抽样行;
|
| 242 |
比对过的行与记录的大小一致或不一致,读过但未比对的行没有取到它的文件。
|
|
@@ -433,9 +433,9 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 433 |
<details>
|
| 434 |
<summary>发布</summary>
|
| 435 |
|
| 436 |
-
- 最新发布:`release-2026-11-11.
|
| 437 |
- 各次发布列在 [CHANGELOG.md](CHANGELOG.md) 中;
|
| 438 |
-
每次发布是一个带有自己发布标签的提交(本次为 [`release-2026-11-11.
|
| 439 |
因此任何较早的状态都可以在它的标签处读到。
|
| 440 |
- `meta/projection.json` 记录发布标签,以及生成本卡片的程序和模板的版本。
|
| 441 |
- Croissant 元数据:[由 Hub 生成](https://huggingface.co/api/datasets/Battam/training-data-foundation/croissant);
|
|
@@ -476,7 +476,7 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 476 |
@misc{training_data_foundation,
|
| 477 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 478 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 479 |
-
note = {Release release-2026-11-11.
|
| 480 |
year = {2026}
|
| 481 |
}
|
| 482 |
```
|
|
|
|
| 11 |
---
|
| 12 |
<!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
|
| 13 |
|
| 14 |
+
<img class="not-prose" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/banner.zh.svg" alt="公开网络,分两层(按合集的任务材料;语料库),每个文件一行(地址、大小、SHA-256、许可证),你的选择,下载并校验">
|
| 15 |
|
| 16 |
本数据集是**数据基座**的公开索引:在这里找到可以用来构建智能体任务和环境的公开文件,并用一条命令把它们取下来。
|
| 17 |
|
| 18 |
[English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/training-data-foundation) · [使用示例视频](https://huggingface.co/spaces/Battam/training-data-foundation#usage-video)
|
| 19 |
|
| 20 |
<picture class="not-prose">
|
| 21 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/numbers-narrow-light.zh.svg">
|
| 22 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/numbers-wide-light.zh.svg" alt="1,805 个材料集,共 4,190 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 34,707 行中,99.6% 与记录的大小一致。">
|
| 23 |
</picture>
|
| 24 |
<picture class="not-prose">
|
| 25 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/numbers-narrow-dark.zh.svg">
|
| 26 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/numbers-wide-dark.zh.svg" alt="1,805 个材料集,共 4,190 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 34,707 行中,99.6% 与记录的大小一致。">
|
| 27 |
</picture>
|
| 28 |
|
| 29 |
## 一条命令取数据
|
| 30 |
|
| 31 |
```sh
|
| 32 |
+
uv run https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/tools/fetch.py --form spreadsheets --sample 3 --out ./data
|
| 33 |
```
|
| 34 |
|
| 35 |
这条命令从每个电子表格材料集各取 3 个单元放进 `./data`,每个单元一个文件夹,并按每个文件所在行记录的大小和哈希值校验它。
|
|
|
|
| 39 |
<details>
|
| 40 |
<summary>命令取什么、按什么顺序取</summary>
|
| 41 |
|
| 42 |
+
这条命令和下面的查询都固定在发布标签 `release-2026-11-11.14` 上。
|
| 43 |
[uv](https://docs.astral.sh/uv/) 会读取脚本声明的依赖,取这个发布当天之前发布的版本。
|
| 44 |
|
| 45 |
命令返回单元:形式为 `spreadsheets` 的每个材料集各 3 个单元,每个单元放在以它的 `unit_id` 命名的单独文件夹里。
|
|
|
|
| 66 |
|
| 67 |
```sql
|
| 68 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 69 |
+
FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.14/meta/catalog.parquet'
|
| 70 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 71 |
ORDER BY collection, units DESC;
|
| 72 |
```
|
|
|
|
| 77 |
在一个语料库里挑选文件:
|
| 78 |
|
| 79 |
```sql
|
| 80 |
+
SET VARIABLE files = (SELECT list('hf://datasets/Battam/training-data-foundation@release-2026-11-11.14/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.14/meta/catalog.parquet' WHERE source = 'if-archive'));
|
| 81 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 82 |
FROM read_parquet(getvariable('files'))
|
| 83 |
WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
|
|
| 99 |
### 任务材料:按合集的单元数
|
| 100 |
|
| 101 |
<picture class="not-prose">
|
| 102 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/material-narrow-light.zh.svg">
|
| 103 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/material-wide-light.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 397;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 193;磁盘镜像 179;复现包和运行 106;不属于任何合集 9;SEC 申报审查 0。">
|
| 104 |
</picture>
|
| 105 |
<picture class="not-prose">
|
| 106 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/material-narrow-dark.zh.svg">
|
| 107 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/material-wide-dark.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 397;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 193;磁盘镜像 179;复现包和运行 106;不属于任何合集 9;SEC 申报审查 0。">
|
| 108 |
</picture>
|
| 109 |
|
| 110 |
1,805 个材料集,共 4,190 个单元,分在 14 个合集中(其中 1 个合集还没有材料集);其中 1 个材料集不属于任何合集。
|
|
|
|
| 123 |
| 硬件设计(EDA)测试 | 81 | 258 | 651 | 75 | 80.8 MB | 80.8 MB |
|
| 124 |
| 问题跟踪系统 | 212 | 258 | 682 | 212 | 196 MB | 196 MB |
|
| 125 |
| 媒体和文档 | 276 | 391 | 1,088 | 269 | 569 MB | 569 MB |
|
| 126 |
+
| 模型服务配置 | 102 | 397 | 1,165 | 82 | 250 MB | 221 MB |
|
| 127 |
| 规则计算 | 177 | 329 | 727 | 154 | 196 MB | 186 MB |
|
| 128 |
| 安全检测 | 110 | 328 | 983 | 77 | 684 MB | 652 MB |
|
| 129 |
| 科学参考数据 | 161 | 342 | 671 | 157 | 63.8 MB | 63.8 MB |
|
|
|
|
| 137 |
### 语料库:按主要领域的行数
|
| 138 |
|
| 139 |
<picture class="not-prose">
|
| 140 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/corpora-narrow-light.zh.svg">
|
| 141 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/corpora-wide-light.zh.svg" alt="按主要领域的语料库行数,条形由长到短:数据科学 750,815,212;系统管理 185,826,217;多领域 109,262,742;软件工程 45,267,701;科学 44,633,675;运营 39,404,642;媒体 12,751,612;机器学习 9,636,889;硬件 8,716,520;未分类 5,284,162;安全 4,521,631;杂项 241,125。">
|
| 142 |
</picture>
|
| 143 |
<picture class="not-prose">
|
| 144 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/corpora-narrow-dark.zh.svg">
|
| 145 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/corpora-wide-dark.zh.svg" alt="按主要领域的语料库行数,条形由长到短:数据科学 750,815,212;系统管理 185,826,217;多领域 109,262,742;软件工程 45,267,701;科学 44,633,675;运营 39,404,642;媒体 12,751,612;机器学习 9,636,889;硬件 8,716,520;未分类 5,284,162;安全 4,521,631;杂项 241,125。">
|
| 146 |
</picture>
|
| 147 |
|
| 148 |
139 个语料库,共 1,216,362,128 行。
|
|
|
|
| 175 |
## 怎样做成
|
| 176 |
|
| 177 |
<picture class="not-prose">
|
| 178 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/steps-narrow-light.zh.svg">
|
| 179 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/steps-wide-light.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.14。">
|
| 180 |
</picture>
|
| 181 |
<picture class="not-prose">
|
| 182 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/steps-narrow-dark.zh.svg">
|
| 183 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/training-data-foundation/resolve/release-2026-11-11.14/docs/figures/steps-wide-dark.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.14。">
|
| 184 |
</picture>
|
| 185 |
|
| 186 |
术语、每一步,以及每个数字怎样得出,都折叠在下面。
|
|
|
|
| 234 |
|
| 235 |
| 层级 | 记录的大小 | 去重后大小 | 读过的行 | 比对过的行 | 一致的行 | 读过但未比对的行 | 没有记录大小的行 | 这些行的估计大小 |
|
| 236 |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
|
| 237 |
+
| 整个索引 | 4.45 PB | 4.11 PB | 35,586 | 34,707 | 34,578(99.6%) | 879:地址无法访问 449 行、文件已不存在 80 行、需要登录 329 行、服务器未给出大小 19 行、其他错误 2 行 | 312,300,338 | 202 TB,这是估计值(95% 范围 171 TB 到 245 TB),针对其中 215,326,513 行,依据读过的 14,161 行 |
|
| 238 |
| 语料库 | 4.45 PB | 4.11 PB | 31,594 | 30,723 | 30,610(99.6%) | 871:地址无法访问 449 行、文件已不存在 80 行、需要登录 322 行、服务器未给出大小 19 行、其他错误 1 行 | 312,300,338 | 202 TB,这是估计值(95% 范围 171 TB 到 245 TB),针对其中 215,326,513 行,依据读过的 14,161 行 |
|
| 239 |
+
| 任务材料 | 2.88 GB | 2.81 GB | 3,992 | 3,984 | 3,968(99.6%) | 8:需要登录 7 行、其他错误 1 行 | 0 | 无 |
|
| 240 |
|
| 241 |
读过的行是核对在 `meta/sizes.parquet` 中读取的抽样行;
|
| 242 |
比对过的行与记录的大小一致或不一致,读过但未比对的行没有取到它的文件。
|
|
|
|
| 433 |
<details>
|
| 434 |
<summary>发布</summary>
|
| 435 |
|
| 436 |
+
- 最新发布:`release-2026-11-11.14`(其最新的 CHANGELOG 条目日期为 2026-11-11)。
|
| 437 |
- 各次发布列在 [CHANGELOG.md](CHANGELOG.md) 中;
|
| 438 |
+
每次发布是一个带有自己发布标签的提交(本次为 [`release-2026-11-11.14`](https://huggingface.co/datasets/Battam/training-data-foundation/tree/release-2026-11-11.14)),
|
| 439 |
因此任何较早的状态都可以在它的标签处读到。
|
| 440 |
- `meta/projection.json` 记录发布标签,以及生成本卡片的程序和模板的版本。
|
| 441 |
- Croissant 元数据:[由 Hub 生成](https://huggingface.co/api/datasets/Battam/training-data-foundation/croissant);
|
|
|
|
| 476 |
@misc{training_data_foundation,
|
| 477 |
title = {training-data-foundation: an index of public materials for building agent environments},
|
| 478 |
howpublished = {https://huggingface.co/datasets/Battam/training-data-foundation},
|
| 479 |
+
note = {Release release-2026-11-11.14},
|
| 480 |
year = {2026}
|
| 481 |
}
|
| 482 |
```
|
campaign_files/2026-10-c-repros-2/mertens-ap-constants-repro/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** Each unit with an answer has one answer file, at answer/<package>/reported.json.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Open with tools for these file types: .py.
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Open with tools for these file types: .py.
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
campaign_files/2026-10-c-repros-2/mertens-zeta-reciprocal-repro/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** Each unit with an answer has one answer file, at answer/<package>/reported.json.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Open with tools for these file types: .py.
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Open with tools for these file types: .py.
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
campaign_files/2026-10-g-solver-instances-2/maze-curriculum-dataset/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Path (move string) from S to E. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Simulate the agent move string: each letter moves one cell, i.e. two characters in the ASCII grid, and the passage character between must not be #; accept when the walk ends on E. Note: the README example uses one-character steps and does not match the data; the two-character rule is what the data follows.
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `data/train-00000-of-00001.parquet`: Maze Navigation Curriculum Dataset: 60,000 ASCII perfect mazes (5x5, 7x7, 9x9 cells) with solution move strings.
|
| 22 |
Format: Parquet: prompt, maze (ASCII, # wall, S start, E end), solution (N/S/E/W string), grid_size; delivered whole as the upstream file; a case is one row
|
| 23 |
Origin: maze set published as-is on Hugging Face by selimaktas, made by the publisher with Wilson's algorithm (was procedurally_generated)
|
| 24 |
-
Reference result: path (move string) from S to E
|
| 25 |
-
Reference source: README: generated with Wilson algorithm, each maze has exactly one solution path; the solution field is that path.
|
| 26 |
Check: Simulate the agent move string: each letter moves one cell, i.e. two characters in the ASCII grid, and the passage character between must not be #; accept when the walk ends on E. Note: the README example uses one-character steps and does not match the data; the two-character rule is what the data follows.
|
| 27 |
Dependencies: not packed; pyarrow 21.0.0 (the version this re-check read the file with) to read the Parquet unit; not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Simulate the agent move string: each letter moves one cell, i.e. two characters in the ASCII grid, and the passage character between must not be #; accept when the walk ends on E. Note: the README example uses one-character steps and does not match the data; the two-character rule is what the data follows.
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `data/train-00000-of-00001.parquet`: Maze Navigation Curriculum Dataset: 60,000 ASCII perfect mazes (5x5, 7x7, 9x9 cells) with solution move strings.
|
| 20 |
Format: Parquet: prompt, maze (ASCII, # wall, S start, E end), solution (N/S/E/W string), grid_size; delivered whole as the upstream file; a case is one row
|
| 21 |
Origin: maze set published as-is on Hugging Face by selimaktas, made by the publisher with Wilson's algorithm (was procedurally_generated)
|
|
|
|
|
|
|
| 22 |
Check: Simulate the agent move string: each letter moves one cell, i.e. two characters in the ASCII grid, and the passage character between must not be #; accept when the walk ends on E. Note: the README example uses one-character steps and does not match the data; the two-character rule is what the data follows.
|
| 23 |
Dependencies: not packed; pyarrow 21.0.0 (the version this re-check read the file with) to read the Parquet unit; not packed
|
campaign_files/2026-10-g-solver-instances-2/minlplib/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Proven optimal objective value (=opt=) with an optimal point. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Open with tools for these file types: .gms.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `gms/ex1221.gms`: MINLPLib instance ex1221: small mixed-integer nonlinear program (3 continuous, 3 binary variables) with proven optimum 7.66718.
|
| 22 |
Format: GAMS scalar model (.gms); companions: sol/ex1221.p1.sol (point) and minlplib.solu (=opt=, =best=, =bestdual= lines for all instances)
|
| 23 |
Origin: textbook model (Floudas-style example) collected in MINLPLib
|
| 24 |
-
Reference result: proven optimal objective value (=opt=) with an optimal point
|
| 25 |
-
Reference source: minlplib.solu line 429: "=opt= ex1221 7.6671800690"; sol/ex1221.p1.sol gives the point. The FAQ says the bounds are not a solver ranking.
|
| 26 |
Companions (not included): sol/ex1221.p1.sol; minlplib.solu
|
| 27 |
Dependencies: not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Open with tools for these file types: .gms.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 19 |
- `gms/ex1221.gms`: MINLPLib instance ex1221: small mixed-integer nonlinear program (3 continuous, 3 binary variables) with proven optimum 7.66718.
|
| 20 |
Format: GAMS scalar model (.gms); companions: sol/ex1221.p1.sol (point) and minlplib.solu (=opt=, =best=, =bestdual= lines for all instances)
|
| 21 |
Origin: textbook model (Floudas-style example) collected in MINLPLib
|
|
|
|
|
|
|
| 22 |
Companions (not included): sol/ex1221.p1.sol; minlplib.solu
|
| 23 |
Dependencies: not packed
|
campaign_files/2026-10-gt-browser-tests-2/mblaze-mflag/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_values_in_test. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** mblaze mflag (or a script that renames Maildir files per the Maildir info suffix ":2,FLAGS", Python mailbox.Maildir set_flags); the final state is the file name in inbox/cur
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC0-1.0
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `t/8000-mflag.t`: Set and clear Maildir flags (Seen, Replied, Flagged, Trashed) on a message and keep the flag letters in sorted order in the file name.
|
| 22 |
Format: shell test that builds a two-message Maildir; the expected file names after each step are the answer
|
| 23 |
Origin: mblaze test script (tool_fixture); the Maildir is built by the script itself
|
| 24 |
-
Reference result: expected_values_in_test
|
| 25 |
-
Reference source: t/8000-mflag.t lines 22-37: after mflag -S the file is inbox/cur/1:2,S; after -R 1:2,RS; after -r 1:2,S; after -F 1:2,FS; after -f 1:2,S; after -s 1:2,; after -T 1:2,T; after -t 1:2.
|
| 26 |
Check: Final file state: after each step the Maildir holds inbox/cur/1:2,<flags> with exactly the expected flag letters (test -e of the expected name, lines 22-36), and the sequence file still lists 2 messages (check_test lines 23-37). No screenshot
|
| 27 |
Tools: mblaze mflag (or a script that renames Maildir files per the Maildir info suffix ":2,FLAGS", Python mailbox.Maildir set_flags); the final state is the file name in inbox/cur
|
| 28 |
Companions (not included): t/lib.sh (plan, check, check_test helpers); COPYING
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** mblaze mflag (or a script that renames Maildir files per the Maildir info suffix ":2,FLAGS", Python mailbox.Maildir set_flags); the final state is the file name in inbox/cur
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC0-1.0
|
|
|
|
| 19 |
- `t/8000-mflag.t`: Set and clear Maildir flags (Seen, Replied, Flagged, Trashed) on a message and keep the flag letters in sorted order in the file name.
|
| 20 |
Format: shell test that builds a two-message Maildir; the expected file names after each step are the answer
|
| 21 |
Origin: mblaze test script (tool_fixture); the Maildir is built by the script itself
|
|
|
|
|
|
|
| 22 |
Check: Final file state: after each step the Maildir holds inbox/cur/1:2,<flags> with exactly the expected flag letters (test -e of the expected name, lines 22-36), and the sequence file still lists 2 messages (check_test lines 23-37). No screenshot
|
| 23 |
Tools: mblaze mflag (or a script that renames Maildir files per the Maildir info suffix ":2,FLAGS", Python mailbox.Maildir set_flags); the final state is the file name in inbox/cur
|
| 24 |
Companions (not included): t/lib.sh (plan, check, check_test helpers); COPYING
|
campaign_files/2026-10-gt-browser-tests-2/mergecal-calendar-colours/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_values_in_test_code. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Python icalendar: a script copies the calendar colour onto components that have none, merges the calendars and writes the result; the colours are read back from the file
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-3.0-only
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/calendars/color_rfc7986.ics`: Merge calendars coloured in RFC 7986 and Apple styles and keep each component colour.
|
| 22 |
Format: 2 iCalendar files; expected values in a pytest file
|
| 23 |
Origin: python-mergecal test fixture (tool_fixture)
|
| 24 |
-
Reference result: expected_values_in_test_code
|
| 25 |
-
Reference source: tests/test_color_merging.py lines 6-30: every VEVENT, VTODO and VJOURNAL of color_rfc7986 gets COLOR turquoise; the event of color_apple gets #e78074; merging rfc7986 then apple gives calendar COLOR turquoise (first wins)
|
| 26 |
Check: Final file state: in the written .ics the calendar COLOR is turquoise, each component from color_rfc7986 has COLOR turquoise and the Apple event has COLOR #e78074. No screenshot
|
| 27 |
Tools: Python icalendar: a script copies the calendar colour onto components that have none, merges the calendars and writes the result; the colours are read back from the file
|
| 28 |
Companions (not included): tests/calendars/color_apple.ics; tests/test_color_merging.py; tests/conftest.py; LICENSE
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Python icalendar: a script copies the calendar colour onto components that have none, merges the calendars and writes the result; the colours are read back from the file
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-3.0-only
|
|
|
|
| 19 |
- `tests/calendars/color_rfc7986.ics`: Merge calendars coloured in RFC 7986 and Apple styles and keep each component colour.
|
| 20 |
Format: 2 iCalendar files; expected values in a pytest file
|
| 21 |
Origin: python-mergecal test fixture (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: Final file state: in the written .ics the calendar COLOR is turquoise, each component from color_rfc7986 has COLOR turquoise and the Apple event has COLOR #e78074. No screenshot
|
| 23 |
Tools: Python icalendar: a script copies the calendar colour onto components that have none, merges the calendars and writes the result; the colours are read back from the file
|
| 24 |
Companions (not included): tests/calendars/color_apple.ics; tests/test_color_merging.py; tests/conftest.py; LICENSE
|
campaign_files/2026-10-gt-browser-tests-2/mergecal-no-uids/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_values_in_test_code. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Python icalendar: a script merges the file and writes the result; the events are counted in the output
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-3.0-only
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/calendars/no_uids_calendar.ics`: Merge a calendar whose events have no UID without dropping or inventing identifiers.
|
| 22 |
Format: 1 iCalendar file; expected values in a pytest file
|
| 23 |
Origin: python-mergecal test fixture (tool_fixture)
|
| 24 |
-
Reference result: expected_values_in_test_code
|
| 25 |
-
Reference source: tests/test_merge_calendars_with_no_uids.py lines 4-22: the merge keeps 3 events with sorted summaries "Event with no UID 1", "... 2", "... 3", none with a UID
|
| 26 |
Check: Final file state: the written .ics holds exactly 3 VEVENTs with those summaries and none has a UID property (no invented UIDs). No screenshot
|
| 27 |
Tools: Python icalendar: a script merges the file and writes the result; the events are counted in the output
|
| 28 |
Companions (not included): tests/test_merge_calendars_with_no_uids.py; tests/conftest.py; LICENSE
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Python icalendar: a script merges the file and writes the result; the events are counted in the output
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-3.0-only
|
|
|
|
| 19 |
- `tests/calendars/no_uids_calendar.ics`: Merge a calendar whose events have no UID without dropping or inventing identifiers.
|
| 20 |
Format: 1 iCalendar file; expected values in a pytest file
|
| 21 |
Origin: python-mergecal test fixture (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: Final file state: the written .ics holds exactly 3 VEVENTs with those summaries and none has a UID property (no invented UIDs). No screenshot
|
| 23 |
Tools: Python icalendar: a script merges the file and writes the result; the events are counted in the output
|
| 24 |
Companions (not included): tests/test_merge_calendars_with_no_uids.py; tests/conftest.py; LICENSE
|
campaign_files/2026-10-gt-browser-tests-2/mergecal-recurring-with-override/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_values_in_test_code. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Python icalendar (or the mergecal command line): a script merges the two .ics files and writes the merged calendar to a file
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-3.0-only
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/calendars/four_week_recurring.ics`: Merge two exports of a recurring meeting where one occurrence was edited.
|
| 22 |
Format: 2 iCalendar files; expected values in a pytest file
|
| 23 |
Origin: python-mergecal test fixture (tool_fixture)
|
| 24 |
-
Reference result: expected_values_in_test_code
|
| 25 |
-
Reference source: tests/test_merge_calendars.py lines 13-39: the merged calendar has 2 VEVENTs, 1 with RRULE and 1 with RECURRENCE-ID; their summaries differ and the RECURRENCE-ID event has the higher SEQUENCE
|
| 26 |
Check: Final file state: parse the written .ics; it must hold exactly 2 VEVENTs, exactly 1 with RRULE and 1 with RECURRENCE-ID, different SUMMARY values, and SEQUENCE of the modified one greater than the series. No screenshot
|
| 27 |
Tools: Python icalendar (or the mergecal command line): a script merges the two .ics files and writes the merged calendar to a file
|
| 28 |
Companions (not included): tests/calendars/four_week_recurring_with_recurrence_id.ics; tests/test_merge_calendars.py; tests/conftest.py; LICENSE
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Python icalendar (or the mergecal command line): a script merges the two .ics files and writes the merged calendar to a file
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-3.0-only
|
|
|
|
| 19 |
- `tests/calendars/four_week_recurring.ics`: Merge two exports of a recurring meeting where one occurrence was edited.
|
| 20 |
Format: 2 iCalendar files; expected values in a pytest file
|
| 21 |
Origin: python-mergecal test fixture (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: Final file state: parse the written .ics; it must hold exactly 2 VEVENTs, exactly 1 with RRULE and 1 with RECURRENCE-ID, different SUMMARY values, and SEQUENCE of the modified one greater than the series. No screenshot
|
| 23 |
Tools: Python icalendar (or the mergecal command line): a script merges the two .ics files and writes the merged calendar to a file
|
| 24 |
Companions (not included): tests/calendars/four_week_recurring_with_recurrence_id.ics; tests/test_merge_calendars.py; tests/conftest.py; LICENSE
|
campaign_files/2026-10-gt-browser-tests-2/mergecal-two-vcalendars/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_values_in_test_code. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Python icalendar (Calendar.from_ical with multiple=True): a script reads both calendars, merges them and writes the merged .ics
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-3.0-only
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/calendars/two_vcalendars.ics`: Merge a file that holds two VCALENDAR blocks without duplicating events.
|
| 22 |
Format: 1 iCalendar file with 2 VCALENDAR objects; expected values in a pytest file
|
| 23 |
Origin: python-mergecal test fixture (tool_fixture)
|
| 24 |
-
Reference result: expected_values_in_test_code
|
| 25 |
-
Reference source: tests/test_multiple_vcalendars.py lines 21-46: the file parses to 2 calendars; the merge holds summaries {Event A, Event B}; merging the file with itself gives the same result
|
| 26 |
Check: Final file state: the written .ics parses to one calendar whose VEVENT summaries are exactly {Event A, Event B} with no duplicates. No screenshot
|
| 27 |
Tools: Python icalendar (Calendar.from_ical with multiple=True): a script reads both calendars, merges them and writes the merged .ics
|
| 28 |
Companions (not included): tests/test_multiple_vcalendars.py; tests/conftest.py; LICENSE
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Python icalendar (Calendar.from_ical with multiple=True): a script reads both calendars, merges them and writes the merged .ics
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-3.0-only
|
|
|
|
| 19 |
- `tests/calendars/two_vcalendars.ics`: Merge a file that holds two VCALENDAR blocks without duplicating events.
|
| 20 |
Format: 1 iCalendar file with 2 VCALENDAR objects; expected values in a pytest file
|
| 21 |
Origin: python-mergecal test fixture (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: Final file state: the written .ics parses to one calendar whose VEVENT summaries are exactly {Event A, Event B} with no duplicates. No screenshot
|
| 23 |
Tools: Python icalendar (Calendar.from_ical with multiple=True): a script reads both calendars, merges them and writes the merged .ics
|
| 24 |
Companions (not included): tests/test_multiple_vcalendars.py; tests/conftest.py; LICENSE
|
campaign_files/2026-10-gt-browser-tests-2/mimekit-mbox/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: golden_output_files. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** MimeKit MimeParser with MimeFormat.Mbox from a .NET script, or Python mailbox.mbox plus email.parser; the script writes a per-message summary of headers and MIME structure, and the byte offsets of each message, headers and body
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `UnitTests/TestData/mbox/issue1189.mbox.txt`: Split an mbox whose bodies hold unescaped From lines (MimeKit issue 1189) and report each message structure and byte offsets.
|
| 22 |
Format: mbox (.mbox.txt) as input; text summary and JSON offsets list as answers
|
| 23 |
Origin: MimeKit regression fixture for issue 1189 (tool_fixture)
|
| 24 |
-
Reference result: golden_output_files
|
| 25 |
-
Reference source: UnitTests/TestData/mbox/issue1189-summary.txt (compared at MimeParserTests.cs line 5867) and issue1189.unix-offsets.json (lines 5904-5918); the parser must also write the messages back so the output equals the original mbox byte for byte
|
| 26 |
Check: Final file state: (1) the summary the agent writes equals issue1189-summary.txt after CRLF to LF (MimeParserTests.cs lines 5862-5867); (2) the offsets list has the same count as issue1189.unix-offsets.json and each message offset, header offset, body offset and line number is equal (lines 5915-5918, AssertMimeOffsets). The summary format is MimeKit specific; for other tools the judge compares message count and per-message offsets only. No screenshot
|
| 27 |
Tools: MimeKit MimeParser with MimeFormat.Mbox from a .NET script, or Python mailbox.mbox plus email.parser; the script writes a per-message summary of headers and MIME structure, and the byte offsets of each message, headers and body
|
| 28 |
Companions (not included): UnitTests/TestData/mbox/issue1189-summary.txt (golden structure summary; hide); UnitTests/TestData/mbox/issue1189.unix-offsets.json (golden offsets with LF line endings; hide); UnitTests/MimeParserTests.cs (AssertMboxResults, TestMbox, TestIssue1189Mbox); LICENSE
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** MimeKit MimeParser with MimeFormat.Mbox from a .NET script, or Python mailbox.mbox plus email.parser; the script writes a per-message summary of headers and MIME structure, and the byte offsets of each message, headers and body
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `UnitTests/TestData/mbox/issue1189.mbox.txt`: Split an mbox whose bodies hold unescaped From lines (MimeKit issue 1189) and report each message structure and byte offsets.
|
| 20 |
Format: mbox (.mbox.txt) as input; text summary and JSON offsets list as answers
|
| 21 |
Origin: MimeKit regression fixture for issue 1189 (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: Final file state: (1) the summary the agent writes equals issue1189-summary.txt after CRLF to LF (MimeParserTests.cs lines 5862-5867); (2) the offsets list has the same count as issue1189.unix-offsets.json and each message offset, header offset, body offset and line number is equal (lines 5915-5918, AssertMimeOffsets). The summary format is MimeKit specific; for other tools the judge compares message count and per-message offsets only. No screenshot
|
| 23 |
Tools: MimeKit MimeParser with MimeFormat.Mbox from a .NET script, or Python mailbox.mbox plus email.parser; the script writes a per-message summary of headers and MIME structure, and the byte offsets of each message, headers and body
|
| 24 |
Companions (not included): UnitTests/TestData/mbox/issue1189-summary.txt (golden structure summary; hide); UnitTests/TestData/mbox/issue1189.unix-offsets.json (golden offsets with LF line endings; hide); UnitTests/MimeParserTests.cs (AssertMboxResults, TestMbox, TestIssue1189Mbox); LICENSE
|
campaign_files/2026-10-m-issue-trackers-2/mcgills-passenger-gtfs/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 14 |
|
| 15 |
**Licence (SPDX):** OGL-UK-3.0
|
|
@@ -22,8 +20,6 @@ Units:
|
|
| 22 |
Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/mcgills/gtfs/mcgills_1790160046.zip
|
| 23 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 24 |
Origin: Live static GTFS feed published by McGill's Buses (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/mcgills/gtfs/mcgills_1790160046.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 25 |
-
Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
|
| 26 |
-
Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
|
| 27 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 28 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 29 |
Companions (not included): calendar_dates.txt; agency.txt
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
| 13 |
**Licence (SPDX):** OGL-UK-3.0
|
|
|
|
| 20 |
Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/mcgills/gtfs/mcgills_1790160046.zip
|
| 21 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 22 |
Origin: Live static GTFS feed published by McGill's Buses (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/mcgills/gtfs/mcgills_1790160046.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
|
|
|
|
|
|
| 23 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 24 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 25 |
Companions (not included): calendar_dates.txt; agency.txt
|
campaign_files/2026-10-m-issue-trackers-2/mcgillsse-passenger-gtfs/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 14 |
|
| 15 |
**Licence (SPDX):** OGL-UK-3.0
|
|
@@ -22,8 +20,6 @@ Units:
|
|
| 22 |
Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/mcgillsse/gtfs/mcgillsse_1790767401.zip
|
| 23 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 24 |
Origin: Live static GTFS feed published by Midland Bluebird (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/mcgillsse/gtfs/mcgillsse_1790767401.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 25 |
-
Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
|
| 26 |
-
Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
|
| 27 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 28 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 29 |
Companions (not included): calendar_dates.txt; agency.txt
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
| 13 |
**Licence (SPDX):** OGL-UK-3.0
|
|
|
|
| 20 |
Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/mcgillsse/gtfs/mcgillsse_1790767401.zip
|
| 21 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 22 |
Origin: Live static GTFS feed published by Midland Bluebird (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/mcgillsse/gtfs/mcgillsse_1790767401.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
|
|
|
|
|
|
| 23 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 24 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 25 |
Companions (not included): calendar_dates.txt; agency.txt
|
campaign_files/2026-10-m-issue-trackers-2/mdot-mta-marc-gtfs/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
@@ -22,8 +20,6 @@ Units:
|
|
| 22 |
Read out of the archive: https://mdotmta-gtfs.s3.amazonaws.com/mdotmta_gtfs_marc.zip
|
| 23 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 24 |
Origin: Live static GTFS feed published by Maryland Transit Administration (MDOT MTA) at https://feeds.mta.maryland.gov/gtfs/marc. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 25 |
-
Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
|
| 26 |
-
Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
|
| 27 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 28 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 29 |
Companions (not included): calendar_dates.txt; agency.txt
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 20 |
Read out of the archive: https://mdotmta-gtfs.s3.amazonaws.com/mdotmta_gtfs_marc.zip
|
| 21 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 22 |
Origin: Live static GTFS feed published by Maryland Transit Administration (MDOT MTA) at https://feeds.mta.maryland.gov/gtfs/marc. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
|
|
|
|
|
|
| 23 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 24 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 25 |
Companions (not included): calendar_dates.txt; agency.txt
|
campaign_files/2026-10-m-issue-trackers-2/metrobus-passenger-gtfs/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 14 |
|
| 15 |
**Licence (SPDX):** OGL-UK-3.0
|
|
@@ -22,8 +20,6 @@ Units:
|
|
| 22 |
Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/metrobus/gtfs/metrobus_1789661278.zip
|
| 23 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 24 |
Origin: Live static GTFS feed published by Metrobus (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/metrobus/gtfs/metrobus_1789661278.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 25 |
-
Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
|
| 26 |
-
Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
|
| 27 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 28 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 29 |
Companions (not included): calendar_dates.txt; agency.txt
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
| 13 |
**Licence (SPDX):** OGL-UK-3.0
|
|
|
|
| 20 |
Read out of the archive: https://s3-eu-west-1.amazonaws.com/passenger-sources/metrobus/gtfs/metrobus_1789661278.zip
|
| 21 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 22 |
Origin: Live static GTFS feed published by Metrobus (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/metrobus/gtfs/metrobus_1789661278.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
|
|
|
|
|
|
| 23 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 24 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 25 |
Companions (not included): calendar_dates.txt; agency.txt
|
campaign_files/2026-10-m-issue-trackers-2/metrolink-gtfs/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Facts computed from the service calendar itself (active services on a date, removed or added dates, day counts). Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
@@ -22,8 +20,6 @@ Units:
|
|
| 22 |
Read out of the archive: https://metrolinktrains.com/globalassets/about/gtfs/gtfs.zip
|
| 23 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt)
|
| 24 |
Origin: Live static GTFS feed published by Southern California Regional Rail Authority (Metrolink) at https://metrolinktrains.com/globalassets/about/gtfs/gtfs.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
| 25 |
-
Reference result: facts computed from the service calendar itself (active services on a date, removed or added dates, day counts)
|
| 26 |
-
Reference source: calendar.txt weekday flags with start_date and end_date, calendar_dates.txt exception rows, agency_timezone of agency.txt, all from the pinned members.
|
| 27 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 28 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 29 |
Companions (not included): calendar_dates.txt; agency.txt; feed_info.txt
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The unit is self-contained. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 20 |
Read out of the archive: https://metrolinktrains.com/globalassets/about/gtfs/gtfs.zip
|
| 21 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt, feed_info.txt)
|
| 22 |
Origin: Live static GTFS feed published by Southern California Regional Rail Authority (Metrolink) at https://metrolinktrains.com/globalassets/about/gtfs/gtfs.zip. calendar.txt and its companions were read by member out of the zip with HTTP Range requests (spec general rule 4: by member); kept as a snapshot pinned by sha256.
|
|
|
|
|
|
|
| 23 |
Check: deterministic, no model judgement. Hand-checking 2 samples per source is pending for the delivery step (spec general rule 5).
|
| 24 |
Tools: Read the CSV files with Python csv or pandas (or sqlite3 .import) and expand service days per GTFS rules; gtfs-kit or partridge compute active service_ids per date headless; dates are local to agency_timezone (Python zoneinfo).
|
| 25 |
Companions (not included): calendar_dates.txt; agency.txt; feed_info.txt
|
campaign_files/2026-10-m-issue-trackers-2/metzdowd-cryptography/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Facts computed from the thread headers. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `m259-03/2019-March.txt.gz`: [Cryptography] Best/simplest document encryption (6 messages, 2019-03-21 to 2019-03-24).
|
| 22 |
Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 23 |
Origin: Real list traffic in a closed past month of the list's archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer and is delivered whole.
|
| 24 |
-
Reference result: facts computed from the thread headers
|
| 25 |
-
Reference source: Message-ID, In-Reply-To, References, From and Date headers of the messages in the thread, read from the pinned month file.
|
| 26 |
Check: Exact match against values computed from the pinned month file: parse it as mbox, drop repeated copies of a Message-ID already seen (first copy kept), take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC (a Date header without zone is read as UTC) and compare sender names. Message-IDs are compared after removing angle brackets and double quotes. People are counted by person: From entries with the same address, or the same name after removing accents and letter case, are one person (the names in scale are the first spelling of each). The first-reply interval is the exact difference in whole seconds between the Date headers of the root and the earliest reply, converted to UTC; Date headers have one-second resolution, so no rounding is involved. Deterministic. The program was checked on 2 threads of this source by a second, independent parser (splits the raw text on mbox From lines and reads headers with regular expressions, no mailbox or email module): the chosen thread (also read message by message) and '[Cryptography] Ghidra (NSA reverse engineering tool) made publicly available' (3 messages, root <alpine.BSF.2.21.9999.1903070925090.50700@aneurin.horsfall.org>); message count, last message time and first-reply seconds agreed on both.
|
| 27 |
Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 19 |
- `m259-03/2019-March.txt.gz`: [Cryptography] Best/simplest document encryption (6 messages, 2019-03-21 to 2019-03-24).
|
| 20 |
Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 21 |
Origin: Real list traffic in a closed past month of the list's archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer and is delivered whole.
|
|
|
|
|
|
|
| 22 |
Check: Exact match against values computed from the pinned month file: parse it as mbox, drop repeated copies of a Message-ID already seen (first copy kept), take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC (a Date header without zone is read as UTC) and compare sender names. Message-IDs are compared after removing angle brackets and double quotes. People are counted by person: From entries with the same address, or the same name after removing accents and letter case, are one person (the names in scale are the first spelling of each). The first-reply interval is the exact difference in whole seconds between the Date headers of the root and the earliest reply, converted to UTC; Date headers have one-second resolution, so no rounding is involved. Deterministic. The program was checked on 2 threads of this source by a second, independent parser (splits the raw text on mbox From lines and reads headers with regular expressions, no mailbox or email module): the chosen thread (also read message by message) and '[Cryptography] Ghidra (NSA reverse engineering tool) made publicly available' (3 messages, root <alpine.BSF.2.21.9999.1903070925090.50700@aneurin.horsfall.org>); message count, last message time and first-reply seconds agreed on both.
|
| 23 |
Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
|
campaign_files/2026-10-m-issue-trackers-2/mit-kerberos/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Facts computed from the thread headers. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `m259-07/2019-March.txt.gz`: Installing heimdal-kdc (7 messages, 2019-03-06 to 2019-03-12).
|
| 22 |
Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 23 |
Origin: Real list traffic in a closed past month of the list's archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer and is delivered whole.
|
| 24 |
-
Reference result: facts computed from the thread headers
|
| 25 |
-
Reference source: Message-ID, In-Reply-To, References, From and Date headers of the messages in the thread, read from the pinned month file.
|
| 26 |
Check: Exact match against values computed from the pinned month file: parse it as mbox, drop repeated copies of a Message-ID already seen (first copy kept), take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC (a Date header without zone is read as UTC) and compare sender names. Message-IDs are compared after removing angle brackets and double quotes. People are counted by person: From entries with the same address, or the same name after removing accents and letter case, are one person (the names in scale are the first spelling of each). The first-reply interval is the exact difference in whole seconds between the Date headers of the root and the earliest reply, converted to UTC; Date headers have one-second resolution, so no rounding is involved. Deterministic. The program was checked on 2 threads of this source by a second, independent parser (splits the raw text on mbox From lines and reads headers with regular expressions, no mailbox or email module): the chosen thread (also read message by message) and 'kdc.conf' (5 messages, root <083f49be-ac55-27e6-4a93-065643b38630@tiny-vps.com>); message count, last message time and first-reply seconds agreed on both.
|
| 27 |
Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 19 |
- `m259-07/2019-March.txt.gz`: Installing heimdal-kdc (7 messages, 2019-03-06 to 2019-03-12).
|
| 20 |
Format: Pipermail month archive, mbox text gzip-compressed: full headers (From with obfuscated address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 21 |
Origin: Real list traffic in a closed past month of the list's archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer and is delivered whole.
|
|
|
|
|
|
|
| 22 |
Check: Exact match against values computed from the pinned month file: parse it as mbox, drop repeated copies of a Message-ID already seen (first copy kept), take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC (a Date header without zone is read as UTC) and compare sender names. Message-IDs are compared after removing angle brackets and double quotes. People are counted by person: From entries with the same address, or the same name after removing accents and letter case, are one person (the names in scale are the first spelling of each). The first-reply interval is the exact difference in whole seconds between the Date headers of the root and the earliest reply, converted to UTC; Date headers have one-second resolution, so no rounding is involved. Deterministic. The program was checked on 2 threads of this source by a second, independent parser (splits the raw text on mbox From lines and reads headers with regular expressions, no mailbox or email module): the chosen thread (also read message by message) and 'kdc.conf' (5 messages, root <083f49be-ac55-27e6-4a93-065643b38630@tiny-vps.com>); message count, last message time and first-reply seconds agreed on both.
|
| 23 |
Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
|
campaign_files/2026-10-md-media-and-documents/mc-zen-pillar-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Reference rendering (1 PNG page) compared pixel by pixel. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** tt run examples/number-alignment (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/examples/number-alignment/test.typ`: Pillar Typst package test examples/number-alignment: a table of spectroscopy values aligned at the decimal point, with a reference PNG.
|
| 22 |
Format: Typst source (.typ) plus reference PNG page
|
| 23 |
Origin: visual regression test written by the package author; ref/1.png is the accepted rendering stored by tytanic
|
| 24 |
-
Reference result: reference rendering (1 PNG page) compared pixel by pixel
|
| 25 |
-
Reference source: tests/examples/number-alignment/ref/1.png, the rendering the author accepted
|
| 26 |
Check: compile test.typ with tytanic 0.4.0 and compare the page with ref/1.png pixel by pixel; a pixel deviates when any channel differs by more than max delta; hide ref/ when posing the task
|
| 27 |
Tools: tt run examples/number-alignment (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 28 |
Companions (not included): typst.toml; LICENSE; tests/examples/number-alignment/ref/1.png; src/impl.typ; src/pillar.typ; .github/workflows/run_tests.yml
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** tt run examples/number-alignment (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `tests/examples/number-alignment/test.typ`: Pillar Typst package test examples/number-alignment: a table of spectroscopy values aligned at the decimal point, with a reference PNG.
|
| 20 |
Format: Typst source (.typ) plus reference PNG page
|
| 21 |
Origin: visual regression test written by the package author; ref/1.png is the accepted rendering stored by tytanic
|
|
|
|
|
|
|
| 22 |
Check: compile test.typ with tytanic 0.4.0 and compare the page with ref/1.png pixel by pixel; a pixel deviates when any channel differs by more than max delta; hide ref/ when posing the task
|
| 23 |
Tools: tt run examples/number-alignment (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 24 |
Companions (not included): typst.toml; LICENSE; tests/examples/number-alignment/ref/1.png; src/impl.typ; src/pillar.typ; .github/workflows/run_tests.yml
|
campaign_files/2026-10-md-media-and-documents/mc-zen-quill-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Reference rendering (PNG) compared pixel by pixel. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** tt run examples/teleportation (tytanic, headless Typst compile and pixel compare)
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/examples/teleportation/test.typ`: Quill Typst package test examples/teleportation: quantum teleportation circuit diagram, with reference PNG.
|
| 22 |
Format: Typst source (.typ) plus reference PNG
|
| 23 |
Origin: visual regression test written by the package author; ref/1.png is the accepted rendering
|
| 24 |
-
Reference result: reference rendering (PNG) compared pixel by pixel
|
| 25 |
-
Reference source: tests/examples/teleportation/ref/1.png, the rendering the author accepted
|
| 26 |
Check: compile test.typ with tytanic 0.4.0 at the default resolution and compare with ref/1.png pixel by pixel; hide ref/ when posing the task
|
| 27 |
Tools: tt run examples/teleportation (tytanic, headless Typst compile and pixel compare)
|
| 28 |
Companions (not included): tests/examples/teleportation/ref/1.png; typst.toml; examples/teleportation.typ
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** tt run examples/teleportation (tytanic, headless Typst compile and pixel compare)
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `tests/examples/teleportation/test.typ`: Quill Typst package test examples/teleportation: quantum teleportation circuit diagram, with reference PNG.
|
| 20 |
Format: Typst source (.typ) plus reference PNG
|
| 21 |
Origin: visual regression test written by the package author; ref/1.png is the accepted rendering
|
|
|
|
|
|
|
| 22 |
Check: compile test.typ with tytanic 0.4.0 at the default resolution and compare with ref/1.png pixel by pixel; hide ref/ when posing the task
|
| 23 |
Tools: tt run examples/teleportation (tytanic, headless Typst compile and pixel compare)
|
| 24 |
Companions (not included): tests/examples/teleportation/ref/1.png; typst.toml; examples/teleportation.typ
|
campaign_files/2026-10-md-media-and-documents/mc-zen-tidy-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Reference rendering (9 PNG pages) compared pixel by pixel. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** tt run show-example (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/show-example/test.typ`: Tidy Typst package test show-example: code and preview side by side in documentation examples (modes, ratio, scale, direction), with 9 reference PNG pages.
|
| 22 |
Format: Typst source (.typ) plus reference PNG pages
|
| 23 |
Origin: visual regression test written by the package author; ref/*.png are the accepted renderings stored by tytanic
|
| 24 |
-
Reference result: reference rendering (9 PNG pages) compared pixel by pixel
|
| 25 |
-
Reference source: tests/show-example/ref/1.png to ref/9.png, the renderings the author accepted
|
| 26 |
Check: compile test.typ with tytanic 0.4.0 and compare each page with ref/N.png pixel by pixel; a pixel deviates when any channel differs by more than max delta; page count must match; hide ref/ when posing the task
|
| 27 |
Tools: tt run show-example (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 28 |
Companions (not included): src/show-example.typ; src/tidy.typ; src/helping.typ; src/locales.typ; src/new-parser.typ; src/old-parser.typ; src/parse-module.typ; src/show-module.typ; src/styles.typ; src/styles/default.typ; src/styles/help.typ; src/styles/minimal.typ; src/testing.typ; src/utilities.typ; typst.toml; LICENSE; .github/workflows/run_tests.yml; tests/show-example/ref/1.png; tests/show-example/ref/2.png; tests/show-example/ref/3.png; tests/show-example/ref/4.png; tests/show-example/ref/5.png; tests/show-example/ref/6.png; tests/show-example/ref/7.png; tests/show-example/ref/8.png; tests/show-example/ref/9.png
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** tt run show-example (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `tests/show-example/test.typ`: Tidy Typst package test show-example: code and preview side by side in documentation examples (modes, ratio, scale, direction), with 9 reference PNG pages.
|
| 20 |
Format: Typst source (.typ) plus reference PNG pages
|
| 21 |
Origin: visual regression test written by the package author; ref/*.png are the accepted renderings stored by tytanic
|
|
|
|
|
|
|
| 22 |
Check: compile test.typ with tytanic 0.4.0 and compare each page with ref/N.png pixel by pixel; a pixel deviates when any channel differs by more than max delta; page count must match; hide ref/ when posing the task
|
| 23 |
Tools: tt run show-example (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 24 |
Companions (not included): src/show-example.typ; src/tidy.typ; src/helping.typ; src/locales.typ; src/new-parser.typ; src/old-parser.typ; src/parse-module.typ; src/show-module.typ; src/styles.typ; src/styles/default.typ; src/styles/help.typ; src/styles/minimal.typ; src/testing.typ; src/utilities.typ; typst.toml; LICENSE; .github/workflows/run_tests.yml; tests/show-example/ref/1.png; tests/show-example/ref/2.png; tests/show-example/ref/3.png; tests/show-example/ref/4.png; tests/show-example/ref/5.png; tests/show-example/ref/6.png; tests/show-example/ref/7.png; tests/show-example/ref/8.png; tests/show-example/ref/9.png
|
campaign_files/2026-10-md-media-and-documents/mc-zen-zero-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Reference rendering produced from a hand-written Typst reference (ref.typ), compared pixel by pixel. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** tt run num/grouping (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/num/grouping/test.typ`: Zero Typst package test num/grouping: digit grouping of numbers (thresholds, separators, group size), checked against a Typst reference document.
|
| 22 |
Format: Typst source (.typ) plus a Typst reference source (ref.typ)
|
| 23 |
Origin: regression test written by the package author; ref.typ is an ephemeral reference: tytanic renders it and the test and compares the two renderings
|
| 24 |
-
Reference result: reference rendering produced from a hand-written Typst reference (ref.typ), compared pixel by pixel
|
| 25 |
-
Reference source: tests/num/grouping/ref.typ, the expected output written out by hand by the author (plain text with the grouping spaces already placed)
|
| 26 |
Check: compile test.typ and ref.typ with tytanic and compare the two renderings page by page, pixel by pixel; a pixel deviates when any channel differs by more than max delta; page count must match; hide ref.typ when posing the task
|
| 27 |
Tools: tt run num/grouping (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 28 |
Companions (not included): tests/num/grouping/ref.typ; src/accessibility.typ; src/align-column.typ; src/assertions.typ; src/formatting.typ; src/impl.typ; src/num.typ; src/parsing.typ; src/quan.typ; src/rounding.typ; src/state.typ; src/units.typ; src/utility.typ; src/zero.typ; src/zi.typ; src/ztable.typ; typst.toml; LICENSE; .github/workflows/run_tests.yml
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** tt run num/grouping (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `tests/num/grouping/test.typ`: Zero Typst package test num/grouping: digit grouping of numbers (thresholds, separators, group size), checked against a Typst reference document.
|
| 20 |
Format: Typst source (.typ) plus a Typst reference source (ref.typ)
|
| 21 |
Origin: regression test written by the package author; ref.typ is an ephemeral reference: tytanic renders it and the test and compares the two renderings
|
|
|
|
|
|
|
| 22 |
Check: compile test.typ and ref.typ with tytanic and compare the two renderings page by page, pixel by pixel; a pixel deviates when any channel differs by more than max delta; page count must match; hide ref.typ when posing the task
|
| 23 |
Tools: tt run num/grouping (tytanic test runner, headless Typst compile to PNG and pixel compare); typst compile for a single render
|
| 24 |
Companions (not included): tests/num/grouping/ref.typ; src/accessibility.typ; src/align-column.typ; src/assertions.typ; src/formatting.typ; src/impl.typ; src/num.typ; src/parsing.typ; src/quan.typ; src/rounding.typ; src/state.typ; src/units.typ; src/utility.typ; src/zero.typ; src/zi.typ; src/ztable.typ; typst.toml; LICENSE; .github/workflows/run_tests.yml
|
campaign_files/2026-10-md-media-and-documents/md4c-spec-wiki-links/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected HTML (x-wikilink elements) for each example. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** md2html --fwiki-links input.md (the MD4C command line converter)
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `test/spec-wiki-links.txt`: MD4C wiki-link extension spec: [[wiki links]] in Markdown converted to HTML.
|
| 22 |
Format: spec-style Markdown file (6372 bytes) with 23 fenced examples (Markdown, ".", expected HTML) and a flag line --fwiki-links after each example
|
| 23 |
Origin: test document written by the MD4C author for the MD_FLAG_WIKILINKS extension; not part of the CommonMark spec
|
| 24 |
-
Reference result: expected HTML (x-wikilink elements) for each example
|
| 25 |
-
Reference source: the part after "." in each example block
|
| 26 |
Check: parse examples as test/run-testsuite.py does; show only the Markdown; convert with --fwiki-links; pass when normalize_html(actual) equals normalize_html(expected) (test/normalize.py)
|
| 27 |
Tools: md2html --fwiki-links input.md (the MD4C command line converter)
|
| 28 |
Dependencies: md4c with md2html; Python 3 for run-testsuite.py and normalize.py
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** md2html --fwiki-links input.md (the MD4C command line converter)
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `test/spec-wiki-links.txt`: MD4C wiki-link extension spec: [[wiki links]] in Markdown converted to HTML.
|
| 20 |
Format: spec-style Markdown file (6372 bytes) with 23 fenced examples (Markdown, ".", expected HTML) and a flag line --fwiki-links after each example
|
| 21 |
Origin: test document written by the MD4C author for the MD_FLAG_WIKILINKS extension; not part of the CommonMark spec
|
|
|
|
|
|
|
| 22 |
Check: parse examples as test/run-testsuite.py does; show only the Markdown; convert with --fwiki-links; pass when normalize_html(actual) equals normalize_html(expected) (test/normalize.py)
|
| 23 |
Tools: md2html --fwiki-links input.md (the MD4C command line converter)
|
| 24 |
Dependencies: md4c with md2html; Python 3 for run-testsuite.py and normalize.py
|
campaign_files/2026-10-md-media-and-documents/mdformat/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected formatted Markdown for each input case. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** mdformat FILE (Python command line formatter, default options), output compared with each fixture's expected Markdown
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/data/default_style.md`: Mdformat style fixtures: Markdown reformatted to the default style.
|
| 22 |
Format: markdown-it fixture text: title, '.', input Markdown, '.', expected Markdown, '.' per case (38 cases)
|
| 23 |
Origin: fixture file of input and expected Markdown pairs written by the mdformat author; tests/test_style.py is the judge
|
| 24 |
-
Reference result: expected formatted Markdown for each input case
|
| 25 |
-
Reference source: the expected Markdown block of each case in tests/data/default_style.md
|
| 26 |
Check: give the agent each case's Markdown and ask for the file mdformat writes with no options; the command must exit 0 and the file must equal the expected block exactly
|
| 27 |
Tools: mdformat FILE (Python command line formatter, default options), output compared with each fixture's expected Markdown
|
| 28 |
Companions (not included): tests/test_style.py; LICENSE
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** mdformat FILE (Python command line formatter, default options), output compared with each fixture's expected Markdown
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `tests/data/default_style.md`: Mdformat style fixtures: Markdown reformatted to the default style.
|
| 20 |
Format: markdown-it fixture text: title, '.', input Markdown, '.', expected Markdown, '.' per case (38 cases)
|
| 21 |
Origin: fixture file of input and expected Markdown pairs written by the mdformat author; tests/test_style.py is the judge
|
|
|
|
|
|
|
| 22 |
Check: give the agent each case's Markdown and ask for the file mdformat writes with no options; the command must exit 0 and the file must equal the expected block exactly
|
| 23 |
Tools: mdformat FILE (Python command line formatter, default options), output compared with each fixture's expected Markdown
|
| 24 |
Companions (not included): tests/test_style.py; LICENSE
|
campaign_files/2026-10-md-media-and-documents/mdit-py-plugins-fixtures-field-list/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected HTML (dl class="field-list") for each case. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** python -c with markdown_it.MarkdownIt("commonmark").use(fieldlist_plugin).render(text) (Python library); pandoc -f rst -t html converts the reStructuredText equivalent
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/fixtures/field_list.md`: Mdit-py-plugins fixture "field_list": reStructuredText-style field lists in Markdown converted to HTML.
|
| 22 |
Format: markdown-it fixture file (6173 bytes): 23 cases of title / "." / Markdown / "." / expected HTML / "."
|
| 23 |
Origin: fixture written for the field list plugin; its first case ("Docutils example") reproduces the field list example of the Docutils reStructuredText documentation, which the Docutils project places in the public domain; the remaining cases are the plugin authors' own; the example names "Me / Myself / I" are placeholders
|
| 24 |
-
Reference result: expected HTML (dl class="field-list") for each case
|
| 25 |
-
Reference source: the second block of each case in field_list.md
|
| 26 |
Check: split into cases as markdown_it.utils read_fixture_file does; show only the Markdown; render with MarkdownIt("commonmark").use(fieldlist_plugin) and xhtmlOut False; pass when the HTML equals the expected block after stripping trailing white space
|
| 27 |
Tools: python -c with markdown_it.MarkdownIt("commonmark").use(fieldlist_plugin).render(text) (Python library); pandoc -f rst -t html converts the reStructuredText equivalent
|
| 28 |
Dependencies: mdit-py-plugins; markdown-it-py
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** python -c with markdown_it.MarkdownIt("commonmark").use(fieldlist_plugin).render(text) (Python library); pandoc -f rst -t html converts the reStructuredText equivalent
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `tests/fixtures/field_list.md`: Mdit-py-plugins fixture "field_list": reStructuredText-style field lists in Markdown converted to HTML.
|
| 20 |
Format: markdown-it fixture file (6173 bytes): 23 cases of title / "." / Markdown / "." / expected HTML / "."
|
| 21 |
Origin: fixture written for the field list plugin; its first case ("Docutils example") reproduces the field list example of the Docutils reStructuredText documentation, which the Docutils project places in the public domain; the remaining cases are the plugin authors' own; the example names "Me / Myself / I" are placeholders
|
|
|
|
|
|
|
| 22 |
Check: split into cases as markdown_it.utils read_fixture_file does; show only the Markdown; render with MarkdownIt("commonmark").use(fieldlist_plugin) and xhtmlOut False; pass when the HTML equals the expected block after stripping trailing white space
|
| 23 |
Tools: python -c with markdown_it.MarkdownIt("commonmark").use(fieldlist_plugin).render(text) (Python library); pandoc -f rst -t html converts the reStructuredText equivalent
|
| 24 |
Dependencies: mdit-py-plugins; markdown-it-py
|
campaign_files/2026-10-ml-serving-configs-2/ml150-06/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_anomaly_points. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Give the agent the series without the EVENT column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `ml150-06/1_gecco2018_water_quality.csv`: GECCO 2018 drinking-water quality series (1_gecco2018_water_quality.csv): 139566 one-minute rows, 2016-08-03 to 2016-11-08, nine sensor columns, 1726 rows with EVENT TRUE.
|
| 22 |
Format: CSV with header "",Time,Tp,Cl,pH,Redox,Leit,Trueb,Cl_2,Fm,Fm_2,EVENT; first column is the row number, EVENT is TRUE or FALSE per minute
|
| 23 |
Origin: Thüringer Fernwasserversorgung measurements; the 2017 rules (same data family) say events were partly imputed into the real series to simulate events (3_Rules_GECCO_Industrial_Challenge_2017.pdf, section 2.2)
|
| 24 |
-
Reference result: labelled_anomaly_points
|
| 25 |
-
Reference source: the EVENT column of the file (1726 TRUE rows out of 139566); marked by the organisers: "All data constellations considered as remarkable changes in the water quality resp. events are marked in the column EVENT" (3_Rules_GECCO_Industrial_Challenge_2017.pdf section 2.2); outliers and baseline changes are not events
|
| 26 |
Check: Give the agent the series without the EVENT column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events
|
| 27 |
Dependencies: none to read the data (CSV); the challenge's own scorer is R (f1score.R in the resource package), which the judge may reimplement in a few lines.
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Give the agent the series without the EVENT column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 19 |
- `ml150-06/1_gecco2018_water_quality.csv`: GECCO 2018 drinking-water quality series (1_gecco2018_water_quality.csv): 139566 one-minute rows, 2016-08-03 to 2016-11-08, nine sensor columns, 1726 rows with EVENT TRUE.
|
| 20 |
Format: CSV with header "",Time,Tp,Cl,pH,Redox,Leit,Trueb,Cl_2,Fm,Fm_2,EVENT; first column is the row number, EVENT is TRUE or FALSE per minute
|
| 21 |
Origin: Thüringer Fernwasserversorgung measurements; the 2017 rules (same data family) say events were partly imputed into the real series to simulate events (3_Rules_GECCO_Industrial_Challenge_2017.pdf, section 2.2)
|
|
|
|
|
|
|
| 22 |
Check: Give the agent the series without the EVENT column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events
|
| 23 |
Dependencies: none to read the data (CSV); the challenge's own scorer is R (f1score.R in the resource package), which the judge may reimplement in a few lines.
|
campaign_files/2026-10-ml-serving-configs-2/ml150-07/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_anomaly_points. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Give the agent the series without the Event column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `ml150-07/7_gecco2019_train_water_quality.csv`: GECCO 2019 drinking-water quality training series (7_gecco2019_train_water_quality.csv): 132480 one-minute rows, 2017-07-01 to 2017-09-30, six sensor columns, 212 rows with Event TRUE.
|
| 22 |
Format: CSV with header "",Time,Tp,pH,Cond,Turb,SAC,PFM,Event; first column is the row number, Event is TRUE or FALSE per minute
|
| 23 |
Origin: Thüringer Fernwasserversorgung measurements prepared by the organisers
|
| 24 |
-
Reference result: labelled_anomaly_points
|
| 25 |
-
Reference source: the Event column of the file (212 TRUE rows out of 132480); marked by the organisers: "All data constellations considered as remarkable changes in the water quality resp. events are marked in the column EVENT" (3_Rules_GECCO_Industrial_Challenge_2017.pdf section 2.2); outliers and baseline changes are not events
|
| 26 |
Check: Give the agent the series without the Event column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events
|
| 27 |
Dependencies: none to read the data (CSV); the challenge's own scorer is R (f1score.R in the resource package), which the judge may reimplement in a few lines.
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Give the agent the series without the Event column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 19 |
- `ml150-07/7_gecco2019_train_water_quality.csv`: GECCO 2019 drinking-water quality training series (7_gecco2019_train_water_quality.csv): 132480 one-minute rows, 2017-07-01 to 2017-09-30, six sensor columns, 212 rows with Event TRUE.
|
| 20 |
Format: CSV with header "",Time,Tp,pH,Cond,Turb,SAC,PFM,Event; first column is the row number, Event is TRUE or FALSE per minute
|
| 21 |
Origin: Thüringer Fernwasserversorgung measurements prepared by the organisers
|
|
|
|
|
|
|
| 22 |
Check: Give the agent the series without the Event column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events
|
| 23 |
Dependencies: none to read the data (CSV); the challenge's own scorer is R (f1score.R in the resource package), which the judge may reimplement in a few lines.
|
campaign_files/2026-10-ml-serving-configs-2/ml150-08/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_anomaly_points. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Give the agent the series without the EVENT column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `ml150-08/1_gecco2017_water_quality.csv`: GECCO 2017 drinking-water quality series (1_gecco2017_water_quality.csv): 122334 one-minute rows, 2016-02-15 to 2016-05-10, nine sensor columns, 1740 rows with EVENT TRUE.
|
| 22 |
Format: CSV with header "",Time,Tp,Cl,pH,Redox,Leit,Trueb,Cl_2,Fm,Fm_2,EVENT; first column is the row number, EVENT is TRUE or FALSE per minute
|
| 23 |
Origin: Thüringer Fernwasserversorgung measurements; the original data only held events from sensor checks and replacements, and additional events were imputed to simulate events (3_Rules_GECCO_Industrial_Challenge_2017.pdf section 2.2: "For this challenge additional events have been imputed into the data")
|
| 24 |
-
Reference result: labelled_anomaly_points
|
| 25 |
-
Reference source: the EVENT column of the file (1740 TRUE rows out of 122334); marked by the organisers: "All data constellations considered as remarkable changes in the water quality resp. events are marked in the column EVENT" (3_Rules_GECCO_Industrial_Challenge_2017.pdf section 2.2); outliers and baseline changes are not events
|
| 26 |
Check: Give the agent the series without the EVENT column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events
|
| 27 |
Dependencies: none to read the data (CSV); the challenge's own scorer is R (f1score.R in the resource package), which the judge may reimplement in a few lines.
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Give the agent the series without the EVENT column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 19 |
- `ml150-08/1_gecco2017_water_quality.csv`: GECCO 2017 drinking-water quality series (1_gecco2017_water_quality.csv): 122334 one-minute rows, 2016-02-15 to 2016-05-10, nine sensor columns, 1740 rows with EVENT TRUE.
|
| 20 |
Format: CSV with header "",Time,Tp,Cl,pH,Redox,Leit,Trueb,Cl_2,Fm,Fm_2,EVENT; first column is the row number, EVENT is TRUE or FALSE per minute
|
| 21 |
Origin: Thüringer Fernwasserversorgung measurements; the original data only held events from sensor checks and replacements, and additional events were imputed to simulate events (3_Rules_GECCO_Industrial_Challenge_2017.pdf section 2.2: "For this challenge additional events have been imputed into the data")
|
|
|
|
|
|
|
| 22 |
Check: Give the agent the series without the EVENT column; the agent returns one TRUE/FALSE per row (online: each row decided from the rows up to it). Score with the challenge's F1: TP, FP, TN and FN counted per row (ResourcePackage/source/R/Framework/Lib/f1score.R lines 2 to 5), F1 = 2 PPV TPR / (PPV + TPR) (line 10), and F1 set to 0 when undefined (line 12); no tolerance window around events
|
| 23 |
Dependencies: none to read the data (CSV); the challenge's own scorer is R (f1score.R in the resource package), which the judge may reimplement in a few lines.
|
campaign_files/2026-10-ml-serving-configs-2/ml198-01/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_failure_flags. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Hide the six label columns. Task A: the agent recovers the failure rules and flags every row for HDF, PWF and OSF; pass on an exact per-row match of the three flag columns. Task B: per-row Machine failure prediction, scored by exact match counts. TWF and RNF are random by construction (uci601.html lines 114 and 118) and are not judged per row.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -22,7 +20,5 @@ Units:
|
|
| 22 |
Read out of the archive: https://archive.ics.uci.edu/static/public/601/ai4i+2020+predictive+maintenance+dataset.zip
|
| 23 |
Format: CSV, 10,000 rows by 14 columns: UDI, Product ID, Type (L, M, H), Air temperature [K], Process temperature [K], Rotational speed [rpm], Torque [Nm], Tool wear [min], Machine failure, TWF, HDF, PWF, OSF, RNF
|
| 24 |
Origin: synthetic dataset built by its author to mirror real predictive maintenance data (dataset page: 'a synthetic dataset that reflects real predictive maintenance data encountered in industry'), published as a benchmark.
|
| 25 |
-
Reference result: labelled_failure_flags
|
| 26 |
-
Reference source: the columns Machine failure, TWF, HDF, PWF, OSF and RNF of ai4i2020.csv; the rules for HDF, PWF and OSF are stated on the dataset page (uci601.html lines 115 to 117); 339 rows have Machine failure 1 (TWF 46, HDF 115, PWF 95, OSF 98, RNF 19)
|
| 27 |
Check: Hide the six label columns. Task A: the agent recovers the failure rules and flags every row for HDF, PWF and OSF; pass on an exact per-row match of the three flag columns. Task B: per-row Machine failure prediction, scored by exact match counts. TWF and RNF are random by construction (uci601.html lines 114 and 118) and are not judged per row
|
| 28 |
Dependencies: none to read the data (comma-separated text with a UTF-8 byte order mark).
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Hide the six label columns. Task A: the agent recovers the failure rules and flags every row for HDF, PWF and OSF; pass on an exact per-row match of the three flag columns. Task B: per-row Machine failure prediction, scored by exact match counts. TWF and RNF are random by construction (uci601.html lines 114 and 118) and are not judged per row.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 20 |
Read out of the archive: https://archive.ics.uci.edu/static/public/601/ai4i+2020+predictive+maintenance+dataset.zip
|
| 21 |
Format: CSV, 10,000 rows by 14 columns: UDI, Product ID, Type (L, M, H), Air temperature [K], Process temperature [K], Rotational speed [rpm], Torque [Nm], Tool wear [min], Machine failure, TWF, HDF, PWF, OSF, RNF
|
| 22 |
Origin: synthetic dataset built by its author to mirror real predictive maintenance data (dataset page: 'a synthetic dataset that reflects real predictive maintenance data encountered in industry'), published as a benchmark.
|
|
|
|
|
|
|
| 23 |
Check: Hide the six label columns. Task A: the agent recovers the failure rules and flags every row for HDF, PWF and OSF; pass on an exact per-row match of the three flag columns. Task B: per-row Machine failure prediction, scored by exact match counts. TWF and RNF are random by construction (uci601.html lines 114 and 118) and are not judged per row
|
| 24 |
Dependencies: none to read the data (comma-separated text with a UTF-8 byte order mark).
|
campaign_files/2026-10-ml-serving-configs-2/ml198-11/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_leak_time_series. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Hide 2018_Leakages.csv and 2018_Fixed_Leakages_Report.txt. The agent reads the 2018 flows and tank level and names the pipes that leaked during 2018. Pass on an exact match of the set of 14 pipe IDs that head the columns of 2018_Leakages.csv.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `ml198-11/2018_SCADA_Flows.csv`: BattLeDIM 2020 historical dataset (year 2018): L-Town water network SCADA flows and tank level at 5-minute steps, with the time series of all 2018 leakages.
|
| 22 |
Format: semicolon-separated text, 105,120 rows at 5-minute steps for 2018, columns Timestamp;p227;p235;PUMP_1 with decimal commas; 2018_Leakages.csv has Timestamp plus 14 pipe columns (p31 p158 p183 p232 p257 p369 p427 p461 p538 p628 p654 p673 p810 p866) of leak flow in m3/h
|
| 23 |
Origin: official competition instance of BattLeDIM 2020: readings simulated with the L-Town EPANET model with injected leakages (README.txt lines 10 to 13: L-TOWN_Real.inp is 'The model of the network used to generate the datasets'), published by the organisers.
|
| 24 |
-
Reference result: labelled_leak_time_series
|
| 25 |
-
Reference source: 2018_Leakages.csv, 'Timeseries of all leakages in the Historical Dataset (year 2018) of the BattLeDIM competition. Measurement units: Cubic meters per hour(m^3/h). Column headings correspond to Link IDs in the L-Town.inp network file.' (README.txt lines 56 to 59); 2018_Fixed_Leakages_Report.txt gives the repair end time of 10 of the leaks
|
| 26 |
Check: Hide 2018_Leakages.csv and 2018_Fixed_Leakages_Report.txt. The agent reads the 2018 flows and tank level and names the pipes that leaked during 2018. Pass on an exact match of the set of 14 pipe IDs that head the columns of 2018_Leakages.csv.
|
| 27 |
Companions (not included): 2018_SCADA_Levels.csv; README.txt; 2018_Leakages.csv; 2018_Fixed_Leakages_Report.txt
|
| 28 |
Dependencies: none to read the data (semicolon-separated text with decimal commas).
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Hide 2018_Leakages.csv and 2018_Fixed_Leakages_Report.txt. The agent reads the 2018 flows and tank level and names the pipes that leaked during 2018. Pass on an exact match of the set of 14 pipe IDs that head the columns of 2018_Leakages.csv.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 19 |
- `ml198-11/2018_SCADA_Flows.csv`: BattLeDIM 2020 historical dataset (year 2018): L-Town water network SCADA flows and tank level at 5-minute steps, with the time series of all 2018 leakages.
|
| 20 |
Format: semicolon-separated text, 105,120 rows at 5-minute steps for 2018, columns Timestamp;p227;p235;PUMP_1 with decimal commas; 2018_Leakages.csv has Timestamp plus 14 pipe columns (p31 p158 p183 p232 p257 p369 p427 p461 p538 p628 p654 p673 p810 p866) of leak flow in m3/h
|
| 21 |
Origin: official competition instance of BattLeDIM 2020: readings simulated with the L-Town EPANET model with injected leakages (README.txt lines 10 to 13: L-TOWN_Real.inp is 'The model of the network used to generate the datasets'), published by the organisers.
|
|
|
|
|
|
|
| 22 |
Check: Hide 2018_Leakages.csv and 2018_Fixed_Leakages_Report.txt. The agent reads the 2018 flows and tank level and names the pipes that leaked during 2018. Pass on an exact match of the set of 14 pipe IDs that head the columns of 2018_Leakages.csv.
|
| 23 |
Companions (not included): 2018_SCADA_Levels.csv; README.txt; 2018_Leakages.csv; 2018_Fixed_Leakages_Report.txt
|
| 24 |
Dependencies: none to read the data (semicolon-separated text with decimal commas).
|
campaign_files/2026-10-ml-serving-configs-2/ml198-12/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_attack_windows. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Hide the ATT_FLAG column and the PNG. The agent flags the hours it judges under attack. An attack counts as detected when at least one flagged hour falls inside its window (start and end hours inclusive). Pass when all 7 attacks are detected and no flagged hour lies outside the 7 windows; also report the per-hour confusion matrix against the union of the windows.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `data/BATADAL_dataset04.csv`: BATADAL Training Dataset 2: about six months of hourly C-Town water network SCADA readings (tank levels, pump and valve flows and status, junction pressures) with seven attacks listed by the organisers.
|
| 22 |
Format: CSV, 4,177 hourly rows from 04/07/16 00 to 25/12/16 00, 45 columns: DATETIME (dd/mm/yy HH), L_T1 to L_T7, F_PU1 to F_PU11 and S_PU1 to S_PU11, F_V2, S_V2, 12 junction pressures P_J*, ATT_FLAG (1 on 219 labelled attack hours, -999 elsewhere)
|
| 23 |
Origin: official competition instance of BATADAL: hourly SCADA readings simulated on the C-Town network with injected attacks (data.html line 78 says Training Dataset 1 'was generated from a one-year long simulation'), published by the organisers.
|
| 24 |
-
Reference result: labelled_attack_windows
|
| 25 |
-
Reference source: 2 26/09/2016 11 to 27/09/2016 10; 3 09/10/2016 09 to 11/10/2016 20; 4 29/10/2016 19 to 02/11/2016 16; 5 26/11/2016 17 to 29/11/2016 04; 6 06/12/2016 07 to 10/12/2016 04; 7 14/12/2016 15 to 19/12/2016 04. Cross-check: the ATT_FLAG=1 runs of the CSV are 5 runs of 42, 60, 37, 7 and 73 hours, each inside windows 1, 3, 4, 5 and 6, equal to the table's labelled hours (attacks 2 and 7 are unlabelled in the CSV, as the table says: 0 labelled hours)
|
| 26 |
Check: Hide the ATT_FLAG column and the PNG. The agent flags the hours it judges under attack. An attack counts as detected when at least one flagged hour falls inside its window (start and end hours inclusive). Pass when all 7 attacks are detected and no flagged hour lies outside the 7 windows; also report the per-hour confusion matrix against the union of the windows.
|
| 27 |
Companions (not included): images/Attacks_TrainingDataset2.png; data/CTOWN.INP
|
| 28 |
Dependencies: none to read the data (comma-separated text); CTOWN.INP is EPANET input text, an optional reference.
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Hide the ATT_FLAG column and the PNG. The agent flags the hours it judges under attack. An attack counts as detected when at least one flagged hour falls inside its window (start and end hours inclusive). Pass when all 7 attacks are detected and no flagged hour lies outside the 7 windows; also report the per-hour confusion matrix against the union of the windows.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 19 |
- `data/BATADAL_dataset04.csv`: BATADAL Training Dataset 2: about six months of hourly C-Town water network SCADA readings (tank levels, pump and valve flows and status, junction pressures) with seven attacks listed by the organisers.
|
| 20 |
Format: CSV, 4,177 hourly rows from 04/07/16 00 to 25/12/16 00, 45 columns: DATETIME (dd/mm/yy HH), L_T1 to L_T7, F_PU1 to F_PU11 and S_PU1 to S_PU11, F_V2, S_V2, 12 junction pressures P_J*, ATT_FLAG (1 on 219 labelled attack hours, -999 elsewhere)
|
| 21 |
Origin: official competition instance of BATADAL: hourly SCADA readings simulated on the C-Town network with injected attacks (data.html line 78 says Training Dataset 1 'was generated from a one-year long simulation'), published by the organisers.
|
|
|
|
|
|
|
| 22 |
Check: Hide the ATT_FLAG column and the PNG. The agent flags the hours it judges under attack. An attack counts as detected when at least one flagged hour falls inside its window (start and end hours inclusive). Pass when all 7 attacks are detected and no flagged hour lies outside the 7 windows; also report the per-hour confusion matrix against the union of the windows.
|
| 23 |
Companions (not included): images/Attacks_TrainingDataset2.png; data/CTOWN.INP
|
| 24 |
Dependencies: none to read the data (comma-separated text); CTOWN.INP is EPANET input text, an optional reference.
|
campaign_files/2026-10-ml-serving-configs-2/ml247-01/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_event_intervals. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Hide Dodgers.events. Task: from Dodgers.data the agent lists the dates on which a game took place; scored per date by exact match against the dates in Dodgers.events, reported as counts of hits, misses and false dates. Dodgers.names section 5 states that 2 of the 81 games fall in periods when the sensor was down, so 79 dates are visible in the data.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -22,8 +20,6 @@ Units:
|
|
| 22 |
Read out of the archive: https://archive.ics.uci.edu/static/public/157/dodgers+loop+sensor.zip
|
| 23 |
Format: Dodgers.data: CSV, 50,400 rows (date and time, car count for the previous 5 minutes, -1 for missing); Dodgers.events: CSV, 81 rows (date, begin time, end time, attendance, away team, W/L score)
|
| 24 |
Origin: real loop detector counts from the PeMS system, prepared by the dataset creator for event detection research (KDD 2006).
|
| 25 |
-
Reference result: labelled_event_intervals
|
| 26 |
-
Reference source: Dodgers.events (81 home games with begin and end times), the validation file named by the source documentation (Dodgers.names section 5)
|
| 27 |
Check: Hide Dodgers.events. Task: from Dodgers.data the agent lists the dates on which a game took place; scored per date by exact match against the dates in Dodgers.events, reported as counts of hits, misses and false dates. Dodgers.names section 5 states that 2 of the 81 games fall in periods when the sensor was down, so 79 dates are visible in the data
|
| 28 |
Companions (not included): Dodgers.events
|
| 29 |
Dependencies: none to read the data (plain comma-separated or space-separated text).
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Hide Dodgers.events. Task: from Dodgers.data the agent lists the dates on which a game took place; scored per date by exact match against the dates in Dodgers.events, reported as counts of hits, misses and false dates. Dodgers.names section 5 states that 2 of the 81 games fall in periods when the sensor was down, so 79 dates are visible in the data.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 20 |
Read out of the archive: https://archive.ics.uci.edu/static/public/157/dodgers+loop+sensor.zip
|
| 21 |
Format: Dodgers.data: CSV, 50,400 rows (date and time, car count for the previous 5 minutes, -1 for missing); Dodgers.events: CSV, 81 rows (date, begin time, end time, attendance, away team, W/L score)
|
| 22 |
Origin: real loop detector counts from the PeMS system, prepared by the dataset creator for event detection research (KDD 2006).
|
|
|
|
|
|
|
| 23 |
Check: Hide Dodgers.events. Task: from Dodgers.data the agent lists the dates on which a game took place; scored per date by exact match against the dates in Dodgers.events, reported as counts of hits, misses and false dates. Dodgers.names section 5 states that 2 of the 81 games fall in periods when the sensor was down, so 79 dates are visible in the data
|
| 24 |
Companions (not included): Dodgers.events
|
| 25 |
Dependencies: none to read the data (plain comma-separated or space-separated text).
|
campaign_files/2026-10-ml-serving-configs-2/ml247-02/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_event_intervals. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Hide CalIt2.events. Task: from CalIt2.data the agent lists the rows (date and time stamps of CalIt2.data) it judges to be inside an event; scored per row by exact match against the rows whose time stamps fall inside the event intervals listed in CalIt2.events, reported as counts of listed event rows found and of flagged rows outside the list. CalIt2.names section 5 says the event list is incomplete, so flagged rows outside it are reported, not counted as wrong.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -22,8 +20,6 @@ Units:
|
|
| 22 |
Read out of the archive: https://archive.ics.uci.edu/static/public/156/calit2+building+people+counts.zip
|
| 23 |
Format: CalIt2.data: CSV, 10,080 rows (flow ID 7 out or 9 in, date, time, count for the previous half hour); CalIt2.events: CSV, 30 rows (date, begin time, end time, anonymised event name)
|
| 24 |
Origin: real door sensor counts at the CalIt2 building of UC Irvine, prepared by the dataset creator for event detection research (KDD 2006).
|
| 25 |
-
Reference result: labelled_event_intervals
|
| 26 |
-
Reference source: CalIt2.events (30 known events with begin and end times), the validation file named by the source documentation (CalIt2.names section 5)
|
| 27 |
Check: Hide CalIt2.events. Task: from CalIt2.data the agent lists the rows (date and time stamps of CalIt2.data) it judges to be inside an event; scored per row by exact match against the rows whose time stamps fall inside the event intervals listed in CalIt2.events, reported as counts of listed event rows found and of flagged rows outside the list. CalIt2.names section 5 says the event list is incomplete, so flagged rows outside it are reported, not counted as wrong
|
| 28 |
Companions (not included): CalIt2.events
|
| 29 |
Dependencies: none to read the data (plain comma-separated or space-separated text).
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Hide CalIt2.events. Task: from CalIt2.data the agent lists the rows (date and time stamps of CalIt2.data) it judges to be inside an event; scored per row by exact match against the rows whose time stamps fall inside the event intervals listed in CalIt2.events, reported as counts of listed event rows found and of flagged rows outside the list. CalIt2.names section 5 says the event list is incomplete, so flagged rows outside it are reported, not counted as wrong.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 20 |
Read out of the archive: https://archive.ics.uci.edu/static/public/156/calit2+building+people+counts.zip
|
| 21 |
Format: CalIt2.data: CSV, 10,080 rows (flow ID 7 out or 9 in, date, time, count for the previous half hour); CalIt2.events: CSV, 30 rows (date, begin time, end time, anonymised event name)
|
| 22 |
Origin: real door sensor counts at the CalIt2 building of UC Irvine, prepared by the dataset creator for event detection research (KDD 2006).
|
|
|
|
|
|
|
| 23 |
Check: Hide CalIt2.events. Task: from CalIt2.data the agent lists the rows (date and time stamps of CalIt2.data) it judges to be inside an event; scored per row by exact match against the rows whose time stamps fall inside the event intervals listed in CalIt2.events, reported as counts of listed event rows found and of flagged rows outside the list. CalIt2.names section 5 says the event list is incomplete, so flagged rows outside it are reported, not counted as wrong
|
| 24 |
Companions (not included): CalIt2.events
|
| 25 |
Dependencies: none to read the data (plain comma-separated or space-separated text).
|
campaign_files/2026-10-ml-serving-configs-2/ml293-06/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_root_cause. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Rename the folder so the path does not reveal the answer. The agent gets data.csv and inject_time.txt and names the root-cause service and the fault type (cpu or mem, the two types of the sibling folders carts, catalogue, orders, payment and user in sock-shop-1.zip); scored by exact match on both.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -21,7 +19,5 @@ Units:
|
|
| 21 |
- `sock-shop-1/sock-shop/payment_mem/1/` (4 files): RCD and CIRCA evaluation data, Sock Shop case payment_mem/1: container metrics around one injected memory fault, with the injection time; the root cause is given by the case folder name.
|
| 22 |
Format: data.csv: CSV of per-second metrics of all services; normal.csv and anomalous.csv: the same split before and after injection; inject_time.txt: Unix time of the injection
|
| 23 |
Origin: real metrics recorded by the authors on Sock Shop deployed on Kubernetes with fault injection, published as-is on Zenodo
|
| 24 |
-
Reference result: labelled_root_cause
|
| 25 |
-
Reference source: the case folder name payment_mem written by the data authors: root-cause service payment, fault type memory
|
| 26 |
Check: Rename the folder so the path does not reveal the answer. The agent gets data.csv and inject_time.txt and names the root-cause service and the fault type (cpu or mem, the two types of the sibling folders carts, catalogue, orders, payment and user in sock-shop-1.zip); scored by exact match on both
|
| 27 |
Dependencies: none to read the data (CSV and text).
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Rename the folder so the path does not reveal the answer. The agent gets data.csv and inject_time.txt and names the root-cause service and the fault type (cpu or mem, the two types of the sibling folders carts, catalogue, orders, payment and user in sock-shop-1.zip); scored by exact match on both.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 19 |
- `sock-shop-1/sock-shop/payment_mem/1/` (4 files): RCD and CIRCA evaluation data, Sock Shop case payment_mem/1: container metrics around one injected memory fault, with the injection time; the root cause is given by the case folder name.
|
| 20 |
Format: data.csv: CSV of per-second metrics of all services; normal.csv and anomalous.csv: the same split before and after injection; inject_time.txt: Unix time of the injection
|
| 21 |
Origin: real metrics recorded by the authors on Sock Shop deployed on Kubernetes with fault injection, published as-is on Zenodo
|
|
|
|
|
|
|
| 22 |
Check: Rename the folder so the path does not reveal the answer. The agent gets data.csv and inject_time.txt and names the root-cause service and the fault type (cpu or mem, the two types of the sibling folders carts, catalogue, orders, payment and user in sock-shop-1.zip); scored by exact match on both
|
| 23 |
Dependencies: none to read the data (CSV and text).
|
campaign_files/2026-10-ml-serving-configs-2/ml293-09/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_root_cause. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Hide exp_22_description.json. The agent gets the run CSV, causes.json and the node and edge lists and names the manipulated variables; scored by exact set match against manipulatedVars.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -20,8 +18,6 @@ Units:
|
|
| 20 |
|
| 21 |
- `dig_twin/exp_coolant/exp_22/run_1/` (2 files)
|
| 22 |
Format: causes.json: cause_start_at, alarms_detected_at, diagnosis_at, cause_end_at, alarms_resolved_at in seconds; exp_22_description.json: scenario text, manipulatedVars and diagnosis; coolant_nodes.csv and coolant_edges.csv: the expert causal graph of the subsystem
|
| 23 |
-
Reference result: labelled_root_cause
|
| 24 |
-
Reference source: manipulatedVars (HP_Pump_Ok, LT_Level_Ok) and the diagnosis in exp_22_description.json, written by the dataset authors who injected the fault
|
| 25 |
Check: Hide exp_22_description.json. The agent gets the run CSV, causes.json and the node and edge lists and names the manipulated variables; scored by exact set match against manipulatedVars
|
| 26 |
Companions (not included): dig_twin/exp_coolant/exp_22/exp_22_description.json; dig_twin/exp_coolant/coolant_nodes.csv; dig_twin/exp_coolant/coolant_edges.csv
|
| 27 |
Dependencies: none to read the data (CSV and JSON).
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Hide exp_22_description.json. The agent gets the run CSV, causes.json and the node and edge lists and names the manipulated variables; scored by exact set match against manipulatedVars.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 18 |
|
| 19 |
- `dig_twin/exp_coolant/exp_22/run_1/` (2 files)
|
| 20 |
Format: causes.json: cause_start_at, alarms_detected_at, diagnosis_at, cause_end_at, alarms_resolved_at in seconds; exp_22_description.json: scenario text, manipulatedVars and diagnosis; coolant_nodes.csv and coolant_edges.csv: the expert causal graph of the subsystem
|
|
|
|
|
|
|
| 21 |
Check: Hide exp_22_description.json. The agent gets the run CSV, causes.json and the node and edge lists and names the manipulated variables; scored by exact set match against manipulatedVars
|
| 22 |
Companions (not included): dig_twin/exp_coolant/exp_22/exp_22_description.json; dig_twin/exp_coolant/coolant_nodes.csv; dig_twin/exp_coolant/coolant_edges.csv
|
| 23 |
Dependencies: none to read the data (CSV and JSON).
|
campaign_files/2026-10-ml-serving-configs-2/ml341-02/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_class. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Hand the agent the wav file under a neutral name (the path holds the label). Task: say whether the machine sound is normal or abnormal. Judge by exact match with the directory label (abnormal for this unit); for a set of files, score accuracy or AUC against the labels.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-SA-4.0
|
|
@@ -22,6 +20,4 @@ Units:
|
|
| 22 |
Read out of the archive: https://zenodo.org/records/3384388/files/6_dB_valve.zip?download=1
|
| 23 |
Format: RIFF WAV, 8 channels, 16 kHz, 16-bit, 10 s
|
| 24 |
Origin: real recordings of industrial machines with factory background noise mixed at the stated SNR by the authors
|
| 25 |
-
Reference result: labelled_class
|
| 26 |
-
Reference source: the directory name of the member (normal or abnormal) set by the dataset authors; the Zenodo record 3384388 description says each model has normal sounds and anomalous sounds and that "To resemble a real-life scenario, various anomalous sounds were recorded (e.g., contamination, leakage, rotating unbalance, and rail damage)"
|
| 27 |
Check: Hand the agent the wav file under a neutral name (the path holds the label). Task: say whether the machine sound is normal or abnormal. Judge by exact match with the directory label (abnormal for this unit); for a set of files, score accuracy or AUC against the labels
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Hand the agent the wav file under a neutral name (the path holds the label). Task: say whether the machine sound is normal or abnormal. Judge by exact match with the directory label (abnormal for this unit); for a set of files, score accuracy or AUC against the labels.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-SA-4.0
|
|
|
|
| 20 |
Read out of the archive: https://zenodo.org/records/3384388/files/6_dB_valve.zip?download=1
|
| 21 |
Format: RIFF WAV, 8 channels, 16 kHz, 16-bit, 10 s
|
| 22 |
Origin: real recordings of industrial machines with factory background noise mixed at the stated SNR by the authors
|
|
|
|
|
|
|
| 23 |
Check: Hand the agent the wav file under a neutral name (the path holds the label). Task: say whether the machine sound is normal or abnormal. Judge by exact match with the directory label (abnormal for this unit); for a set of files, score accuracy or AUC against the labels
|
campaign_files/2026-10-op-rule-calculations-2/medusa-inventory-module-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: test_assertions. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** the repository jest integration-test runner on the inventory module (headless, PostgreSQL), or the Medusa admin REST API for inventory items, levels and reservations
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `packages/modules/inventory/integration-tests/__tests__/inventory-module-service.spec.ts`: Medusa inventory module tests: inventory levels, reservations, stocked, reserved and available quantities including fractional quantities.
|
| 22 |
Format: TypeScript jest integration test, 1295 lines
|
| 23 |
Origin: test written by the project authors; products, quantities and prices are made up
|
| 24 |
-
Reference result: test_assertions
|
| 25 |
-
Reference source: stocked, reserved and available quantities per item and level after each create, update, reserve and delete (for example lines 297-312)
|
| 26 |
Check: give the inventory items, the levels per location and the reservations and ask the rolled-up stocked and reserved quantity per item and the available quantity per level; compare as toEqual does
|
| 27 |
Tools: the repository jest integration-test runner on the inventory module (headless, PostgreSQL), or the Medusa admin REST API for inventory items, levels and reservations
|
| 28 |
Dependencies: Medusa at commit 146c46b0ad1146b40595c8ef586c4d5890982603, Node.js, TypeScript, jest, @medusajs/test-utils, PostgreSQL.
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** the repository jest integration-test runner on the inventory module (headless, PostgreSQL), or the Medusa admin REST API for inventory items, levels and reservations
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `packages/modules/inventory/integration-tests/__tests__/inventory-module-service.spec.ts`: Medusa inventory module tests: inventory levels, reservations, stocked, reserved and available quantities including fractional quantities.
|
| 20 |
Format: TypeScript jest integration test, 1295 lines
|
| 21 |
Origin: test written by the project authors; products, quantities and prices are made up
|
|
|
|
|
|
|
| 22 |
Check: give the inventory items, the levels per location and the reservations and ask the rolled-up stocked and reserved quantity per item and the available quantity per level; compare as toEqual does
|
| 23 |
Tools: the repository jest integration-test runner on the inventory module (headless, PostgreSQL), or the Medusa admin REST API for inventory items, levels and reservations
|
| 24 |
Dependencies: Medusa at commit 146c46b0ad1146b40595c8ef586c4d5890982603, Node.js, TypeScript, jest, @medusajs/test-utils, PostgreSQL.
|
campaign_files/2026-10-op-rule-calculations-2/minethatdata-hillstrom-email-challenge/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: published_metric_values. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** read the CSV with Python csv (or pandas) in a script, group by segment and compute visit, conversion and spend rates and their differences against the control group; write the table to JSON
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `op073-01/Kevin_Hillstrom_MineThatData_E-MailAnalytics_DataMiningChallenge_2008.03.20.csv`: MineThatData E-Mail Analytics and Data Mining Challenge (64,000 customers, men's e-mail, women's e-mail, no e-mail) with the published incremental impact of the two mailings.
|
| 22 |
Format: CSV, 64,000 rows plus header, 3,964,977 bytes; companions: Radcliffe challenge-winning paper (PDF, 410,959 bytes) and the challenge blog post (HTML)
|
| 23 |
Origin: real customers of a US retailer, two-week e-mail test in 2008, released by Kevin Hillstrom for a public analysis challenge
|
| 24 |
-
Reference result: published_metric_values
|
| 25 |
-
Reference source: pdf/HillstromChallenge.pdf, Table 2 "Incremental Impact of the Two Mailings" (radcliffe.txt lines 60-100, PDF page 2): visit rate control 10.62%, men 18.28%, women 15.14%; conversion and spend per head for each group with the increments; the paper reports the challenge win
|
| 26 |
Check: give the CSV and the challenge questions (blog post); ask for the visit rate, conversion rate and spend per head of each group and the increments of each mailing over the control group; compare each percentage against Table 2 to its printed precision and each dollar value to the cent
|
| 27 |
Tools: read the CSV with Python csv (or pandas) in a script, group by segment and compute visit, conversion and spend rates and their differences against the control group; write the table to JSON
|
| 28 |
Companions (not included): pdf/HillstromChallenge.pdf; 2008/03/minethatdata-e-mail-analytics-and-data.html
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** read the CSV with Python csv (or pandas) in a script, group by segment and compute visit, conversion and spend rates and their differences against the control group; write the table to JSON
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 19 |
- `op073-01/Kevin_Hillstrom_MineThatData_E-MailAnalytics_DataMiningChallenge_2008.03.20.csv`: MineThatData E-Mail Analytics and Data Mining Challenge (64,000 customers, men's e-mail, women's e-mail, no e-mail) with the published incremental impact of the two mailings.
|
| 20 |
Format: CSV, 64,000 rows plus header, 3,964,977 bytes; companions: Radcliffe challenge-winning paper (PDF, 410,959 bytes) and the challenge blog post (HTML)
|
| 21 |
Origin: real customers of a US retailer, two-week e-mail test in 2008, released by Kevin Hillstrom for a public analysis challenge
|
|
|
|
|
|
|
| 22 |
Check: give the CSV and the challenge questions (blog post); ask for the visit rate, conversion rate and spend per head of each group and the increments of each mailing over the control group; compare each percentage against Table 2 to its printed precision and each dollar value to the cent
|
| 23 |
Tools: read the CSV with Python csv (or pandas) in a script, group by segment and compute visit, conversion and spend rates and their differences against the control group; write the table to JSON
|
| 24 |
Companions (not included): pdf/HillstromChallenge.pdf; 2008/03/minethatdata-e-mail-analytics-and-data.html
|
campaign_files/2026-10-s-security-detection-2/mitre-brawl-public-game-001/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: attack_technique_label. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Detection task: given the Sysmon and Windows event files only (bsf withheld), list the hosts and process ids or event uuids caused by the intruder; score precision and recall against the bsf events matched by host plus pid. Classification task: for a flagged process or group of events, name the ATT&CK technique; exact match on the technique id of the bsf step that contains the event. Timeline task: order the lateral movement from the starting host sounder-pc (game_metadata starting_host) across hosts; compare to the bsf step order. Ids follow the 2017 ATT&CK numbering (T1086, T1060, T1077 and so on), map to current ids only with the published ATT&CK revocation table.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `s327-01/brawl-public-game-001.zip`: MITRE BRAWL public game 001: Sysmon and Windows event telemetry of a Windows domain while CALDERA ran an automated assume-breach intrusion, with the red bot's own action log (BSF) as ground truth.
|
| 22 |
Format: ZIP (4,967,769 B) of 6 NDJSON files under data/: sysmon, win_events (4,507,435 B, 3,605 raw Windows event XML records), wmi_xml1 (byte-identical copy of win_events), computer_properties (468,530 B), game_metadata (698 B) and bsf (83,742 B, the red bot action log in BRAWL Shared Format)
|
| 23 |
Origin: telemetry recorded by MITRE on its BRAWL cyber range while CALDERA ran unattended; released by MITRE as a research dataset (not the test data of one tool)
|
| 24 |
-
Reference result: attack_technique_label
|
| 25 |
-
Reference source: data/bsf-brawl_public_game_001.json inside the ZIP (CALDERA's own record of what it did, written by the red bot during the game, not inferred afterwards); checked: all 97 process-create events in bsf match a Sysmon process/create record in data/sysmon by host and pid, with the same command line (e.g. reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run /v caldera /d C:\and.exe /f on sounder-pc)
|
| 26 |
Check: Detection task: given the Sysmon and Windows event files only (bsf withheld), list the hosts and process ids or event uuids caused by the intruder; score precision and recall against the bsf events matched by host plus pid. Classification task: for a flagged process or group of events, name the ATT&CK technique; exact match on the technique id of the bsf step that contains the event. Timeline task: order the lateral movement from the starting host sounder-pc (game_metadata starting_host) across hosts; compare to the bsf step order. Ids follow the 2017 ATT&CK numbering (T1086, T1060, T1077 and so on), map to current ids only with the published ATT&CK revocation table.
|
| 27 |
Companions (not included): README.md; LICENSE; sysmon_config.txt
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Detection task: given the Sysmon and Windows event files only (bsf withheld), list the hosts and process ids or event uuids caused by the intruder; score precision and recall against the bsf events matched by host plus pid. Classification task: for a flagged process or group of events, name the ATT&CK technique; exact match on the technique id of the bsf step that contains the event. Timeline task: order the lateral movement from the starting host sounder-pc (game_metadata starting_host) across hosts; compare to the bsf step order. Ids follow the 2017 ATT&CK numbering (T1086, T1060, T1077 and so on), map to current ids only with the published ATT&CK revocation table.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 19 |
- `s327-01/brawl-public-game-001.zip`: MITRE BRAWL public game 001: Sysmon and Windows event telemetry of a Windows domain while CALDERA ran an automated assume-breach intrusion, with the red bot's own action log (BSF) as ground truth.
|
| 20 |
Format: ZIP (4,967,769 B) of 6 NDJSON files under data/: sysmon, win_events (4,507,435 B, 3,605 raw Windows event XML records), wmi_xml1 (byte-identical copy of win_events), computer_properties (468,530 B), game_metadata (698 B) and bsf (83,742 B, the red bot action log in BRAWL Shared Format)
|
| 21 |
Origin: telemetry recorded by MITRE on its BRAWL cyber range while CALDERA ran unattended; released by MITRE as a research dataset (not the test data of one tool)
|
|
|
|
|
|
|
| 22 |
Check: Detection task: given the Sysmon and Windows event files only (bsf withheld), list the hosts and process ids or event uuids caused by the intruder; score precision and recall against the bsf events matched by host plus pid. Classification task: for a flagged process or group of events, name the ATT&CK technique; exact match on the technique id of the bsf step that contains the event. Timeline task: order the lateral movement from the starting host sounder-pc (game_metadata starting_host) across hosts; compare to the bsf step order. Ids follow the 2017 ATT&CK numbering (T1086, T1060, T1077 and so on), map to current ids only with the published ATT&CK revocation table.
|
| 23 |
Companions (not included): README.md; LICENSE; sysmon_config.txt
|
campaign_files/2026-10-sc-science-reference-data-2/metoffice-cru-crutem5/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: published_aggregate_in_companion_file. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: The agent averages the 12 monthly anomalies of each complete year. Checked this round: 168 complete years within 1e-7 (max |diff| 7.9e-8).
|
| 14 |
|
| 15 |
**Licence (SPDX):** OGL-UK-3.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `sc146-05/monthly.csv`: CRUTEM5 (5.0.2.0) global land air temperature anomalies: recompute the annual means from the monthly series.
|
| 22 |
Format: CSV: Time (YYYY-MM), Anomaly (deg C), lower and upper 95% confidence limits; missing as empty
|
| 23 |
Origin: gridded station temperature dataset, global mean series
|
| 24 |
-
Reference result: published_aggregate_in_companion_file
|
| 25 |
-
Reference source: annual.csv column Anomaly (deg C), e.g. line 172 "2020,1.3127614"
|
| 26 |
Check: the agent averages the 12 monthly anomalies of each complete year. Checked this round: 168 complete years within 1e-7 (max |diff| 7.9e-8)
|
| 27 |
Companions (not included): annual.csv (answer; hidden from the agent)
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: The agent averages the 12 monthly anomalies of each complete year. Checked this round: 168 complete years within 1e-7 (max |diff| 7.9e-8).
|
| 12 |
|
| 13 |
**Licence (SPDX):** OGL-UK-3.0
|
|
|
|
| 19 |
- `sc146-05/monthly.csv`: CRUTEM5 (5.0.2.0) global land air temperature anomalies: recompute the annual means from the monthly series.
|
| 20 |
Format: CSV: Time (YYYY-MM), Anomaly (deg C), lower and upper 95% confidence limits; missing as empty
|
| 21 |
Origin: gridded station temperature dataset, global mean series
|
|
|
|
|
|
|
| 22 |
Check: the agent averages the 12 monthly anomalies of each complete year. Checked this round: 168 complete years within 1e-7 (max |diff| 7.9e-8)
|
| 23 |
Companions (not included): annual.csv (answer; hidden from the agent)
|
campaign_files/2026-10-sc-science-reference-data-2/metoffice-hadisdh-land-q/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: published_aggregate_in_companion_file. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: The agent reads the monthly file (624 data rows, 1973-01 to 2024-12) and returns, for each year, the mean of the 12 monthly values in each of the 9 columns. Pass when every |answer - published| <= 0.00001. Checked this round: all 52 x 9 values within 0.00001 (largest difference 5.8e-6).
|
| 14 |
|
| 15 |
**Licence (SPDX):** OGL-UK-3.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `hadobs/hadisdh/data/HadISDH.landq.4.6.1.2024f_global_monthly_full_anoms19912020.txt`: HadISDH.land specific humidity v4.6.1.2024f, global monthly anomalies with 2-sigma uncertainty bounds: compute the annual series (all 9 columns).
|
| 22 |
Format: whitespace text: decimal year-month then 9 columns (anomaly, sample-/+, coverage-/+, station-/+, combined-/+ 2-sigma bounds), 5 decimals, g/kg anomalies from 1991-2020; 3 trailing '#' comment lines
|
| 23 |
Origin: gridded land station humidity record (Willett et al. 2014), area-averaged to a global series by the Met Office Hadley Centre
|
| 24 |
-
Reference result: published_aggregate_in_companion_file
|
| 25 |
-
Reference source: HadISDH.landq.4.6.1.2024f_global_annual_full_anoms19912020.txt: the 9 value columns for each year 1973 to 2024 (52 rows), published by the Met Office beside the monthly file
|
| 26 |
Check: The agent reads the monthly file (624 data rows, 1973-01 to 2024-12) and returns, for each year, the mean of the 12 monthly values in each of the 9 columns. Pass when every |answer - published| <= 0.00001. Checked this round: all 52 x 9 values within 0.00001 (largest difference 5.8e-6).
|
| 27 |
Companions (not included): hadobs/hadisdh/data/HadISDH.landq.4.6.1.2024f_global_annual_full_anoms19912020.txt (published annual series; the answer, withheld from the agent); hadobs/hadisdh/licence_ogl.html (licence and citation page; given to the agent); hadobs/hadisdh/index.html (dataset page: version, variables, anomaly period; given to the agent); hadobs/hadisdh/onlinematerialLAND.html (documentation of the time series files; given to the agent)
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: The agent reads the monthly file (624 data rows, 1973-01 to 2024-12) and returns, for each year, the mean of the 12 monthly values in each of the 9 columns. Pass when every |answer - published| <= 0.00001. Checked this round: all 52 x 9 values within 0.00001 (largest difference 5.8e-6).
|
| 12 |
|
| 13 |
**Licence (SPDX):** OGL-UK-3.0
|
|
|
|
| 19 |
- `hadobs/hadisdh/data/HadISDH.landq.4.6.1.2024f_global_monthly_full_anoms19912020.txt`: HadISDH.land specific humidity v4.6.1.2024f, global monthly anomalies with 2-sigma uncertainty bounds: compute the annual series (all 9 columns).
|
| 20 |
Format: whitespace text: decimal year-month then 9 columns (anomaly, sample-/+, coverage-/+, station-/+, combined-/+ 2-sigma bounds), 5 decimals, g/kg anomalies from 1991-2020; 3 trailing '#' comment lines
|
| 21 |
Origin: gridded land station humidity record (Willett et al. 2014), area-averaged to a global series by the Met Office Hadley Centre
|
|
|
|
|
|
|
| 22 |
Check: The agent reads the monthly file (624 data rows, 1973-01 to 2024-12) and returns, for each year, the mean of the 12 monthly values in each of the 9 columns. Pass when every |answer - published| <= 0.00001. Checked this round: all 52 x 9 values within 0.00001 (largest difference 5.8e-6).
|
| 23 |
Companions (not included): hadobs/hadisdh/data/HadISDH.landq.4.6.1.2024f_global_annual_full_anoms19912020.txt (published annual series; the answer, withheld from the agent); hadobs/hadisdh/licence_ogl.html (licence and citation page; given to the agent); hadobs/hadisdh/index.html (dataset page: version, variables, anomaly period; given to the agent); hadobs/hadisdh/onlinematerialLAND.html (documentation of the time series files; given to the agent)
|
campaign_files/2026-10-sc-science-reference-data-2/metoffice-haduk-regional-england-rainfall/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: published_aggregate_in_same_file. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Strip the five answer columns; the agent sums the monthly totals per season (winter takes December of the previous year) and per year, for years whose months are all present. Scored within the rounding bound: each monthly input is printed to 0.1 mm, so a sum of n inputs carries up to n x 0.05 rounding, plus 0.05 for the printed answer (season 0.2 mm, year 0.65 mm). Checked this round: win 189/189, spr 190/190, sum 190/190, aut 190/190, ann 190/190 within the bound (max |diff| 0.1 for seasons, 0.3 for years).
|
| 14 |
|
| 15 |
**Licence (SPDX):** OGL-UK-3.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `sc094-13/England.txt`: England areal rainfall (HadUK-Grid), 1836 to 2026: recompute the seasonal (win, spr, sum, aut) and annual totals from the monthly totals.
|
| 22 |
Format: plain text, a 5 line header, a column header line, then one row per year: 12 monthly totals in mm (1 decimal) followed by win, spr, sum, aut, ann; missing as ---
|
| 23 |
Origin: agency areal series from the HadUK-Grid observation grid
|
| 24 |
-
Reference result: published_aggregate_in_same_file
|
| 25 |
-
Reference source: columns win (Dec of the previous year plus Jan, Feb), spr (Mar to May), sum (Jun to Aug), aut (Sep to Nov) and ann (Jan to Dec) of England.txt; e.g. line 8: 1837 win 232.6, ann 746.8
|
| 26 |
Check: strip the five answer columns; the agent sums the monthly totals per season (winter takes December of the previous year) and per year, for years whose months are all present. Scored within the rounding bound: each monthly input is printed to 0.1 mm, so a sum of n inputs carries up to n x 0.05 rounding, plus 0.05 for the printed answer (season 0.2 mm, year 0.65 mm). Checked this round: win 189/189, spr 190/190, sum 190/190, aut 190/190, ann 190/190 within the bound (max |diff| 0.1 for seasons, 0.3 for years)
|
| 27 |
Companions (not included): England.txt columns win, spr, sum, aut, ann (answer columns in the same file; hidden from the agent)
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Strip the five answer columns; the agent sums the monthly totals per season (winter takes December of the previous year) and per year, for years whose months are all present. Scored within the rounding bound: each monthly input is printed to 0.1 mm, so a sum of n inputs carries up to n x 0.05 rounding, plus 0.05 for the printed answer (season 0.2 mm, year 0.65 mm). Checked this round: win 189/189, spr 190/190, sum 190/190, aut 190/190, ann 190/190 within the bound (max |diff| 0.1 for seasons, 0.3 for years).
|
| 12 |
|
| 13 |
**Licence (SPDX):** OGL-UK-3.0
|
|
|
|
| 19 |
- `sc094-13/England.txt`: England areal rainfall (HadUK-Grid), 1836 to 2026: recompute the seasonal (win, spr, sum, aut) and annual totals from the monthly totals.
|
| 20 |
Format: plain text, a 5 line header, a column header line, then one row per year: 12 monthly totals in mm (1 decimal) followed by win, spr, sum, aut, ann; missing as ---
|
| 21 |
Origin: agency areal series from the HadUK-Grid observation grid
|
|
|
|
|
|
|
| 22 |
Check: strip the five answer columns; the agent sums the monthly totals per season (winter takes December of the previous year) and per year, for years whose months are all present. Scored within the rounding bound: each monthly input is printed to 0.1 mm, so a sum of n inputs carries up to n x 0.05 rounding, plus 0.05 for the printed answer (season 0.2 mm, year 0.65 mm). Checked this round: win 189/189, spr 190/190, sum 190/190, aut 190/190, ann 190/190 within the bound (max |diff| 0.1 for seasons, 0.3 for years)
|
| 23 |
Companions (not included): England.txt columns win, spr, sum, aut, ann (answer columns in the same file; hidden from the agent)
|
campaign_files/2026-10-sc-science-reference-data/meteoswiss-ogd-smn-ber/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: published_aggregate_file. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Agent groups days by month: mean of tre200d0 rounded half up to 0.1 (score within 0.1: 8 of 1944 months differ by exactly 0.1, from unrounded inputs), max of tre200dx, min of tre200dn, sum of rre150d0, counts of days with tre200dn < 0, tre200dx < 0, tre200dx >= 25, tre200dx >= 30 (all exact over 1936 to 1944 months).
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `sc030-12/ber_d.csv`: MeteoSwiss SwissMetNet Bern-Zollikofen (BER) daily data: recompute the published monthly means, totals, extremes and threshold day counts.
|
| 22 |
Format: semicolon separated CSV, one row per day from 1864; columns are language-neutral parameter codes (tre200d0 etc.) explained in English in the parameter metadata file
|
| 23 |
Origin: agency open data station file as published
|
| 24 |
-
Reference result: published_aggregate_file
|
| 25 |
-
Reference source: monthly file columns tre200m0 (mean), tre200mx, tre200mn (extremes), rre150m0 (precipitation total), tnd00nm0 (frost days), tnd00xm0 (ice days), tnd25xm0 (summer days), tnd30xm0 (hot days)
|
| 26 |
Check: agent groups days by month: mean of tre200d0 rounded half up to 0.1 (score within 0.1: 8 of 1944 months differ by exactly 0.1, from unrounded inputs), max of tre200dx, min of tre200dn, sum of rre150d0, counts of days with tre200dn < 0, tre200dx < 0, tre200dx >= 25, tre200dx >= 30 (all exact over 1936 to 1944 months)
|
| 27 |
Companions (not included): ogd-smn_ber_m.csv (monthly values; answer file); ogd-smn_meta_parameters.csv (parameter codes with English descriptions); terms-of-use page (licence evidence, not packed)
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Agent groups days by month: mean of tre200d0 rounded half up to 0.1 (score within 0.1: 8 of 1944 months differ by exactly 0.1, from unrounded inputs), max of tre200dx, min of tre200dn, sum of rre150d0, counts of days with tre200dn < 0, tre200dx < 0, tre200dx >= 25, tre200dx >= 30 (all exact over 1936 to 1944 months).
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 19 |
- `sc030-12/ber_d.csv`: MeteoSwiss SwissMetNet Bern-Zollikofen (BER) daily data: recompute the published monthly means, totals, extremes and threshold day counts.
|
| 20 |
Format: semicolon separated CSV, one row per day from 1864; columns are language-neutral parameter codes (tre200d0 etc.) explained in English in the parameter metadata file
|
| 21 |
Origin: agency open data station file as published
|
|
|
|
|
|
|
| 22 |
Check: agent groups days by month: mean of tre200d0 rounded half up to 0.1 (score within 0.1: 8 of 1944 months differ by exactly 0.1, from unrounded inputs), max of tre200dx, min of tre200dn, sum of rre150d0, counts of days with tre200dn < 0, tre200dx < 0, tre200dx >= 25, tre200dx >= 30 (all exact over 1936 to 1944 months)
|
| 23 |
Companions (not included): ogd-smn_ber_m.csv (monthly values; answer file); ogd-smn_meta_parameters.csv (parameter codes with English descriptions); terms-of-use page (licence evidence, not packed)
|
campaign_files/2026-10-sc-science-reference-data/metoffice-hadcrut5/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: published_aggregate_file. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Annual anomaly = mean of the 12 monthly anomalies; score within 1e-6 (checked 176 years, max |diff| 5e-8). Confidence limits are not a plain mean and are not asked.
|
| 14 |
|
| 15 |
**Licence (SPDX):** OGL-UK-3.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `sc030-04/hc5_m.csv`: HadCRUT.5.1.0.0 global mean monthly anomalies: recompute the published annual series.
|
| 22 |
Format: CSV: Time, Anomaly (deg C), lower and upper 95% limits; 8 significant decimals
|
| 23 |
Origin: agency climate dataset diagnostics as published
|
| 24 |
-
Reference result: published_aggregate_file
|
| 25 |
-
Reference source: annual CSV column Anomaly (deg C)
|
| 26 |
Check: annual anomaly = mean of the 12 monthly anomalies; score within 1e-6 (checked 176 years, max |diff| 5e-8). Confidence limits are not a plain mean and are not asked
|
| 27 |
Companions (not included): HadCRUT.5.1.0.0.analysis.summary_series.global.annual.csv (answer file); hadcrut5_terms.html (licence evidence, not packed)
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Annual anomaly = mean of the 12 monthly anomalies; score within 1e-6 (checked 176 years, max |diff| 5e-8). Confidence limits are not a plain mean and are not asked.
|
| 12 |
|
| 13 |
**Licence (SPDX):** OGL-UK-3.0
|
|
|
|
| 19 |
- `sc030-04/hc5_m.csv`: HadCRUT.5.1.0.0 global mean monthly anomalies: recompute the published annual series.
|
| 20 |
Format: CSV: Time, Anomaly (deg C), lower and upper 95% limits; 8 significant decimals
|
| 21 |
Origin: agency climate dataset diagnostics as published
|
|
|
|
|
|
|
| 22 |
Check: annual anomaly = mean of the 12 monthly anomalies; score within 1e-6 (checked 176 years, max |diff| 5e-8). Confidence limits are not a plain mean and are not asked
|
| 23 |
Companions (not included): HadCRUT.5.1.0.0.analysis.summary_series.global.annual.csv (answer file); hadcrut5_terms.html (licence evidence, not packed)
|
campaign_files/2026-10-sw-tests-and-exercises-2/medallion-dbt-starter-unit-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_output. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Dbt test --select test_type:unit on DuckDB: exact match of the expect rows; passes when both unit tests pass.
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `models/gold/_gold.yml`: Write gold__deal_recovery (zero cost and no sales handled) and silver__sales_daily (exact duplicates dropped, distinct rows kept) so that both dbt unit tests pass on DuckDB.
|
| 22 |
Format: dbt unit_tests yml (given and expect rows inline)
|
| 23 |
Origin: hand-written dbt unit test fixtures of a starter template
|
| 24 |
-
Reference result: expected_output
|
| 25 |
-
Reference source: expect blocks in models/gold/_gold.yml and models/silver/_silver.yml, written by the author
|
| 26 |
Check: dbt test --select test_type:unit on DuckDB: exact match of the expect rows; passes when both unit tests pass
|
| 27 |
Companions (not included): LICENSE; dbt_project.yml; models/gold/gold__deal_recovery.sql; models/silver/_silver.yml; models/silver/silver__sales_daily.sql; profiles.yml
|
| 28 |
Dependencies: the rest of the dbt project (bronze and silver models the given blocks stand in for) (at commit 0e56b8277af2b86cfcc6c37761fb4007274b4571)
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Dbt test --select test_type:unit on DuckDB: exact match of the expect rows; passes when both unit tests pass.
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `models/gold/_gold.yml`: Write gold__deal_recovery (zero cost and no sales handled) and silver__sales_daily (exact duplicates dropped, distinct rows kept) so that both dbt unit tests pass on DuckDB.
|
| 20 |
Format: dbt unit_tests yml (given and expect rows inline)
|
| 21 |
Origin: hand-written dbt unit test fixtures of a starter template
|
|
|
|
|
|
|
| 22 |
Check: dbt test --select test_type:unit on DuckDB: exact match of the expect rows; passes when both unit tests pass
|
| 23 |
Companions (not included): LICENSE; dbt_project.yml; models/gold/gold__deal_recovery.sql; models/silver/_silver.yml; models/silver/silver__sales_daily.sql; profiles.yml
|
| 24 |
Dependencies: the rest of the dbt project (bronze and silver models the given blocks stand in for) (at commit 0e56b8277af2b86cfcc6c37761fb4007274b4571)
|
campaign_files/2026-10-sw-tests-and-exercises-2/medicare-cclf-connector-unit-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_output. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Dbt test --select test_type:unit at the pinned commit: dbt builds each tested model from the mocked given rows and compares to the expect rows (exact row set match on the listed columns); a unit passes when its unit test passes.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `models/intermediate/_unit_tests.yml`: Medicare CCLF connector: write the intermediate dbt models so that member months collapse into contiguous enrollment spans, adjusted claim versions rank and dedupe correctly and diagnoses pivot by sequence, matching the expected rows of 10 dbt unit tests.
|
| 22 |
Format: dbt unit test YAML (given and expect rows as SQL) + dbt model SQL (hidden)
|
| 23 |
Origin: regression unit tests of an open source claims connector; mock rows written by the maintainers (tool_fixture)
|
| 24 |
-
Reference result: expected_output
|
| 25 |
-
Reference source: the expect rows of each unit test in models/intermediate/_unit_tests.yml, written by the maintainers; the reference model SQL is hidden
|
| 26 |
Check: dbt test --select test_type:unit at the pinned commit: dbt builds each tested model from the mocked given rows and compares to the expect rows (exact row set match on the listed columns); a unit passes when its unit test passes
|
| 27 |
Companions (not included): LICENSE; models/intermediate/int_enrollment.sql; packages.yml
|
| 28 |
Dependencies: dbt-labs/dbt_utils >=0.9.2 (packages.yml); tuva-health/the_tuva_project at revision v0.17.2 (packages.yml); the rest of the connector project (staging models such as stg_enrollment must resolve at parse time)
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Dbt test --select test_type:unit at the pinned commit: dbt builds each tested model from the mocked given rows and compares to the expect rows (exact row set match on the listed columns); a unit passes when its unit test passes.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `models/intermediate/_unit_tests.yml`: Medicare CCLF connector: write the intermediate dbt models so that member months collapse into contiguous enrollment spans, adjusted claim versions rank and dedupe correctly and diagnoses pivot by sequence, matching the expected rows of 10 dbt unit tests.
|
| 20 |
Format: dbt unit test YAML (given and expect rows as SQL) + dbt model SQL (hidden)
|
| 21 |
Origin: regression unit tests of an open source claims connector; mock rows written by the maintainers (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: dbt test --select test_type:unit at the pinned commit: dbt builds each tested model from the mocked given rows and compares to the expect rows (exact row set match on the listed columns); a unit passes when its unit test passes
|
| 23 |
Companions (not included): LICENSE; models/intermediate/int_enrollment.sql; packages.yml
|
| 24 |
Dependencies: dbt-labs/dbt_utils >=0.9.2 (packages.yml); tuva-health/the_tuva_project at revision v0.17.2 (packages.yml); the rest of the connector project (staging models such as stg_enrollment must resolve at parse time)
|
campaign_files/2026-10-sw-tests-and-exercises-2/minibude/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: reference_output_with_tolerance. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: The program reads the deck with --deck data/bm1 and checks each computed energy against ref_energies.out (src/main.cpp line 328 `difference(a, b)` = |a - b| / a, line 339 per-pose check, line 371 overall verdict); a pose fails when 100 times the relative difference exceeds DIFF_TOLERANCE_PCT 0.025 percent (src/bude.h line 11 `#define DIFF_TOLERANCE_PCT 0.025f`); pass = no pose over the tolerance.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `data/bm1/ref_energies.out`: miniBUDE bm1: compute the BUDE molecular docking energies of 65,536 poses for the bm1 deck and match the shipped reference energies.
|
| 22 |
Format: C++17 source + CMake + text deck files and reference energies
|
| 23 |
Origin: HPC mini-app: kernel, input deck and reference energies shipped together (tool_fixture)
|
| 24 |
-
Reference result: reference_output_with_tolerance
|
| 25 |
-
Reference source: data/bm1/ref_energies.out: one reference energy per pose (65,536 lines) for the deck in data/bm1/*.in; the serial model src/serial/fasten.hpp is the reference kernel
|
| 26 |
Check: the program reads the deck with --deck data/bm1 and checks each computed energy against ref_energies.out (src/main.cpp line 328 `difference(a, b)` = |a - b| / a, line 339 per-pose check, line 371 overall verdict); a pose fails when 100 times the relative difference exceeds DIFF_TOLERANCE_PCT 0.025 percent (src/bude.h line 11 `#define DIFF_TOLERANCE_PCT 0.025f`); pass = no pose over the tolerance
|
| 27 |
Companions (not included): LICENSE.txt; README.md; data/README.md; data/bm1/forcefield.in; data/bm1/ligand.in; data/bm1/poses.in; data/bm1/protein.in; src/main.cpp; src/bude.h; src/serial/fasten.hpp; src/serial/model.cmake; CMakeLists.txt
|
| 28 |
Dependencies: C++17 compiler; CMake 3.14 or later
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: The program reads the deck with --deck data/bm1 and checks each computed energy against ref_energies.out (src/main.cpp line 328 `difference(a, b)` = |a - b| / a, line 339 per-pose check, line 371 overall verdict); a pose fails when 100 times the relative difference exceeds DIFF_TOLERANCE_PCT 0.025 percent (src/bude.h line 11 `#define DIFF_TOLERANCE_PCT 0.025f`); pass = no pose over the tolerance.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `data/bm1/ref_energies.out`: miniBUDE bm1: compute the BUDE molecular docking energies of 65,536 poses for the bm1 deck and match the shipped reference energies.
|
| 20 |
Format: C++17 source + CMake + text deck files and reference energies
|
| 21 |
Origin: HPC mini-app: kernel, input deck and reference energies shipped together (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: the program reads the deck with --deck data/bm1 and checks each computed energy against ref_energies.out (src/main.cpp line 328 `difference(a, b)` = |a - b| / a, line 339 per-pose check, line 371 overall verdict); a pose fails when 100 times the relative difference exceeds DIFF_TOLERANCE_PCT 0.025 percent (src/bude.h line 11 `#define DIFF_TOLERANCE_PCT 0.025f`); pass = no pose over the tolerance
|
| 23 |
Companions (not included): LICENSE.txt; README.md; data/README.md; data/bm1/forcefield.in; data/bm1/ligand.in; data/bm1/poses.in; data/bm1/protein.in; src/main.cpp; src/bude.h; src/serial/fasten.hpp; src/serial/model.cmake; CMakeLists.txt
|
| 24 |
Dependencies: C++17 compiler; CMake 3.14 or later
|
campaign_files/2026-10-sw-tests-and-exercises-2/ml-preprocessing-k-bins-50/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_table. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Dbt deps, dbt seed, dbt run, dbt test in integration_tests/; pass = the dbt_utils.equality test on test_k_bins_discretizer_50_bins passes (exact). As a task: hide macros/k_bins_discretizer.sql and ask for one that passes.
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `integration_tests/data/sql/data_k_bins_discretizer_50_bins_expected.csv`: Dbt-ml-preprocessing: SQL k-bins discretizer with 50 bins whose bin numbers must equal the expected seed [main file integration_tests/data/sql/data_k_bins_discretizer_50_bins_expected.csv].
|
| 22 |
Format: dbt test project with input and expected seeds and equality tests
|
| 23 |
Origin: tool_fixture: the project's own tests and expected outputs
|
| 24 |
-
Reference result: expected_table
|
| 25 |
-
Reference source: integration_tests/data/sql/data_k_bins_discretizer_50_bins_expected.csv (300 rows), compared with model test_k_bins_discretizer_50_bins by dbt_utils.equality in integration_tests/models/sql/schema.yml lines 39 to 42
|
| 26 |
Check: dbt deps, dbt seed, dbt run, dbt test in integration_tests/; pass = the dbt_utils.equality test on test_k_bins_discretizer_50_bins passes (exact). As a task: hide macros/k_bins_discretizer.sql and ask for one that passes
|
| 27 |
Companions (not included): LICENSE; dbt_project.yml; integration_tests/data/sql/data_k_bins_discretizer.csv; integration_tests/data/sql/data_normalizer.csv; integration_tests/data/sql/data_normalizer_expected.csv; integration_tests/data/sql/data_quantile_transformer.csv; integration_tests/data/sql/data_quantile_transformer_expected.csv; integration_tests/data/sql/data_standard_scaler.csv; integration_tests/data/sql/data_standard_scaler_expected.csv; integration_tests/dbt_project.yml; integration_tests/macros/equality_with_numeric_tolerance.sql; integration_tests/macros/quantile_transformer_model_macro.sql; integration_tests/macros/standard_scaler_model_macro.sql; integration_tests/macros/test_quantile_transformer_result_with_tolerance.sql; integration_tests/models/sql/schema.yml; integration_tests/models/sql/test_k_bins_discretizer_50_bins.sql; integration_tests/models/sql/test_normalizer.sql; integration_tests/models/sql/test_quantile_transformer.sql; integration_tests/models/sql/test_standard_scaler.sql; integration_tests/packages.yml; macros/.gitkeep; macros/k_bins_discretizer.sql; macros/k_bins_discretizer.yml; macros/label_encoder.sql; macros/label_encoder.yml; macros/max_abs_scaler.sql; macros/max_abs_scaler.yml; macros/min_max_scaler.sql; macros/min_max_scaler.yml; macros/normalizer.sql; macros/normalizer.yml; macros/one_hot_encoder.sql; macros/one_hot_encoder.yml; macros/quantile_transformer.sql; macros/quantile_transformer.yml; macros/robust_scaler.sql; macros/robust_scaler.yml; macros/standard_scaler.sql; macros/standard_scaler.yml
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Dbt deps, dbt seed, dbt run, dbt test in integration_tests/; pass = the dbt_utils.equality test on test_k_bins_discretizer_50_bins passes (exact). As a task: hide macros/k_bins_discretizer.sql and ask for one that passes.
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `integration_tests/data/sql/data_k_bins_discretizer_50_bins_expected.csv`: Dbt-ml-preprocessing: SQL k-bins discretizer with 50 bins whose bin numbers must equal the expected seed [main file integration_tests/data/sql/data_k_bins_discretizer_50_bins_expected.csv].
|
| 20 |
Format: dbt test project with input and expected seeds and equality tests
|
| 21 |
Origin: tool_fixture: the project's own tests and expected outputs
|
|
|
|
|
|
|
| 22 |
Check: dbt deps, dbt seed, dbt run, dbt test in integration_tests/; pass = the dbt_utils.equality test on test_k_bins_discretizer_50_bins passes (exact). As a task: hide macros/k_bins_discretizer.sql and ask for one that passes
|
| 23 |
Companions (not included): LICENSE; dbt_project.yml; integration_tests/data/sql/data_k_bins_discretizer.csv; integration_tests/data/sql/data_normalizer.csv; integration_tests/data/sql/data_normalizer_expected.csv; integration_tests/data/sql/data_quantile_transformer.csv; integration_tests/data/sql/data_quantile_transformer_expected.csv; integration_tests/data/sql/data_standard_scaler.csv; integration_tests/data/sql/data_standard_scaler_expected.csv; integration_tests/dbt_project.yml; integration_tests/macros/equality_with_numeric_tolerance.sql; integration_tests/macros/quantile_transformer_model_macro.sql; integration_tests/macros/standard_scaler_model_macro.sql; integration_tests/macros/test_quantile_transformer_result_with_tolerance.sql; integration_tests/models/sql/schema.yml; integration_tests/models/sql/test_k_bins_discretizer_50_bins.sql; integration_tests/models/sql/test_normalizer.sql; integration_tests/models/sql/test_quantile_transformer.sql; integration_tests/models/sql/test_standard_scaler.sql; integration_tests/packages.yml; macros/.gitkeep; macros/k_bins_discretizer.sql; macros/k_bins_discretizer.yml; macros/label_encoder.sql; macros/label_encoder.yml; macros/max_abs_scaler.sql; macros/max_abs_scaler.yml; macros/min_max_scaler.sql; macros/min_max_scaler.yml; macros/normalizer.sql; macros/normalizer.yml; macros/one_hot_encoder.sql; macros/one_hot_encoder.yml; macros/quantile_transformer.sql; macros/quantile_transformer.yml; macros/robust_scaler.sql; macros/robust_scaler.yml; macros/standard_scaler.sql; macros/standard_scaler.yml
|