Release [run release-20261111T173549Z]

#23
by Battam - opened
This view is limited to 50 files because it contains too many changes. See the raw diff here.
Files changed (50) hide show
  1. CHANGELOG.md +18 -0
  2. README.md +27 -27
  3. README.zh.md +27 -27
  4. campaign_files/2026-10-a-spreadsheets-with-answers-2/ncsu-are-enterprise-budgets/README.md +0 -2
  5. campaign_files/2026-10-a-spreadsheets-with-answers-2/nkc0686-inventory-planning-model/README.md +0 -2
  6. campaign_files/2026-10-b-disk-images/nist-cfreds-dfr-exfat/README.md +0 -2
  7. campaign_files/2026-10-c-repros/ng-rc-paper-code-repro/LICENSE.txt +5 -0
  8. campaign_files/2026-10-c-repros/ng-rc-paper-code-repro/README.md +0 -2
  9. campaign_files/2026-10-c-repros/ngboost-repro/LICENSE.txt +6 -0
  10. campaign_files/2026-10-c-repros/ngboost-repro/README.md +0 -2
  11. campaign_files/2026-10-g-solver-instances-2/neo-malaga-vrp/README.md +0 -8
  12. campaign_files/2026-10-g-solver-instances-2/netlib-lp/README.md +0 -4
  13. campaign_files/2026-10-gt-browser-tests-2/networkmanager-keyfile-tests/README.md +0 -28
  14. campaign_files/2026-10-gt-browser-tests-2/networkmanager-openvpn-import-tests/README.md +0 -28
  15. campaign_files/2026-10-gt-browser-tests-2/node-ical-examples/README.md +0 -4
  16. campaign_files/2026-10-gt-browser-tests-2/node-ical-fixtures/README.md +0 -4
  17. campaign_files/2026-10-m-issue-trackers-2/nationalrtap-boston-express-bus/README.md +0 -4
  18. campaign_files/2026-10-m-issue-trackers-2/newportbus-passenger-gtfs/README.md +0 -4
  19. campaign_files/2026-10-m-issue-trackers-2/nfta-metro-gtfs/README.md +0 -4
  20. campaign_files/2026-10-m-issue-trackers-2/nginx-mailing-list/README.md +0 -4
  21. campaign_files/2026-10-m-issue-trackers-2/nlnetlabs-unbound-users/README.md +0 -4
  22. campaign_files/2026-10-md-media-and-documents/natfarleydev-gurps-press-tests/README.md +0 -4
  23. campaign_files/2026-10-md-media-and-documents/noaa-nos-diving-deeper-dd013014/README.md +0 -3
  24. campaign_files/2026-10-md-media-and-documents/noaa-nos-diving-deeper-dd022014/README.md +0 -4
  25. campaign_files/2026-10-md-media-and-documents/noaa-nos-diving-deeper-dd022615-3/README.md +0 -3
  26. campaign_files/2026-10-md-media-and-documents/noaa-nos-diving-deeper-dd031814/README.md +0 -3
  27. campaign_files/2026-10-md-media-and-documents/noaa-nos-diving-deeper-dd041615-1/README.md +0 -3
  28. campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-dd61-oceaneconomy/README.md +0 -4
  29. campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-dd66-microplastics/README.md +0 -4
  30. campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-dds28-restoration/README.md +0 -4
  31. campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-dds29-lionfish/README.md +0 -4
  32. campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-mw122-exxonvaldez/README.md +0 -4
  33. campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-mw126-garbagepatch/README.md +0 -4
  34. campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-mw137-wetlands-bluecarbon/README.md +0 -4
  35. campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-os6-bluecarbon/README.md +0 -4
  36. campaign_files/2026-10-ml-serving-configs-2/nab-realknowncause/README.md +0 -6
  37. campaign_files/2026-10-ml-serving-configs-2/nab-realtraffic/README.md +0 -4
  38. campaign_files/2026-10-ml-serving-configs-2/nannyml-synthetic-car-loan/README.md +0 -4
  39. campaign_files/2026-10-ml-serving-configs-2/nnapi-cts-test-specs/README.md +0 -6
  40. campaign_files/2026-10-s-security-detection-2/naxsi-waf-unit-tests/README.md +0 -10
  41. campaign_files/2026-10-s-security-detection-2/nobrackets-ctf-2024-challenge-repository/README.md +0 -6
  42. campaign_files/2026-10-s-security-detection/naxsi-unit-tests/README.md +0 -4
  43. campaign_files/2026-10-sc-science-reference-data-2/nasa-power-daily-to-monthly-wichita/README.md +0 -4
  44. campaign_files/2026-10-sc-science-reference-data-2/ncei-lcd-72530094846-2020/README.md +0 -4
  45. campaign_files/2026-10-sc-science-reference-data-2/ncei-ocean-heat-content-basin/README.md +0 -4
  46. campaign_files/2026-10-sc-science-reference-data-2/noaa-cpc-arctic-oscillation-monthly/README.md +0 -4
  47. campaign_files/2026-10-sc-science-reference-data-2/noaa-glerl-great-lakes-hydro-data/README.md +0 -4
  48. campaign_files/2026-10-sc-science-reference-data-2/noaa-glerl-great-lakes-ice-cover/README.md +0 -4
  49. campaign_files/2026-10-sc-science-reference-data-2/noaa-gml-aggi/README.md +0 -4
  50. campaign_files/2026-10-sc-science-reference-data-2/noaa-gml-co2-spo-insitu/README.md +0 -4
CHANGELOG.md CHANGED
@@ -3213,3 +3213,21 @@ Changes to the content of this index, oldest first. There is one entry for each
3213
  - hf-training-records: refused
3214
  - npm: refused
3215
  - stackexchange-api-posts: refused
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
3213
  - hf-training-records: refused
3214
  - npm: refused
3215
  - stackexchange-api-posts: refused
3216
+
3217
+ ## 2026-11-11: sources held back
3218
+
3219
+ - Each source below keeps its newest version that passed every check; its newer batch waits until it passes them:
3220
+ - 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
3221
+ - 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
3222
+ - cfpb-complaints: refused
3223
+ - 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
3224
+ - 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
3225
+ - 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
3226
+ - 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
3227
+ - 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
3228
+ - 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
3229
+ - 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
3230
+ - 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
3231
+ - hf-training-records: refused
3232
+ - npm: refused
3233
+ - 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.15/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.15/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.15/docs/figures/numbers-wide-light.svg" alt="1,806 material sets with 4,191 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,485 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.15/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.15/docs/figures/numbers-wide-dark.svg" alt="1,806 material sets with 4,191 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,485 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.15/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,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.15`.
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.15/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,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.15/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.15/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,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.15/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.15/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 398; 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.15/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.15/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 398; 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,806 material sets with 4,191 units, in 14 collections (1 of them with no material set yet); 1 of the material sets are in no collection.
@@ -132,7 +132,7 @@ A data file may hold the rows of several sources, so the query keeps this one's
132
  | Reproduction packages and runs | 88 | 106 | 870 | 88 | 120 MB | 120 MB |
133
  | SEC filing reviews | 0 | 0 | 0 | 0 | 0 B | 0 B |
134
  | Solver instances | 69 | 193 | 367 | 66 | 127 MB | 127 MB |
135
- | Browser tests | 123 | 439 | 852 | 88 | 32.0 MB | 31.9 MB |
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 |
@@ -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.15/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.15/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.15/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.15/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,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.15/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.15/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.15.">
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.15/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.15/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.15.">
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,364 | 34,485 | 34,356 (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,770 | 3,762 | 3,746 (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,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.15` (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.15`](https://huggingface.co/datasets/Battam/training-data-foundation/tree/release-2026-11-11.15)),
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.15},
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.16/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.16/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.16/docs/figures/numbers-wide-light.svg" alt="1,806 material sets with 4,191 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,220 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.16/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.16/docs/figures/numbers-wide-dark.svg" alt="1,806 material sets with 4,191 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,220 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.16/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.16`.
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.16/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.16/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.16/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.16/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.16/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 398; 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.16/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.16/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 398; 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,806 material sets with 4,191 units, in 14 collections (1 of them with no material set yet); 1 of the material sets are in no collection.
 
132
  | Reproduction packages and runs | 88 | 106 | 870 | 88 | 120 MB | 120 MB |
133
  | SEC filing reviews | 0 | 0 | 0 | 0 | 0 B | 0 B |
134
  | Solver instances | 69 | 193 | 367 | 66 | 127 MB | 127 MB |
135
+ | Browser tests | 123 | 439 | 852 | 88 | 31.9 MB | 31.9 MB |
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 |
 
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.16/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.16/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.16/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.16/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.16/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.16/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.16.">
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.16/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.16/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.16.">
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,099 | 34,220 | 34,091 (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,505 | 3,497 | 3,481 (99.5%) | 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.16` (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.16`](https://huggingface.co/datasets/Battam/training-data-foundation/tree/release-2026-11-11.16)),
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.16},
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/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.15/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.15/docs/figures/numbers-wide-light.zh.svg" alt="1,806 个材料集,共 4,191 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 34,485 行中,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.15/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.15/docs/figures/numbers-wide-dark.zh.svg" alt="1,806 个材料集,共 4,191 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 34,485 行中,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.15/tools/fetch.py --form spreadsheets --sample 3 --out ./data
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.15` 上。
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.15/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,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.15/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.15/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,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.15/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.15/docs/figures/material-wide-light.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 398;媒体和文档 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.15/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.15/docs/figures/material-wide-dark.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 398;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 193;磁盘镜像 179;复现包和运行 106;不属于任何合集 9;SEC 申报审查 0。">
108
  </picture>
109
 
110
  1,806 个材料集,共 4,191 个单元,分在 14 个合集中(其中 1 个合集还没有材料集);其中 1 个材料集不属于任何合集。
@@ -119,7 +119,7 @@ ORDER BY size_bytes LIMIT 20;
119
  | 复现包和运行 | 88 | 106 | 870 | 88 | 120 MB | 120 MB |
120
  | SEC 申报审查 | 0 | 0 | 0 | 0 | 0 B | 0 B |
121
  | 求解器实例 | 69 | 193 | 367 | 66 | 127 MB | 127 MB |
122
- | 浏览器测试 | 123 | 439 | 852 | 88 | 32.0 MB | 31.9 MB |
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 |
@@ -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.15/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.15/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.15/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.15/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,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.15/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.15/docs/figures/steps-wide-light.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.15。">
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.15/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.15/docs/figures/steps-wide-dark.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作��和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.15。">
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,364 | 34,485 | 34,356(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,770 | 3,762 | 3,746(99.6%) | 8:需要登录 7 行、其他错误 1 行 | 0 | 无 |
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.15`(其最新的 CHANGELOG 条目日期为 2026-11-11)。
437
  - 各次发布列在 [CHANGELOG.md](CHANGELOG.md) 中;
438
- 每次发布是一个带有自己发布标签的提交(本次为 [`release-2026-11-11.15`](https://huggingface.co/datasets/Battam/training-data-foundation/tree/release-2026-11-11.15)),
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.15},
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.16/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.16/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.16/docs/figures/numbers-wide-light.zh.svg" alt="1,806 个材料集,共 4,191 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 34,220 行中,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.16/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.16/docs/figures/numbers-wide-dark.zh.svg" alt="1,806 个材料集,共 4,191 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 34,220 行中,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.16/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.16` 上。
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.16/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.16/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/training-data-foundation@release-2026-11-11.16/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.16/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.16/docs/figures/material-wide-light.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 398;媒体和文档 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.16/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.16/docs/figures/material-wide-dark.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 398;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 193;磁盘镜像 179;复现包和运行 106;不属于任何合集 9;SEC 申报审查 0。">
108
  </picture>
109
 
110
  1,806 个材料集,共 4,191 个单元,分在 14 个合集中(其中 1 个合集还没有材料集);其中 1 个材料集不属于任何合集。
 
119
  | 复现包和运行 | 88 | 106 | 870 | 88 | 120 MB | 120 MB |
120
  | SEC 申报审查 | 0 | 0 | 0 | 0 | 0 B | 0 B |
121
  | 求解器实例 | 69 | 193 | 367 | 66 | 127 MB | 127 MB |
122
+ | 浏览器测试 | 123 | 439 | 852 | 88 | 31.9 MB | 31.9 MB |
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 |
 
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.16/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.16/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.16/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.16/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.16/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.16/docs/figures/steps-wide-light.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.16。">
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.16/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.16/docs/figures/steps-wide-dark.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.16。">
184
  </picture>
185
 
186
  术语、每一步,以及每个数字怎样得出,都折叠在下面。
 
234
 
235
  | 层级 | 记录的大小 | 去重后大小 | 读过的行 | 比对过的行 | 一致的行 | 读过但未比对的行 | 没有记录大小的行 | 这些行的估计大小 |
236
  |---|---:|---:|---:|---:|---:|---:|---:|---:|
237
+ | 整个索引 | 4.45 PB | 4.11 PB | 35,099 | 34,220 | 34,091(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,505 | 3,497 | 3,481(99.5%) | 8:需要登录 7 行、其他错误 1 行 | 0 | 无 |
240
 
241
  读过的行是核对在 `meta/sizes.parquet` 中读取的抽样行;
242
  比对过的行与记录的大小一致或不一致,读过但未比对的行没有取到它的文件。
 
433
  <details>
434
  <summary>发布</summary>
435
 
436
+ - 最新发布:`release-2026-11-11.16`(其最新的 CHANGELOG 条目日期为 2026-11-11)。
437
  - 各次发布列在 [CHANGELOG.md](CHANGELOG.md) 中;
438
+ 每次发布是一个带有自己发布标签的提交(本次为 [`release-2026-11-11.16`](https://huggingface.co/datasets/Battam/training-data-foundation/tree/release-2026-11-11.16)),
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.16},
480
  year = {2026}
481
  }
482
  ```
campaign_files/2026-10-a-spreadsheets-with-answers-2/ncsu-are-enterprise-budgets/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is self-contained.
10
 
11
- **Answers:** Each file with an answer has one answer file, at answer/<unit path>.json (the unit path plus .json). Reference result kind: key_formula_values.
12
-
13
  **Tools to open and check:** openpyxl (formulas and cached values); LibreOffice headless recalculation (soffice --headless --convert-to xlsx)
14
 
15
  **Licence (SPDX):** NOASSERTION
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** openpyxl (formulas and cached values); LibreOffice headless recalculation (soffice --headless --convert-to xlsx)
12
 
13
  **Licence (SPDX):** NOASSERTION
campaign_files/2026-10-a-spreadsheets-with-answers-2/nkc0686-inventory-planning-model/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** The file is self-contained.
10
 
11
- **Answers:** Each file with an answer has one answer file, at answer/<unit path>.json (the unit path plus .json). Reference result kind: key_formula_values.
12
-
13
  **Tools to open and check:** openpyxl (formulas and cached values); LibreOffice headless recalculation (soffice --headless --convert-to xlsx)
14
 
15
  **Licence (SPDX):** MIT
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** openpyxl (formulas and cached values); LibreOffice headless recalculation (soffice --headless --convert-to xlsx)
12
 
13
  **Licence (SPDX):** MIT
campaign_files/2026-10-b-disk-images/nist-cfreds-dfr-exfat/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Self-contained: each image opens on its own after gunzip; the exFAT partition starts at sector 2048 or 63 (given in the answer file; mmls also finds it).
10
 
11
- **Answers:** answer/images/<unit file name>.json (unit path plus .json) lists the deleted files named in the image's section of NIST's layout document setup-july-10-2012.pdf: name as stored on disk (UTF-8), path and size where given, disk sector runs, overwrites, with the PDF URL and page numbers; for the large cases the PDF prints only part of its lists, and the file states how many deleted files it names out of the total.
12
-
13
  **Tools to open and check:** gunzip; sleuthkit: mmls to find the partition, fls -o <start sector> -r -d to list deleted entries, icat to recover them; file to identify the partition table.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
8
 
9
  **Self-contained:** Self-contained: each image opens on its own after gunzip; the exFAT partition starts at sector 2048 or 63 (given in the answer file; mmls also finds it).
10
 
 
 
11
  **Tools to open and check:** gunzip; sleuthkit: mmls to find the partition, fls -o <start sector> -r -d to list deleted entries, icat to recover them; file to identify the partition table.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
campaign_files/2026-10-c-repros/ng-rc-paper-code-repro/LICENSE.txt ADDED
@@ -0,0 +1,5 @@
 
 
 
 
 
 
1
+ Licence: MIT
2
+
3
+ - MIT: https://raw.githubusercontent.com/quantinfo/ng-rc-paper-code/8516a6ba47eb627212437e3d842c76074fd68399/LICENSE (publisher: Daniel J. Gauthier, Erik Bollt, Aaron Griffith, Wendson A. S. Barbosa (GitHub quantinfo/ng-rc-paper-code))
4
+
5
+ The publisher's licence file is LICENSE next to this file, fetched from https://raw.githubusercontent.com/quantinfo/ng-rc-paper-code/8516a6ba47eb627212437e3d842c76074fd68399/LICENSE.
campaign_files/2026-10-c-repros/ng-rc-paper-code-repro/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Self-contained: run `python run_repro.py` inside code/; it reads only files inside the package, needs no network and no GPU.
10
 
11
- **Answers:** answer/ngrc-lorenz63-forecast/reported.json gives the values the paper reports for this experiment (reported, tolerance per key, table or figure number, page, how the value was read).
12
-
13
  **Tools to open and check:** Python 3.7 with NumPy 1.20.2 and SciPy 1.6.2, the exact versions the authors list in requirements-exact.txt.
14
 
15
  **Licence (SPDX):** MIT
 
8
 
9
  **Self-contained:** Self-contained: run `python run_repro.py` inside code/; it reads only files inside the package, needs no network and no GPU.
10
 
 
 
11
  **Tools to open and check:** Python 3.7 with NumPy 1.20.2 and SciPy 1.6.2, the exact versions the authors list in requirements-exact.txt.
12
 
13
  **Licence (SPDX):** MIT
campaign_files/2026-10-c-repros/ngboost-repro/LICENSE.txt ADDED
@@ -0,0 +1,6 @@
 
 
 
 
 
 
 
1
+ Licence: Apache-2.0 AND CC-BY-4.0
2
+
3
+ - Apache-2.0: https://raw.githubusercontent.com/stanfordmlgroup/ngboost/6aadc1fc49311606c9abc808c2a1f100880120c5/LICENSE (publisher: Stanford ML Group (GitHub stanfordmlgroup/ngboost))
4
+ - CC-BY-4.0: https://creativecommons.org/licenses/by/4.0/ (publisher: I-Cheng Yeh (UCI Machine Learning Repository, Concrete Compressive Strength))
5
+
6
+ The publisher's licence file is LICENSE next to this file, fetched from https://raw.githubusercontent.com/stanfordmlgroup/ngboost/6aadc1fc49311606c9abc808c2a1f100880120c5/LICENSE.
campaign_files/2026-10-c-repros/ngboost-repro/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Self-contained: run `python run_repro.py` inside code/; it reads only files inside the package, needs no network and no GPU.
10
 
11
- **Answers:** answer/ngboost-concrete-uci/reported.json gives the values the paper reports for this experiment (reported, tolerance per key, table or figure number, page, how the value was read).
12
-
13
  **Tools to open and check:** Python 3.11 with scikit-learn 1.6, NumPy 1.26, SciPy 1.13, pandas 2.2 and xlrd 2.0; exact pins are in the package README.md.
14
 
15
  **Licence (SPDX):** Apache-2.0 AND CC-BY-4.0
 
8
 
9
  **Self-contained:** Self-contained: run `python run_repro.py` inside code/; it reads only files inside the package, needs no network and no GPU.
10
 
 
 
11
  **Tools to open and check:** Python 3.11 with scikit-learn 1.6, NumPy 1.26, SciPy 1.13, pandas 2.2 and xlrd 2.0; exact pins are in the package README.md.
12
 
13
  **Licence (SPDX):** Apache-2.0 AND CC-BY-4.0
campaign_files/2026-10-g-solver-instances-2/neo-malaga-vrp/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 3 of 3 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: Best known total cost plus reference routes (upper bound, not marked optimal). 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:** Tools are named in the check written per unit in the notes.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -22,8 +20,6 @@ Units:
22
  Read out of the archive: https://neo.lcc.uma.es/vrp/wp-content/data/instances/cordeau/C-mdvrp.zip
23
  Format: Cordeau text format (first line "type m n t", then t lines "D Q", then one line per customer and depot "i x y d q f a list e l"); one case = one instance; the answer is routes and their total cost
24
  Origin: published benchmark instance (Cordeau, Gendreau and Laporte (1997), MDVRP p01 (Christofides and Eilon data), 4 depots, 50 customers) as served by the NEO VRP web; recorded tool_fixture
25
- Reference result: best known total cost plus reference routes (upper bound, not marked optimal)
26
- Reference source: p01.res line 1 "576.87" from C-mdvrp-sol.zip.
27
  Check: Program: read the agent routes per depot (format of index.html lines 167 to 175: depot l, vehicle k, then customers, 0 marks the depot); depots are nodes 51 to 54 (index.html line 165: "the last t entries correspond to the t depots"); feasible when each of the 50 customers is on exactly one route, at most 4 routes per depot, each route load at most 80; cost is the total unrounded Euclidean distance; pass when feasible and the total is at most 576.87 plus 0.005
28
  Companions (not included): vrp/wp-content/data/instances/cordeau/C-mdvrp-sol/p01.res; vrp/vrp-instances/description-for-files-of-cordeaus-instances/index.html
29
  Dependencies: no upstream code used
@@ -31,8 +27,6 @@ Units:
31
  Read out of the archive: https://neo.lcc.uma.es/vrp/wp-content/data/instances/cordeau/C-pvrp.zip
32
  Format: Cordeau text format (first line "type m n t", then t lines "D Q", then one line per customer and depot "i x y d q f a list e l"); one case = one instance; the answer is routes and their total cost
33
  Origin: published benchmark instance (Cordeau, Gendreau and Laporte (1997), PVRP p01, 2 days, 50 customers plus a dummy) as served by the NEO VRP web; recorded tool_fixture
34
- Reference result: best known total cost plus reference routes (upper bound, not marked optimal)
35
- Reference source: p01.res line 1 "524.61" from C-pvrp-sol.zip.
36
  Check: Program: read the agent routes per day; each customer i is visited f times on days forming one of its allowed visit combinations (decimal code of the day bit string, index.html line 164); at most 3 routes per day, each route load at most 160; node 51 (p01 line 55) sits at the depot with demand 160 on day 1, so it takes one whole vehicle on day 1 at zero distance and may be left out of the listed routes; cost is the total unrounded Euclidean distance over both days; pass when feasible and the total is at most 524.61 plus 0.005
37
  Companions (not included): vrp/wp-content/data/instances/cordeau/C-pvrp-sol/p01.res; vrp/vrp-instances/description-for-files-of-cordeaus-instances/index.html
38
  Dependencies: no upstream code used
@@ -40,8 +34,6 @@ Units:
40
  Read out of the archive: https://neo.lcc.uma.es/vrp/wp-content/data/instances/cordeau/C-mdvrptw.zip
41
  Format: Cordeau text format (first line "type m n t", then t lines "D Q", then one line per customer and depot "i x y d q f a list e l"); one case = one instance; the answer is routes and their total cost
42
  Origin: published benchmark instance (Cordeau, Laporte and Mercier (2001), MDVRPTW pr01, 4 depots, 48 customers) as served by the NEO VRP web; recorded tool_fixture
43
- Reference result: best known total cost plus reference routes (upper bound, not marked optimal)
44
- Reference source: pr01.res line 1 "1083.98" from C-mdvrptw-sol.zip.
45
  Check: Program: read the agent routes per depot (depots are nodes 49 to 52, each with window 0 to 1000); feasible when each of the 48 customers is on exactly one route, at most 2 routes per depot, each route load at most 200, service starts within each customer window e to l (waiting allowed) and lasts d, and each route duration from depot departure (which may be delayed) to return is at most 500; travel time equals unrounded Euclidean distance; cost is the total distance excluding service time (index.html line 167); pass when feasible and the total is at most 1083.98 plus 0.005
46
  Companions (not included): vrp/wp-content/data/instances/cordeau/C-mdvrptw-sol/pr01.res; vrp/vrp-instances/description-for-files-of-cordeaus-instances/index.html
47
  Dependencies: no upstream code used
 
8
 
9
  **Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 3 of 3 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:** Tools are named in the check written per unit in the notes.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
20
  Read out of the archive: https://neo.lcc.uma.es/vrp/wp-content/data/instances/cordeau/C-mdvrp.zip
21
  Format: Cordeau text format (first line "type m n t", then t lines "D Q", then one line per customer and depot "i x y d q f a list e l"); one case = one instance; the answer is routes and their total cost
22
  Origin: published benchmark instance (Cordeau, Gendreau and Laporte (1997), MDVRP p01 (Christofides and Eilon data), 4 depots, 50 customers) as served by the NEO VRP web; recorded tool_fixture
 
 
23
  Check: Program: read the agent routes per depot (format of index.html lines 167 to 175: depot l, vehicle k, then customers, 0 marks the depot); depots are nodes 51 to 54 (index.html line 165: "the last t entries correspond to the t depots"); feasible when each of the 50 customers is on exactly one route, at most 4 routes per depot, each route load at most 80; cost is the total unrounded Euclidean distance; pass when feasible and the total is at most 576.87 plus 0.005
24
  Companions (not included): vrp/wp-content/data/instances/cordeau/C-mdvrp-sol/p01.res; vrp/vrp-instances/description-for-files-of-cordeaus-instances/index.html
25
  Dependencies: no upstream code used
 
27
  Read out of the archive: https://neo.lcc.uma.es/vrp/wp-content/data/instances/cordeau/C-pvrp.zip
28
  Format: Cordeau text format (first line "type m n t", then t lines "D Q", then one line per customer and depot "i x y d q f a list e l"); one case = one instance; the answer is routes and their total cost
29
  Origin: published benchmark instance (Cordeau, Gendreau and Laporte (1997), PVRP p01, 2 days, 50 customers plus a dummy) as served by the NEO VRP web; recorded tool_fixture
 
 
30
  Check: Program: read the agent routes per day; each customer i is visited f times on days forming one of its allowed visit combinations (decimal code of the day bit string, index.html line 164); at most 3 routes per day, each route load at most 160; node 51 (p01 line 55) sits at the depot with demand 160 on day 1, so it takes one whole vehicle on day 1 at zero distance and may be left out of the listed routes; cost is the total unrounded Euclidean distance over both days; pass when feasible and the total is at most 524.61 plus 0.005
31
  Companions (not included): vrp/wp-content/data/instances/cordeau/C-pvrp-sol/p01.res; vrp/vrp-instances/description-for-files-of-cordeaus-instances/index.html
32
  Dependencies: no upstream code used
 
34
  Read out of the archive: https://neo.lcc.uma.es/vrp/wp-content/data/instances/cordeau/C-mdvrptw.zip
35
  Format: Cordeau text format (first line "type m n t", then t lines "D Q", then one line per customer and depot "i x y d q f a list e l"); one case = one instance; the answer is routes and their total cost
36
  Origin: published benchmark instance (Cordeau, Laporte and Mercier (2001), MDVRPTW pr01, 4 depots, 48 customers) as served by the NEO VRP web; recorded tool_fixture
 
 
37
  Check: Program: read the agent routes per depot (depots are nodes 49 to 52, each with window 0 to 1000); feasible when each of the 48 customers is on exactly one route, at most 2 routes per depot, each route load at most 200, service starts within each customer window e to l (waiting allowed) and lasts d, and each route duration from depot departure (which may be delayed) to return is at most 500; travel time equals unrounded Euclidean distance; cost is the total distance excluding service time (index.html line 167); pass when feasible and the total is at most 1083.98 plus 0.005
38
  Companions (not included): vrp/wp-content/data/instances/cordeau/C-mdvrptw-sol/pr01.res; vrp/vrp-instances/description-for-files-of-cordeaus-instances/index.html
39
  Dependencies: no upstream code used
campaign_files/2026-10-g-solver-instances-2/netlib-lp/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: Published optimal objective value. 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: Compare the agent's optimal value with the readme value at the 11 significant digits printed.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,8 +19,6 @@ Files:
21
  - `lp/data/afiro`: Netlib LP problem AFIRO (28 rows, 32 columns) with the published optimal value -464.75314286.
22
  Format: compressed MPS (Netlib emps format); expands to standard MPS with the companion lp/data/emps.c decompressor; answer in lp/data/readme PROBLEM SUMMARY TABLE
23
  Origin: LP contributed by the Systems Optimization Laboratory at Stanford (readme line 224)
24
- Reference result: published optimal objective value
25
- Reference source: lp/data/readme line 75: "AFIRO 28 32 88 794 -4.6475314286E+02" (PROBLEM SUMMARY TABLE header line 68).
26
  Check: Compare the agent's optimal value with the readme value at the 11 significant digits printed.
27
  Companions (not included): lp/data/readme; lp/data/emps.c
28
  Dependencies: not packed; exact version is the latest highspy release on or before the pinned date, to be filled by relay task 043-T4; 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:** Check: Compare the agent's optimal value with the readme value at the 11 significant digits printed.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `lp/data/afiro`: Netlib LP problem AFIRO (28 rows, 32 columns) with the published optimal value -464.75314286.
20
  Format: compressed MPS (Netlib emps format); expands to standard MPS with the companion lp/data/emps.c decompressor; answer in lp/data/readme PROBLEM SUMMARY TABLE
21
  Origin: LP contributed by the Systems Optimization Laboratory at Stanford (readme line 224)
 
 
22
  Check: Compare the agent's optimal value with the readme value at the 11 significant digits printed.
23
  Companions (not included): lp/data/readme; lp/data/emps.c
24
  Dependencies: not packed; exact version is the latest highspy release on or before the pinned date, to be filled by relay task 043-T4; not packed
campaign_files/2026-10-gt-browser-tests-2/networkmanager-keyfile-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. 13 of 13 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_written_keyfile; asserted_parsed_settings. 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:** write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
14
 
15
  **Licence (SPDX):** GPL-2.0-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Wired`: Wired connection with manual IPv4 and IPv6 addresses, DNS, routes and route options, written as a NetworkManager keyfile.
22
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
23
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
24
- Reference result: expected_written_keyfile
25
- Reference source: src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Wired (whole file) is the byte-exact reference that test-keyfile-settings.c compares the written file with (write_test_connection_and_reread, lines 166-209: "The content of ... differs from ...").
26
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_Wired with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
27
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
28
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -30,8 +26,6 @@ Files:
30
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Wired_IP6`: Wired connection with IPv4 disabled and a manual IPv6 address, gateway and DNS, written as a NetworkManager keyfile.
31
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
32
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
33
- Reference result: expected_written_keyfile
34
- Reference source: src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Wired_IP6 (whole file) is the byte-exact reference that test-keyfile-settings.c compares the written file with (write_test_connection_and_reread, lines 166-209: "The content of ... differs from ..."); the settings to make come from test_write_ip6_wired_connection, lines 637-701 of test-keyfile-settings.c: id "Work Wired IP6", uuid 0bef2d09-50a3-56b9-912a-5dc941284e3e, autoconnect false, IPv4 disabled, IPv6 manual with abcd::beef/64, gateway dcba::beef, DNS 1::cafe and dns-search wallaceandgromit.com
35
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_Wired_IP6 with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
36
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
37
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -39,8 +33,6 @@ Files:
39
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Wireless`: Wi-Fi connection with SSID, BSSID and MTU and automatic IP, written as a NetworkManager keyfile.
40
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
41
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
42
- Reference result: expected_written_keyfile
43
- Reference source: src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Wireless (whole file) is the byte-exact reference that test-keyfile-settings.c compares the written file with (write_test_connection_and_reread, lines 166-209: "The content of ... differs from ..."); the settings to make come from test_write_wireless_connection, lines 810-876 of test-keyfile-settings.c: id "Work Wireless", uuid e9b337d3-6aa0-552a-822c-4b71c8ddec2e, autoconnect false, timestamp, BSSID aa:b9:a1:74:55:44, SSID 1337, MTU 1000, IPv4 and IPv6 automatic
44
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_Wireless with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
45
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
46
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -48,8 +40,6 @@ Files:
48
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_GSM`: Mobile broadband (GSM) connection with APN, user name, PIN, network id and SIM ids, written as a NetworkManager keyfile.
49
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
50
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
51
- Reference result: expected_written_keyfile
52
- Reference source: src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_GSM (whole file) is the byte-exact reference that test-keyfile-settings.c compares the written file with (write_test_connection_and_reread, lines 166-209: "The content of ... differs from ..."); the settings to make come from test_write_gsm_connection, lines 1352-1416 of test-keyfile-settings.c: id "T-Mobile Funkadelic 2", uuid 952d369e-52c7-5686-ad8c-37ca7e47f8b2, autoconnect false, APN internet2.voicestream.com, user name george.clinton.again, a test password, PIN 123456, network id 254098, home-only, device id and device uid MODEM1, SIM id 89148000000060671234 and SIM operator id 310260
53
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_GSM with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
54
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
55
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -57,8 +47,6 @@ Files:
57
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Infiniband`: InfiniBand connection with a 20-byte hardware address, MTU and datagram transport, written as a NetworkManager keyfile.
58
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
59
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
60
- Reference result: expected_written_keyfile
61
- Reference source: src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Infiniband (whole file) is the byte-exact reference that test-keyfile-settings.c compares the written file with (write_test_connection_and_reread, lines 166-209: "The content of ... differs from ..."); the settings to make come from test_write_infiniband_connection, lines 1898-1954 of test-keyfile-settings.c: id "Work InfiniBand", uuid c27325f5-9eff-517a-9d96-d7897785fa5b, autoconnect false, MAC 99:88:77:66:55:44:AB:BC:CD:DE:EF:F0:0A:1B:2C:3D:4E:5F:6F:BA, MTU 900, transport mode datagram, IPv4 and IPv6 automatic
62
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_Infiniband with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
63
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
64
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -66,8 +54,6 @@ Files:
66
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Bridge_Main`: Network bridge br0 with a static IPv4 address and gateway, written as a NetworkManager keyfile.
67
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
68
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
69
- Reference result: expected_written_keyfile
70
- Reference source: src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Bridge_Main (whole file) is the byte-exact reference that test-keyfile-settings.c compares the written file with (write_test_connection_and_reread, lines 166-209: "The content of ... differs from ..."); the settings to make come from test_write_bridge_main, lines 1990-2055 of test-keyfile-settings.c: id "Test Write Bridge Main", uuid b23c15e0-815b-5e6e-a5f9-aea49237aa35, interface br0, bridge setting with defaults, IPv4 manual 1.2.3.4/24 with gateway 1.1.1.1, IPv6 automatic
71
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_Bridge_Main with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
72
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
73
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -75,8 +61,6 @@ Files:
75
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Wired_Connection`: Wired connection keyfile with manual IPv4 and IPv6 addresses, routes with attributes and a bogus DNS entry that must be dropped.
76
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
77
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
78
- Reference result: asserted_parsed_settings
79
- Reference source: the assertions of test_read_valid_wired_connection, lines 255-404 of test-keyfile-settings.c, which reads src/core/settings/plugins/keyfile/tests/keyfiles/Test_Wired_Connection with keyfile_read_connection_from_file: id, uuid, timestamp and autoconnect of the connection; MAC address and MTU of the wired setting; IPv4 method manual, 2 DNS servers (the bogus entry dropped), 10 addresses in the asserted order with gateway 2.3.4.6, 14 routes with metrics and route attributes; IPv6 method manual, 2 DNS servers, 3 dns-search domains, addresses and routes
80
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; Test_Wired_Connection is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_valid_wired_connection (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting; the reader's warnings and notes listed with NMTST_EXPECT_NM_WARN / NMTST_EXPECT_NM_INFO at lines 268-280 (missing prefix lengths, the invalid DNS server 'bogus', trailing semicolons) are expected and do not fail the judge
81
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
82
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -84,8 +68,6 @@ Files:
84
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Wireless_Connection`: Wi-Fi connection keyfile with an SSID written as a byte list, a BSSID and a fixed timestamp.
85
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
86
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
87
- Reference result: asserted_parsed_settings
88
- Reference source: the assertions of test_read_valid_wireless_connection, lines 778-807 of test-keyfile-settings.c, which reads src/core/settings/plugins/keyfile/tests/keyfiles/Test_Wireless_Connection with keyfile_read_connection_from_file: id "Test Wireless Connection", uuid 2f962388-e5f3-45af-a62c-ac220b8f7baa, timestamp 1226604314, autoconnect false, BSSID 00:1a:33:44:99:82, IPv4 method auto
89
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; Test_Wireless_Connection is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_valid_wireless_connection (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting
90
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
91
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -93,8 +75,6 @@ Files:
93
  - `src/core/settings/plugins/keyfile/tests/keyfiles/ATT_Data_Connect_BT`: Bluetooth dial-up (DUN) mobile connection keyfile with GSM APN and credentials and odd serial parity.
94
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
95
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
96
- Reference result: asserted_parsed_settings
97
- Reference source: the assertions of test_read_bt_dun_connection, lines 1205-1242 of test-keyfile-settings.c, which reads src/core/settings/plugins/keyfile/tests/keyfiles/ATT_Data_Connect_BT with keyfile_read_connection_from_file: id "AT&T Data Connect BT", uuid, Bluetooth address 00:11:22:33:44:55 with connection type dun, GSM APN ISP.CINGULAR, user name ISP@CINGULARGPRS.COM, the test password, serial parity odd
98
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; ATT_Data_Connect_BT is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_bt_dun_connection (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting
99
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
100
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -102,8 +82,6 @@ Files:
102
  - `src/core/settings/plugins/keyfile/tests/keyfiles/ATT_Data_Connect_Plain`: Plain GSM mobile broadband connection keyfile with APN, credentials, PIN, network id and SIM ids.
103
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
104
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
105
- Reference result: asserted_parsed_settings
106
- Reference source: the assertions of test_read_gsm_connection, lines 1314-1349 of test-keyfile-settings.c, which reads src/core/settings/plugins/keyfile/tests/keyfiles/ATT_Data_Connect_Plain with keyfile_read_connection_from_file: id "AT&T Data Connect", type gsm, no Bluetooth setting, APN ISP.CINGULAR, user name ISP@CINGULARGPRS.COM, the test password, network id 24005, PIN 2345, device id, SIM id 89148000000060671234, SIM operator id 310260, serial parity odd
107
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; ATT_Data_Connect_Plain is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_gsm_connection (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting
108
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
109
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -111,8 +89,6 @@ Files:
111
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Bridge_Main`: Network bridge keyfile with STP, priority, forward delay, hello time, max age, ageing time and multicast snooping.
112
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
113
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
114
- Reference result: asserted_parsed_settings
115
- Reference source: the assertions of test_read_bridge_main, lines 1957-1987 of test-keyfile-settings.c, which reads src/core/settings/plugins/keyfile/tests/keyfiles/Test_Bridge_Main with keyfile_read_connection_from_file: id "Test Bridge Main", uuid 8f061643-fe41-4d4c-a8d9-097d26e2ad3a, interface br0, IPv4 auto, forward delay 2, STP on, priority 32744, hello time 7, max age 39, ageing time 235352, multicast snooping off
116
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; Test_Bridge_Main is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_bridge_main (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting
117
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
118
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -120,8 +96,6 @@ Files:
120
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_New_Wireless_Group_Names`: WPA-PSK Wi-Fi connection keyfile using the short group names [wifi] and [wifi-security].
121
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
122
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
123
- Reference result: asserted_parsed_settings
124
- Reference source: the assertions of test_read_new_wireless_group_names, lines 2226-2250 of test-keyfile-settings.c, which reads src/core/settings/plugins/keyfile/tests/keyfiles/Test_New_Wireless_Group_Names with keyfile_read_connection_from_file: SSID foobar, mode infrastructure, key management wpa-psk, the test passphrase
125
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; Test_New_Wireless_Group_Names is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_new_wireless_group_names (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting
126
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
127
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
@@ -129,8 +103,6 @@ Files:
129
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Wired_Connection_MAC_Case`: Wired connection keyfile whose MAC address is written in mixed case and must be read as the same address.
130
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
131
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
132
- Reference result: asserted_parsed_settings
133
- Reference source: the assertions of test_read_wired_mac_case, lines 704-731 of test-keyfile-settings.c, which reads src/core/settings/plugins/keyfile/tests/keyfiles/Test_Wired_Connection_MAC_Case with keyfile_read_connection_from_file: id "Test Wired Connection MAC Case", uuid 4e80a56d-c99f-4aad-a6dd-b449bc398c57, MAC address 00:11:aa:bb:cc:55 matched case-insensitively (nm_utils_hwaddr_matches)
134
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; Test_Wired_Connection_MAC_Case is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_wired_mac_case (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting; MAC addresses compare case-insensitively, as nm_utils_hwaddr_matches does; the reader's notes listed with NMTST_EXPECT_NM_INFO at lines 712-714 are expected
135
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
136
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 13 of 13 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:** write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
12
 
13
  **Licence (SPDX):** GPL-2.0-or-later
 
19
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Wired`: Wired connection with manual IPv4 and IPv6 addresses, DNS, routes and route options, written as a NetworkManager keyfile.
20
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
21
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
22
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_Wired with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
23
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
24
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
26
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Wired_IP6`: Wired connection with IPv4 disabled and a manual IPv6 address, gateway and DNS, written as a NetworkManager keyfile.
27
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
28
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
29
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_Wired_IP6 with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
30
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
31
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
33
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Wireless`: Wi-Fi connection with SSID, BSSID and MTU and automatic IP, written as a NetworkManager keyfile.
34
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
35
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
36
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_Wireless with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
37
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
38
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
40
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_GSM`: Mobile broadband (GSM) connection with APN, user name, PIN, network id and SIM ids, written as a NetworkManager keyfile.
41
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
42
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
43
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_GSM with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
44
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
45
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
47
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Infiniband`: InfiniBand connection with a 20-byte hardware address, MTU and datagram transport, written as a NetworkManager keyfile.
48
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
49
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
50
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_Infiniband with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
51
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
52
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
54
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Write_Bridge_Main`: Network bridge br0 with a static IPv4 address and gateway, written as a NetworkManager keyfile.
55
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
56
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
57
  Check: Final configuration state, no screenshot needed. Parse the keyfile the agent leaves in /etc/NetworkManager/system-connections (or the path the task names) and the reference Test_Write_Bridge_Main with a GKeyFile or INI parser (case kept, no interpolation) and require the same groups, the same keys in each group and equal values (exact string match, order ignored; empty groups such as [proxy] count). The stricter form is the upstream one: byte equality with the reference, which holds for a file written by NetworkManager's own keyfile writer at the pinned commit. Optionally reload the agent's file with libnm at the pinned commit to confirm it parses
58
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
59
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
61
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Wired_Connection`: Wired connection keyfile with manual IPv4 and IPv6 addresses, routes with attributes and a bogus DNS entry that must be dropped.
62
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
63
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
64
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; Test_Wired_Connection is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_valid_wired_connection (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting; the reader's warnings and notes listed with NMTST_EXPECT_NM_WARN / NMTST_EXPECT_NM_INFO at lines 268-280 (missing prefix lengths, the invalid DNS server 'bogus', trailing semicolons) are expected and do not fail the judge
65
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
66
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
68
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Wireless_Connection`: Wi-Fi connection keyfile with an SSID written as a byte list, a BSSID and a fixed timestamp.
69
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
70
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
71
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; Test_Wireless_Connection is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_valid_wireless_connection (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting
72
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
73
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
75
  - `src/core/settings/plugins/keyfile/tests/keyfiles/ATT_Data_Connect_BT`: Bluetooth dial-up (DUN) mobile connection keyfile with GSM APN and credentials and odd serial parity.
76
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
77
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
78
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; ATT_Data_Connect_BT is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_bt_dun_connection (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting
79
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
80
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
82
  - `src/core/settings/plugins/keyfile/tests/keyfiles/ATT_Data_Connect_Plain`: Plain GSM mobile broadband connection keyfile with APN, credentials, PIN, network id and SIM ids.
83
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
84
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
85
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; ATT_Data_Connect_Plain is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_gsm_connection (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting
86
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
87
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
89
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Bridge_Main`: Network bridge keyfile with STP, priority, forward delay, hello time, max age, ageing time and multicast snooping.
90
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
91
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
92
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; Test_Bridge_Main is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_bridge_main (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting
93
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
94
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
96
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_New_Wireless_Group_Names`: WPA-PSK Wi-Fi connection keyfile using the short group names [wifi] and [wifi-security].
97
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
98
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
99
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; Test_New_Wireless_Group_Names is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_new_wireless_group_names (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting
100
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
101
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
 
103
  - `src/core/settings/plugins/keyfile/tests/keyfiles/Test_Wired_Connection_MAC_Case`: Wired connection keyfile whose MAC address is written in mixed case and must be read as the same address.
104
  Format: NetworkManager keyfile (GLib GKeyFile INI format: [group] sections of key=value lines; list values end with ';')
105
  Origin: keyfile fixtures of NetworkManager's keyfile settings plugin tests (src/core/settings/plugins/keyfile/tests), read or written by test-keyfile-settings.c (tool_fixture)
 
 
106
  Check: Final configuration state, no screenshot needed. The task gives the connection settings that the assertions fix and asks for a keyfile that NetworkManager loads as that connection; Test_Wired_Connection_MAC_Case is one correct answer. Judge the agent's keyfile by loading it with NetworkManager's keyfile reader at the pinned commit (libnm) and checking every asserted value of test_read_wired_mac_case (exact equality, as the g_assert_cmpstr / g_assert_cmpint / nm_utils_hwaddr_matches calls do). A parser-only judge also works: parse the file with a GKeyFile or INI parser and compare the asserted keys, accepting both the legacy group names (802-3-ethernet, 802-11-wireless) and the current ones (ethernet, wifi) that the keyfile reader maps to the same setting; MAC addresses compare case-insensitively, as nm_utils_hwaddr_matches does; the reader's notes listed with NMTST_EXPECT_NM_INFO at lines 712-714 are expected
107
  Tools: write the keyfile under /etc/NetworkManager/system-connections (mode 0600) with a text editor or a script (Python configparser with interpolation off and case kept, or GLib GKeyFile), or create it with nmcli (`nmcli connection add type ethernet con-name ... ipv4.method manual ipv4.addresses ...`, then `nmcli connection show` / `nmcli -t -f all connection show ID` to read it back); NetworkManager's keyfile reader (libnm, `nm_keyfile_read`) or the test harness at the pinned commit can reload the file to confirm it parses to the same settings
108
  Companions (not included): src/core/settings/plugins/keyfile/tests/test-keyfile-settings.c; COPYING
campaign_files/2026-10-gt-browser-tests-2/networkmanager-openvpn-import-tests/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 13 of 13 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_imported_vpn_settings. 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:** `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
14
 
15
  **Licence (SPDX):** GPL-2.0-or-later
@@ -21,8 +19,6 @@ Files:
21
  - `properties/tests/conf/password.conf`: OpenVPN client profile with username and password authentication (auth-user-pass), remote test.server.com port 443, rport 2352, AES-256-CBC, reneg-sec 0, to be imported as a NetworkManager VPN connection.
22
  Format: OpenVPN client configuration file (.conf, one directive per line)
23
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_password_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
24
- Reference result: expected_imported_vpn_settings
25
- Reference source: test_password_import in properties/tests/test-import-export.c lines 193-234; registered at line 1439 (_add_test_func_simple): connection id "password"; connection-type "password"; dev "tun"; reneg-seconds "0"; remote "test.server.com:443"; port "2352"; cipher "AES-256-CBC"; ca "<dir>/cacert.pem"; absent: proto-tcp, comp-lzo, compress, float, cert, key, static-key, static-key-direction, ta, ta-dir, data-ciphers, data-ciphers-fallback, local-ip, remote-ip, auth; no password or cert-pass secret. Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
26
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
27
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
28
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -30,8 +26,6 @@ Files:
30
  - `properties/tests/conf/proxy-http.ovpn`
31
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
32
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_proxy_http_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
33
- Reference result: expected_imported_vpn_settings
34
- Reference source: test_proxy_http_import in properties/tests/test-import-export.c lines 792-829; registered at line 1489: connection-type "password"; dev "tun"; proto-tcp "yes"; reneg-seconds "0"; remote "[aa:bb::1]:1194:udp"; port "2352"; cipher "AES-256-CBC"; proxy-type "http"; proxy-port "8080"; http-proxy-username "myusername"; secret http-proxy-password "mypassword" (read from the companion httpauthfile); absent: comp-lzo, compress, float, cert, key, static-key, static-key-direction, ta, ta-dir, data-ciphers, data-ciphers-fallback, local-ip, remote-ip, auth. Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
35
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. The secret http-proxy-password is asserted as "mypassword": it must be stored under [vpn-secrets] (or the password flags must say it is agent-owned, in which case the judge reads it from the task's secret store); the companion httpauthfile must sit beside the unit when importing.
36
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
37
  Companions (not included): properties/tests/conf/httpauthfile; properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -39,8 +33,6 @@ Files:
39
  - `properties/tests/conf/proxy-http-with-auth.ovpn`: OpenVPN client profile over TCP through an HTTP proxy proxy.domain.tld:3128 with basic authentication from a credentials file, to be imported as a NetworkManager VPN connection.
40
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
41
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_proxy_http_with_auth_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
42
- Reference result: expected_imported_vpn_settings
43
- Reference source: test_proxy_http_with_auth_import in properties/tests/test-import-export.c lines 858-895; registered at line 1492: connection-type "password"; dev "tun"; proto-tcp "yes"; reneg-seconds "0"; remote "test.server.com:443"; port "2352"; cipher "AES-256-CBC"; proxy-type "http"; proxy-server "proxy.domain.tld"; proxy-port "3128"; http-proxy-username "myusername"; secret http-proxy-password "mypassword"; absent: comp-lzo, compress, float, cert, key, static-key, static-key-direction, ta, ta-dir, data-ciphers, data-ciphers-fallback, local-ip, remote-ip, auth. Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
44
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. The secret http-proxy-password must be stored under [vpn-secrets] (or be agent-owned per its flags); the companion httpauthfile must sit beside the unit when importing.
45
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
46
  Companions (not included): properties/tests/conf/httpauthfile; properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -48,8 +40,6 @@ Files:
48
  - `properties/tests/conf/proxy-socks.ovpn`
49
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
50
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_proxy_socks_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
51
- Reference result: expected_imported_vpn_settings
52
- Reference source: test_proxy_socks_import in properties/tests/test-import-export.c lines 898-933; registered at line 1494: connection-type "password"; dev "tun"; proto-tcp "yes"; reneg-seconds "0"; remote "test.server.com:443"; port "2352"; cipher "AES-256-CBC"; proxy-type "socks"; proxy-port "1080"; absent: comp-lzo, compress, float, cert, key, static-key, static-key-direction, ta, ta-dir, data-ciphers, data-ciphers-fallback, local-ip, remote-ip, auth. Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
53
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
54
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
55
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -57,8 +47,6 @@ Files:
57
  - `properties/tests/conf/route.ovpn`: OpenVPN TLS client profile with three static routes, to be imported as a NetworkManager VPN connection with IPv4 routes.
58
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
59
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_route_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
60
- Reference result: expected_imported_vpn_settings
61
- Reference source: test_route_import in properties/tests/test-import-export.c lines 1011-1059; registered at line 1515: connection-type "tls"; exactly 3 IPv4 routes in order: 1.2.3.0/24 next hop 1.2.3.254 metric 99; 5.6.7.8/30 no next hop, metric -1 (unset); Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
62
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. Routes are read from the [ipv4] section of the keyfile: the same count, order, destination, prefix, next hop and metric (no metric written means -1), compared exactly as the test does with g_assert_cmpint and g_assert_cmpstr.
63
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
64
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -66,8 +54,6 @@ Files:
66
  - `properties/tests/conf/tun-opts.conf`: OpenVPN client profile with tunnel options tun-mtu 1300, mssfix and fragment 1200, to be imported as a NetworkManager VPN connection.
67
  Format: OpenVPN client configuration file (.conf, one directive per line)
68
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_tun_opts_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
69
- Reference result: expected_imported_vpn_settings
70
- Reference source: test_tun_opts_import in properties/tests/test-import-export.c lines 776-789; registered at line 1477: mssfix "yes"; tunnel-mtu "1300"; fragment-size "1200". Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
71
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
72
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
73
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -75,8 +61,6 @@ Files:
75
  - `properties/tests/conf/compress.ovpn`: OpenVPN client profile with compression options allow-compression asym, comp-lzo and compress lzo, to be imported as a NetworkManager VPN connection.
76
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
77
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_compress_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
78
- Reference result: expected_imported_vpn_settings
79
- Reference source: test_compress_import in properties/tests/test-import-export.c lines 1062-1075; registered at line 1518: allow-compression "asym"; comp-lzo "adaptive"; compress "lzo". Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
80
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
81
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
82
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -84,8 +68,6 @@ Files:
84
  - `properties/tests/conf/static.ovpn`
85
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
86
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_static_key_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
87
- Reference result: expected_imported_vpn_settings
88
- Reference source: test_static_key_import in properties/tests/test-import-export.c lines 674-715 with the data of line 1463 ("static-import-1": file static.ovpn, id "static", direction "1"): connection id "static"; connection-type "static-key"; dev "tun"; static-key-direction "1"; static-key "<dir>/static.key"; absent: proto-tcp, comp-lzo, compress, float, reneg-seconds, port, ta, ta-dir, cipher, data-ciphers, data-ciphers-fallback, auth; no password or cert-pass secret. Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
89
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
90
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
91
  Companions (not included): properties/tests/conf/static.key; properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -93,8 +75,6 @@ Files:
93
  - `properties/tests/conf/ping-with-exit.ovpn`: OpenVPN TLS client profile with keep-alive options ping 10 and ping-exit 120, to be imported as a NetworkManager VPN connection.
94
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
95
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_ping_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
96
- Reference result: expected_imported_vpn_settings
97
- Reference source: test_ping_import in properties/tests/test-import-export.c lines 757-773 with the data of line 1480 ("ping-with-exit-import": "10", "120", NULL): ping "10"; ping-exit "120"; ping-restart absent. Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
98
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
99
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
100
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -102,8 +82,6 @@ Files:
102
  - `properties/tests/conf/device.ovpn`: OpenVPN client profile with a named tunnel device (dev company0, dev-type tun), to be imported as a NetworkManager VPN connection.
103
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
104
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_device_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
105
- Reference result: expected_imported_vpn_settings
106
- Reference source: test_device_import in properties/tests/test-import-export.c lines 951-966 with the data of line 1500 ("device-import-default": "company0", "tun"): dev "company0"; dev-type "tun". Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
107
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
108
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
109
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -111,8 +89,6 @@ Files:
111
  - `properties/tests/conf/tls3.ovpn`: OpenVPN TLS client profile with tls-crypt, verify-x509-name, remote-cert-tls server and TLS version bounds 1.0 to 1.2, to be imported as a NetworkManager VPN connection.
112
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
113
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_tls_import_3 in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
114
- Reference result: expected_imported_vpn_settings
115
- Reference source: test_tls_import_3 in properties/tests/test-import-export.c lines 388-435; registered at line 1449: connection id "tls3"; connection-type "tls"; dev "tun"; comp-lzo "adaptive"; float "yes"; remote "173.8.149.245:1194"; tls-remote "/CN=myvpn.company.com"; verify-x509-name "subject:C=US, L=Cambridge, CN=GNOME, emailAddress=networkmanager-list@gnome.org"; remote-cert-tls "server"; ca "<dir>/keys/mg8.ca"; cert "<dir>/keys/clee.crt"; key "<dir>/keys/clee.key"; tls-crypt "<dir>/keys/46.key"; tls-version-min "1.0"; tls-version-max "1.2"; absent: proto-tcp, reneg-seconds, port, static-key, static-key-direction, cipher, data-ciphers, data-ciphers-fallback, local-ip, remote-ip, auth; no password or cert-pass secret. Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
116
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. The key files under keys/ are not needed: only their absolute paths are compared.
117
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
118
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -120,8 +96,6 @@ Files:
120
  - `properties/tests/conf/tls4.ovpn`: OpenVPN TLS client profile with tls-crypt-v2, verify-x509-name, remote-cert-tls server and tls-version-min 1.0 or-highest, to be imported as a NetworkManager VPN connection.
121
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
122
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_tls_import_4 in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
123
- Reference result: expected_imported_vpn_settings
124
- Reference source: test_tls_import_4 in properties/tests/test-import-export.c lines 438-486; registered at line 1452: connection id "tls4"; connection-type "tls"; dev "tun"; comp-lzo "adaptive"; float "yes"; remote "173.8.149.245:1194"; tls-remote "/CN=myvpn.company.com"; verify-x509-name "subject:C=US, L=Cambridge, CN=GNOME, emailAddress=networkmanager-list@gnome.org"; remote-cert-tls "server"; ca "<dir>/keys/mg8.ca"; cert "<dir>/keys/clee.crt"; key "<dir>/keys/clee.key"; tls-crypt-v2 "<dir>/keys/46.key"; tls-version-min "1.0"; tls-version-min-or-highest "yes"; tls-version-max "1.2"; absent: proto-tcp, reneg-seconds, port, static-key, static-key-direction, cipher, data-ciphers, data-ciphers-fallback, local-ip, remote-ip, auth; no password or cert-pass secret. Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
125
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. The key files under keys/ are not needed: only their absolute paths are compared.
126
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
127
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
@@ -129,8 +103,6 @@ Files:
129
  - `properties/tests/conf/tls-inline.ovpn`: OpenVPN TLS client profile with inline <ca>, <cert>, <key>, <tls-auth> and <crl-verify> blocks (and a NUL byte inside a comment), to be imported as a NetworkManager VPN connection that extracts each block to its own file.
130
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
131
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_tls_inline_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
132
- Reference result: expected_imported_vpn_settings
133
- Reference source: test_tls_inline_import in properties/tests/test-import-export.c lines 510-561; registered at line 1443; file comparison in test_file_contents, lines 489-508: connection id "tls-inline"; connection-type "tls"; dev "tun"; compress "lz4-v2"; float "yes"; remote "173.8.149.245:1194"; tls-remote "/CN=myvpn.company.com"; remote-cert-tls "server"; ta-dir "1"; absent: proto-tcp, comp-lzo, reneg-seconds, port, static-key, static-key-direction, cipher, data-ciphers, data-ciphers-fallback, local-ip, remote-ip, auth; the files named by ca, cert, key, ta and crl-verify-file must be byte-identical to tls-inline-ca.pem, tls-inline-cert.pem, tls-inline-key.pem, tls-inline-ta.pem and tls-inline-crl-verify-file.pem; no password or cert-pass secret. Key names are the string values of the NM_OPENVPN_KEY_* constants in shared/nm-service-defines.h; <dir> is the directory that holds the imported file (SRCDIR in the test)
134
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. For the extracted files, read the paths stored in ca, cert, key, ta and crl-verify-file and compare each file byte for byte with the matching companion PEM (upstream uses g_assert_cmpmem); where they are written is free.
135
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
136
  Companions (not included): properties/tests/conf/tls-inline-ca.pem; properties/tests/conf/tls-inline-cert.pem; properties/tests/conf/tls-inline-key.pem; properties/tests/conf/tls-inline-ta.pem; properties/tests/conf/tls-inline-crl-verify-file.pem; properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
8
 
9
  **Self-contained:** Whether each file needs other upstream files is not stated. 13 of 13 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:** `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
12
 
13
  **Licence (SPDX):** GPL-2.0-or-later
 
19
  - `properties/tests/conf/password.conf`: OpenVPN client profile with username and password authentication (auth-user-pass), remote test.server.com port 443, rport 2352, AES-256-CBC, reneg-sec 0, to be imported as a NetworkManager VPN connection.
20
  Format: OpenVPN client configuration file (.conf, one directive per line)
21
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_password_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
22
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
23
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
24
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
26
  - `properties/tests/conf/proxy-http.ovpn`
27
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
28
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_proxy_http_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
29
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. The secret http-proxy-password is asserted as "mypassword": it must be stored under [vpn-secrets] (or the password flags must say it is agent-owned, in which case the judge reads it from the task's secret store); the companion httpauthfile must sit beside the unit when importing.
30
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
31
  Companions (not included): properties/tests/conf/httpauthfile; properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
33
  - `properties/tests/conf/proxy-http-with-auth.ovpn`: OpenVPN client profile over TCP through an HTTP proxy proxy.domain.tld:3128 with basic authentication from a credentials file, to be imported as a NetworkManager VPN connection.
34
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
35
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_proxy_http_with_auth_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
36
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. The secret http-proxy-password must be stored under [vpn-secrets] (or be agent-owned per its flags); the companion httpauthfile must sit beside the unit when importing.
37
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
38
  Companions (not included): properties/tests/conf/httpauthfile; properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
40
  - `properties/tests/conf/proxy-socks.ovpn`
41
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
42
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_proxy_socks_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
43
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
44
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
45
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
47
  - `properties/tests/conf/route.ovpn`: OpenVPN TLS client profile with three static routes, to be imported as a NetworkManager VPN connection with IPv4 routes.
48
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
49
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_route_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
50
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. Routes are read from the [ipv4] section of the keyfile: the same count, order, destination, prefix, next hop and metric (no metric written means -1), compared exactly as the test does with g_assert_cmpint and g_assert_cmpstr.
51
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
52
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
54
  - `properties/tests/conf/tun-opts.conf`: OpenVPN client profile with tunnel options tun-mtu 1300, mssfix and fragment 1200, to be imported as a NetworkManager VPN connection.
55
  Format: OpenVPN client configuration file (.conf, one directive per line)
56
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_tun_opts_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
57
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
58
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
59
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
61
  - `properties/tests/conf/compress.ovpn`: OpenVPN client profile with compression options allow-compression asym, comp-lzo and compress lzo, to be imported as a NetworkManager VPN connection.
62
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
63
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_compress_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
64
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
65
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
66
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
68
  - `properties/tests/conf/static.ovpn`
69
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
70
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_static_key_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
71
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
72
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
73
  Companions (not included): properties/tests/conf/static.key; properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
75
  - `properties/tests/conf/ping-with-exit.ovpn`: OpenVPN TLS client profile with keep-alive options ping 10 and ping-exit 120, to be imported as a NetworkManager VPN connection.
76
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
77
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_ping_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
78
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
79
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
80
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
82
  - `properties/tests/conf/device.ovpn`: OpenVPN client profile with a named tunnel device (dev company0, dev-type tun), to be imported as a NetworkManager VPN connection.
83
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
84
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_device_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
85
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets].
86
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
87
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
89
  - `properties/tests/conf/tls3.ovpn`: OpenVPN TLS client profile with tls-crypt, verify-x509-name, remote-cert-tls server and TLS version bounds 1.0 to 1.2, to be imported as a NetworkManager VPN connection.
90
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
91
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_tls_import_3 in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
92
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. The key files under keys/ are not needed: only their absolute paths are compared.
93
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
94
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
96
  - `properties/tests/conf/tls4.ovpn`: OpenVPN TLS client profile with tls-crypt-v2, verify-x509-name, remote-cert-tls server and tls-version-min 1.0 or-highest, to be imported as a NetworkManager VPN connection.
97
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
98
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_tls_import_4 in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
99
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. The key files under keys/ are not needed: only their absolute paths are compared.
100
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
101
  Companions (not included): properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
 
103
  - `properties/tests/conf/tls-inline.ovpn`: OpenVPN TLS client profile with inline <ca>, <cert>, <key>, <tls-auth> and <crl-verify> blocks (and a NUL byte inside a comment), to be imported as a NetworkManager VPN connection that extracts each block to its own file.
104
  Format: OpenVPN client configuration file (.ovpn or .conf, one directive per line)
105
  Origin: OpenVPN client configuration fixture of the NetworkManager-openvpn import and export unit tests (properties/tests/conf), imported by test_tls_inline_import in properties/tests/test-import-export.c through nm_vpn_editor_plugin_import (tool_fixture)
 
 
106
  Check: Final configuration state, no screenshot needed. Parse the keyfile NetworkManager writes for the imported connection (/etc/NetworkManager/system-connections/<id>.nmconnection, or the keyfile the agent leaves at the path the task names) with an INI or GKeyFile parser; All comparisons are exact string equality, as upstream uses g_assert_cmpstr with == through _check_item; the connection id is the file name without its extension and the uuid is free (the test asserts no uuid only before saving). Secrets the test asserts as NULL must not appear under [vpn-secrets]. For the extracted files, read the paths stored in ca, cert, key, ta and crl-verify-file and compare each file byte for byte with the matching companion PEM (upstream uses g_assert_cmpmem); where they are written is free.
107
  Tools: `nmcli connection import type openvpn file <unit>` (runs the same NetworkManager-openvpn import plugin headless), then read /etc/NetworkManager/system-connections/<id>.nmconnection; or write the keyfile directly ([connection] type=vpn, [vpn] service-type=org.freedesktop.NetworkManager.openvpn plus the data items, [vpn-secrets] for stored secrets) with a text editor or Python configparser; or `nmcli connection add type vpn vpn-type openvpn vpn.data "key=value, ..."`
108
  Companions (not included): properties/tests/conf/tls-inline-ca.pem; properties/tests/conf/tls-inline-cert.pem; properties/tests/conf/tls-inline-key.pem; properties/tests/conf/tls-inline-ta.pem; properties/tests/conf/tls-inline-crl-verify-file.pem; properties/tests/test-import-export.c; shared/nm-service-defines.h; COPYING
campaign_files/2026-10-gt-browser-tests-2/node-ical-examples/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:** node-ical expandRecurringEvent (Node.js), or Python icalendar plus recurring-ical-events; a script lists every occurrence in 2017 with its local start time in Europe/Berlin and writes it to a text file
14
 
15
  **Licence (SPDX):** Apache-2.0
@@ -21,8 +19,6 @@ Files:
21
  - `examples/example-rrule.ics`: Expand a recurring event with exceptions over 2017 in Europe/Berlin and list its occurrences.
22
  Format: iCalendar (.ics); text occurrence list as answer
23
  Origin: node-ical example and snapshot test (tool_fixture)
24
- Reference result: golden_output_files
25
- Reference source: test/snapshots/example-rrule-vanilla.txt, the stdout of examples/example-rrule-vanilla.js under TZ=Europe/Berlin (test/examples-snapshot.test.js line 28 sets the zone)
26
  Check: Final file state: the agent writes the occurrence list; compare occurrence start instants and titles with the snapshot (the vanilla script prints them with toLocaleDateString en-US, lines 35-44); exact match after newline normalization when the same format is asked. No screenshot
27
  Tools: node-ical expandRecurringEvent (Node.js), or Python icalendar plus recurring-ical-events; a script lists every occurrence in 2017 with its local start time in Europe/Berlin and writes it to a text file
28
  Companions (not included): test/snapshots/example-rrule-vanilla.txt; examples/example-rrule-vanilla.js
 
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:** node-ical expandRecurringEvent (Node.js), or Python icalendar plus recurring-ical-events; a script lists every occurrence in 2017 with its local start time in Europe/Berlin and writes it to a text file
12
 
13
  **Licence (SPDX):** Apache-2.0
 
19
  - `examples/example-rrule.ics`: Expand a recurring event with exceptions over 2017 in Europe/Berlin and list its occurrences.
20
  Format: iCalendar (.ics); text occurrence list as answer
21
  Origin: node-ical example and snapshot test (tool_fixture)
 
 
22
  Check: Final file state: the agent writes the occurrence list; compare occurrence start instants and titles with the snapshot (the vanilla script prints them with toLocaleDateString en-US, lines 35-44); exact match after newline normalization when the same format is asked. No screenshot
23
  Tools: node-ical expandRecurringEvent (Node.js), or Python icalendar plus recurring-ical-events; a script lists every occurrence in 2017 with its local start time in Europe/Berlin and writes it to a text file
24
  Companions (not included): test/snapshots/example-rrule-vanilla.txt; examples/example-rrule-vanilla.js
campaign_files/2026-10-gt-browser-tests-2/node-ical-fixtures/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: inline_expected_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:** node-ical parseFile, or Python icalendar Calendar.from_ical; a script writes SUMMARY, LOCATION, DESCRIPTION and CATEGORIES unescaped to a JSON file
14
 
15
  **Licence (SPDX):** Apache-2.0
@@ -21,7 +19,5 @@ Files:
21
  - `test/fixtures/text-escaped-backslashes.ics`: Unescape iCalendar TEXT values that contain backslashes, commas and newline escapes.
22
  Format: iCalendar (.ics); expected values in the test file
23
  Origin: node-ical regression fixture (tool_fixture)
24
- Reference result: inline_expected_values
25
- Reference source: test/regression-fixes.test.js lines 31-51: summary C:\new\Notes, location Folder\, room; desk, description with literal \n and \N plus two real line breaks, categories [C:\new, Notes, drafts, Folder\]
26
  Check: Final file state: the JSON values must equal the expected strings and list exactly (assert.equal and assert.deepEqual). No screenshot
27
  Tools: node-ical parseFile, or Python icalendar Calendar.from_ical; a script writes SUMMARY, LOCATION, DESCRIPTION and CATEGORIES unescaped to a JSON file
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** node-ical parseFile, or Python icalendar Calendar.from_ical; a script writes SUMMARY, LOCATION, DESCRIPTION and CATEGORIES unescaped to a JSON file
12
 
13
  **Licence (SPDX):** Apache-2.0
 
19
  - `test/fixtures/text-escaped-backslashes.ics`: Unescape iCalendar TEXT values that contain backslashes, commas and newline escapes.
20
  Format: iCalendar (.ics); expected values in the test file
21
  Origin: node-ical regression fixture (tool_fixture)
 
 
22
  Check: Final file state: the JSON values must equal the expected strings and list exactly (assert.equal and assert.deepEqual). No screenshot
23
  Tools: node-ical parseFile, or Python icalendar Calendar.from_ical; a script writes SUMMARY, LOCATION, DESCRIPTION and CATEGORIES unescaped to a JSON file
campaign_files/2026-10-m-issue-trackers-2/nationalrtap-boston-express-bus/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://rapid.nationalrtap.org/GTFSFileManagement/UserUploadFiles/11782/fare_attributes.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 Boston Express Bus (Massachusetts and New Hampshire), uploaded to the National RTAP GTFS Builder file manager, at https://rapid.nationalrtap.org/GTFSFileManagement/UserUploadFiles/11782/fare_attributes.zip. calendar.txt and its companions were read by member out of the zip (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://rapid.nationalrtap.org/GTFSFileManagement/UserUploadFiles/11782/fare_attributes.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 Boston Express Bus (Massachusetts and New Hampshire), uploaded to the National RTAP GTFS Builder file manager, at https://rapid.nationalrtap.org/GTFSFileManagement/UserUploadFiles/11782/fare_attributes.zip. calendar.txt and its companions were read by member out of the zip (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/newportbus-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/newportbus/gtfs/newportbus_1791215720.zip
23
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
24
  Origin: Live static GTFS feed published by Newport Bus (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/newportbus/gtfs/newportbus_1791215720.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/newportbus/gtfs/newportbus_1791215720.zip
21
  Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
22
  Origin: Live static GTFS feed published by Newport Bus (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/newportbus/gtfs/newportbus_1791215720.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/nfta-metro-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):** LicenseRef-NFTA-GTFS-License-Agreement
@@ -22,8 +20,6 @@ Units:
22
  Read out of the archive: https://metro.nfta.com/__googletransit/google_transit.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 Niagara Frontier Transportation Authority (NFTA) at https://metro.nfta.com/__googletransit/google_transit.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):** LicenseRef-NFTA-GTFS-License-Agreement
 
20
  Read out of the archive: https://metro.nfta.com/__googletransit/google_transit.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 Niagara Frontier Transportation Authority (NFTA) at https://metro.nfta.com/__googletransit/google_transit.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/nginx-mailing-list/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. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,7 +19,5 @@ Files:
21
  - `m027-10/2019-March.txt`: Protect against php files being send as static files (7 messages, 2019-03-05 to 2019-03-26).
22
  Format: Pipermail month archive, mbox text: 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. Addresses written as 'x at y'; forum gateway posts carry the forum address with the poster's name.
23
  Origin: Real list traffic in a closed past month of the list's Pipermail archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer.
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.
26
  Check: Exact match against values computed from the pinned month file: parse it as mbox, 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 and compare sender names. People are counted by person, not address (the row's scale names the people). Deterministic. The thread-cutting program was checked against a hand reading on 2 threads of this list (spec general rule 5): on the chosen thread the header closure and the Subject lines agree message for message; on a second thread every difference was traced by hand to the In-Reply-To headers (a renamed subject inside the reply chain, or a separate root with the same subject), and the program followed the headers correctly. Questions that need the body (what was asked, what fixed it) need a model or human judge and are listed separately. Hand-check second sample: 'nginx servers share session or cookies' (8 messages; header closure and Subject lines agree).
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. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
 
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. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `m027-10/2019-March.txt`: Protect against php files being send as static files (7 messages, 2019-03-05 to 2019-03-26).
20
  Format: Pipermail month archive, mbox text: 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. Addresses written as 'x at y'; forum gateway posts carry the forum address with the poster's name.
21
  Origin: Real list traffic in a closed past month of the list's Pipermail archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer.
 
 
22
  Check: Exact match against values computed from the pinned month file: parse it as mbox, 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 and compare sender names. People are counted by person, not address (the row's scale names the people). Deterministic. The thread-cutting program was checked against a hand reading on 2 threads of this list (spec general rule 5): on the chosen thread the header closure and the Subject lines agree message for message; on a second thread every difference was traced by hand to the In-Reply-To headers (a renamed subject inside the reply chain, or a separate root with the same subject), and the program followed the headers correctly. Questions that need the body (what was asked, what fixed it) need a model or human judge and are listed separately. Hand-check second sample: 'nginx servers share session or cookies' (8 messages; header closure and Subject lines agree).
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. For HyperKitty, curl the archive REST API (?format=json) and walk the parent links.
campaign_files/2026-10-m-issue-trackers-2/nlnetlabs-unbound-users/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
  - `m089-09/2019-March.txt.gz`: Caching in libunbound (8 messages, 2019-03-21 to 2019-03-21).
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 Pipermail 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, 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 and compare sender names. Message-IDs are compared after removing double quotes (one archive writes a quoted local part that replies cite unquoted; found in the hand check). 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). Deterministic. The program was checked by hand on 2 threads of this source before giving answers: the chosen thread (read message by message) and 'TLS certificate question about unbound 1.9.2' (22 messages by headers; 20 carry variants of the subject line, all linked by In-Reply-To); it agreed on both. On the chosen thread the last message renames the subject to 'libunbound & libevent (was: Re: Caching in libunbound)' and is linked by In-Reply-To, so it counts.
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
  - `m089-09/2019-March.txt.gz`: Caching in libunbound (8 messages, 2019-03-21 to 2019-03-21).
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 Pipermail 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, 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 and compare sender names. Message-IDs are compared after removing double quotes (one archive writes a quoted local part that replies cite unquoted; found in the hand check). 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). Deterministic. The program was checked by hand on 2 threads of this source before giving answers: the chosen thread (read message by message) and 'TLS certificate question about unbound 1.9.2' (22 messages by headers; 20 carry variants of the subject line, all linked by In-Reply-To); it agreed on both. On the chosen thread the last message renames the subject to 'libunbound & libevent (was: Re: Caching in libunbound)' and is linked by In-Reply-To, so it counts.
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/natfarleydev-gurps-press-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 stat-block (tytanic, headless Typst compile and pixel compare); typst compile for a single render
14
 
15
  **Licence (SPDX):** MIT-0
@@ -21,8 +19,6 @@ Files:
21
  - `tests/stat-block/test.typ`: Gurps-press Typst test stat-block: three tabletop game character stat blocks (all defaults, one of everything with sorted lists, points hidden) on a 12 cm page, compared with a reference rendering.
22
  Format: Typst source (.typ) plus reference PNG
23
  Origin: regression test of the package author; ref/1.png is the accepted rendering that tytanic compares against in CI
24
- Reference result: reference rendering (PNG) compared pixel by pixel
25
- Reference source: tests/stat-block/ref/1.png (340 x 422 px), saved by the author and checked in CI on three tytanic versions
26
  Check: compile test.typ with tytanic at 72 ppi and compare the page with ref/1.png pixel by pixel; a pixel deviates when any channel differs by more than max delta, and the page fails when any pixel deviates; page count must match; hide ref/ when posing the task
27
  Tools: tt run stat-block (tytanic, headless Typst compile and pixel compare); typst compile for a single render
28
  Companions (not included): tests/stat-block/ref/1.png; typst.toml; src/lib.typ; src/character.typ; src/damage.typ; src/stat-block.typ; src/text.typ; src/util.typ; LICENSE
 
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 stat-block (tytanic, headless Typst compile and pixel compare); typst compile for a single render
12
 
13
  **Licence (SPDX):** MIT-0
 
19
  - `tests/stat-block/test.typ`: Gurps-press Typst test stat-block: three tabletop game character stat blocks (all defaults, one of everything with sorted lists, points hidden) on a 12 cm page, compared with a reference rendering.
20
  Format: Typst source (.typ) plus reference PNG
21
  Origin: regression test of the package author; ref/1.png is the accepted rendering that tytanic compares against in CI
 
 
22
  Check: compile test.typ with tytanic at 72 ppi and compare the page with ref/1.png pixel by pixel; a pixel deviates when any channel differs by more than max delta, and the page fails when any pixel deviates; page count must match; hide ref/ when posing the task
23
  Tools: tt run stat-block (tytanic, headless Typst compile and pixel compare); typst compile for a single render
24
  Companions (not included): tests/stat-block/ref/1.png; typst.toml; src/lib.typ; src/character.typ; src/damage.typ; src/stat-block.typ; src/text.typ; src/util.typ; LICENSE
campaign_files/2026-10-md-media-and-documents/noaa-nos-diving-deeper-dd013014/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,6 +19,5 @@ Files:
21
  - `podcast/jan14/dd013014.mp3`: NOAA Diving Deeper episode 55 "Planning Ocean Uses" audio with its published transcript.
22
  Format: MP3, about 10.4 min (10,001,270 bytes), interview recorded for the podcast
23
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels
26
  Companions (not included): podcast/jan14/dd55-ocean-uses.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/jan14/dd013014.mp3`: NOAA Diving Deeper episode 55 "Planning Ocean Uses" audio with its published transcript.
20
  Format: MP3, about 10.4 min (10,001,270 bytes), interview recorded for the podcast
21
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels
23
  Companions (not included): podcast/jan14/dd55-ocean-uses.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-diving-deeper-dd022014/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `podcast/feb14/dd022014.mp3`: NOAA Diving Deeper episode 56 "The Intracoastal Waterway" audio with its published transcript.
22
  Format: MP3, about 10.9 min (10,455,021 bytes), host plus two guests, interview recorded for the podcast
23
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
- Reference source: podcast/feb14/dd56-icw.html, section "Transcript", from "HOST: Welcome to Diving Deeper. I'm your host, Kate Nielsen.
26
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels
27
  Companions (not included): podcast/feb14/dd56-icw.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/feb14/dd022014.mp3`: NOAA Diving Deeper episode 56 "The Intracoastal Waterway" audio with its published transcript.
20
  Format: MP3, about 10.9 min (10,455,021 bytes), host plus two guests, interview recorded for the podcast
21
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
 
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels
23
  Companions (not included): podcast/feb14/dd56-icw.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-diving-deeper-dd022615-3/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark against the published transcript with the speaker labels (HOST, guest name) removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded; speaker turns may be scored separately as a diarisation check.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,6 +19,5 @@ Files:
21
  - `podcast/feb15/dd022615-3.mp3`: NOAA Diving Deeper episode 59 "Invasive Species" audio with its published transcript.
22
  Format: MP3 44.1 kHz, about 19.3 min, two-person interview
23
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark against the published transcript with the speaker labels (HOST, guest name) removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded; speaker turns may be scored separately as a diarisation check
26
  Companions (not included): podcast/feb15/dd59-invasivespecies.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark against the published transcript with the speaker labels (HOST, guest name) removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded; speaker turns may be scored separately as a diarisation check.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/feb15/dd022615-3.mp3`: NOAA Diving Deeper episode 59 "Invasive Species" audio with its published transcript.
20
  Format: MP3 44.1 kHz, about 19.3 min, two-person interview
21
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark against the published transcript with the speaker labels (HOST, guest name) removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded; speaker turns may be scored separately as a diarisation check
23
  Companions (not included): podcast/feb15/dd59-invasivespecies.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-diving-deeper-dd031814/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,6 +19,5 @@ Files:
21
  - `podcast/mar14/dd031814.mp3`: NOAA Diving Deeper episode 57 "Tides and Currents" audio with its published transcript.
22
  Format: MP3, about 15.5 min (14,936,321 bytes), interview recorded for the podcast
23
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels
26
  Companions (not included): podcast/mar14/dd57-tides-currents.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/mar14/dd031814.mp3`: NOAA Diving Deeper episode 57 "Tides and Currents" audio with its published transcript.
20
  Format: MP3, about 15.5 min (14,936,321 bytes), interview recorded for the podcast
21
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels
23
  Companions (not included): podcast/mar14/dd57-tides-currents.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-diving-deeper-dd041615-1/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark against the published transcript with the speaker labels (HOST, guest name) removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded; speaker turns may be scored separately as a diarisation check.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,6 +19,5 @@ Files:
21
  - `podcast/apr15/dd041615-1.mp3`: NOAA Diving Deeper episode 60 "GPS on Bench Marks" audio with its published transcript.
22
  Format: MP3 44.1 kHz, about 9.6 min, two-person interview
23
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark against the published transcript with the speaker labels (HOST, guest name) removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded; speaker turns may be scored separately as a diarisation check
26
  Companions (not included): podcast/apr15/dd60-gpsbenchmarks.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark against the published transcript with the speaker labels (HOST, guest name) removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded; speaker turns may be scored separately as a diarisation check.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/apr15/dd041615-1.mp3`: NOAA Diving Deeper episode 60 "GPS on Bench Marks" audio with its published transcript.
20
  Format: MP3 44.1 kHz, about 9.6 min, two-person interview
21
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark against the published transcript with the speaker labels (HOST, guest name) removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded; speaker turns may be scored separately as a diarisation check
23
  Companions (not included): podcast/apr15/dd60-gpsbenchmarks.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-dd61-oceaneconomy/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `podcast/june15/dd062515.mp3`: NOAA Diving Deeper episode 61 "Ocean Economy" audio with its published transcript.
22
  Format: MP3, 16,533,973 bytes, about 827 seconds (13.8 min, afinfo estimate); host interview with one guest; two voices; series intro and outro music
23
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
- Reference source: ... That’s all for today’s show, thanks for tuning in!"; about 2,038 words as extracted including the speaker labels; labels: HOST and JEFF ADKINS; the last line of the section is the page's series blurb, not speech, and is dropped from the reference; the transcript's first host turn carries the HOST label
26
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
27
  Companions (not included): podcast/june15/dd61-oceaneconomy.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/june15/dd062515.mp3`: NOAA Diving Deeper episode 61 "Ocean Economy" audio with its published transcript.
20
  Format: MP3, 16,533,973 bytes, about 827 seconds (13.8 min, afinfo estimate); host interview with one guest; two voices; series intro and outro music
21
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
 
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
23
  Companions (not included): podcast/june15/dd61-oceaneconomy.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-dd66-microplastics/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `podcast/june16/dd063016.mp3`: NOAA Diving Deeper episode 66 "Microplastics" audio with its published transcript.
22
  Format: MP3, 18,726,169 bytes, about 936 seconds (15.6 min, afinfo estimate); host interview with one guest; two voices; series intro and outro music
23
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
- Reference source: ... Thanks for tuning in, that’s all for today’s show!"; about 2,357 words as extracted including the speaker labels; labels: HOST and AMY UHRIN (the first host turn has no label); the last line of the section is the page's series blurb, not speech, and is dropped from the reference; the first host turn has no label
26
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
27
  Companions (not included): podcast/june16/dd66-microplastics.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/june16/dd063016.mp3`: NOAA Diving Deeper episode 66 "Microplastics" audio with its published transcript.
20
  Format: MP3, 18,726,169 bytes, about 936 seconds (15.6 min, afinfo estimate); host interview with one guest; two voices; series intro and outro music
21
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
 
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
23
  Companions (not included): podcast/june16/dd66-microplastics.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-dds28-restoration/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `podcast/jan14/dds011614.mp3`: NOAA Diving Deeper Shorts episode 28 "Natural Resource Restoration" audio with its published transcript.
22
  Format: MP3, 4,031,244 bytes, about 202 seconds (3.4 min, afinfo estimate); short replay of an earlier host interview; two voices
23
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
- Reference source: podcast/jan14/dds28-restoration.html, section "Transcript", from "Eighteen years ago, on January 6, 1996, NOAA issued its final rules for conducting Natural Resource Damage Assessments for oil spills." to "HOST: That's all for today's Diving Deeper Shorts, thanks for tuning in. ... Diving Deeper is back in two weeks."; about 504 words as extracted including the speaker labels; labels: HOST and TOM BROSNAN (the opening host turns have no label); the last line of the section is the page's series blurb, not speech, and is dropped from the reference; the opening host turns have no label
26
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
27
  Companions (not included): podcast/jan14/dds28-restoration.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/jan14/dds011614.mp3`: NOAA Diving Deeper Shorts episode 28 "Natural Resource Restoration" audio with its published transcript.
20
  Format: MP3, 4,031,244 bytes, about 202 seconds (3.4 min, afinfo estimate); short replay of an earlier host interview; two voices
21
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
 
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
23
  Companions (not included): podcast/jan14/dds28-restoration.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-dds29-lionfish/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `podcast/feb14/dds020614.mp3`: NOAA Diving Deeper Shorts episode 29 "Lionfish" audio with its published transcript.
22
  Format: MP3, 3,530,690 bytes, about 3.7 min, short replay of an April 2012 host interview; two voices
23
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
- Reference source: podcast/feb14/dds29-lionfish.html, section "Transcript", from "HOST: Lionfish are beautiful creatures, but are having a negative impact on coastal ecosystems." to the closing HOST turn "HOST: That's all for today's Diving Deeper Shorts, thanks for tuning in. ..."
26
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels
27
  Companions (not included): podcast/feb14/dds29-lionfish.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/feb14/dds020614.mp3`: NOAA Diving Deeper Shorts episode 29 "Lionfish" audio with its published transcript.
20
  Format: MP3, 3,530,690 bytes, about 3.7 min, short replay of an April 2012 host interview; two voices
21
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
 
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels
23
  Companions (not included): podcast/feb14/dds29-lionfish.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-mw122-exxonvaldez/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `podcast/mar14/mw032114.mp3`: NOAA Making Waves episode 122 "The Exxon Valdez, 25 Years Later" audio with its published transcript.
22
  Format: MP3, 14,458,915 bytes, about 904 seconds (15.1 min, afinfo estimate); narrated feature with one interviewee and a short archival ship radio clip; three sources of speech
23
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
- Reference source: podcast/mar14/mw122-exxonvaldez.html, section "Transcript", from "[SHIP RADIO] \"Yeah, this is Valdez. should be on your radar there." to "[NARRATOR] That was Gary Shigenaka, marine biologist with the Emergency Response Division of NOAA's Office of Response and Restoration. ... about 2,351 words as extracted including the speaker labels; labels: [SHIP RADIO], [NARRATOR] and [GARY SHIGENAKA] in square brackets; the last line of the section is the page's series blurb, not speech, and is dropped from the reference; the opening ship radio clip is archival 1989 radio audio, noisy and partly elided in the transcript ("..."); score it separately or cut it
26
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
27
  Companions (not included): podcast/mar14/mw122-exxonvaldez.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/mar14/mw032114.mp3`: NOAA Making Waves episode 122 "The Exxon Valdez, 25 Years Later" audio with its published transcript.
20
  Format: MP3, 14,458,915 bytes, about 904 seconds (15.1 min, afinfo estimate); narrated feature with one interviewee and a short archival ship radio clip; three sources of speech
21
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
 
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
23
  Companions (not included): podcast/mar14/mw122-exxonvaldez.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-mw126-garbagepatch/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `podcast/june14/mw062614.mp3`: NOAA Making Waves episode 126 "Great Pacific Garbage Patch" audio with its published transcript.
22
  Format: MP3, 8,609,491 bytes, about 538 seconds (9.0 min, afinfo estimate); host interview with one guest; two voices
23
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
- Reference source: podcast/june14/mw126-garbagepatch.html, section "Transcript", from "This is Making Waves from NOAA's National Ocean Service. I'm Troy Kitch. ... And thanks for listening to Making Waves from NOAA's National Ocean Service."; about 1,402 words as extracted including the speaker labels; labels: [Dianna Parker] in square brackets; host turns have no label; the last line of the section is the page's series blurb, not speech, and is dropped from the reference; host turns are unlabeled, so a diarisation check needs the [Dianna Parker] turns only
26
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
27
  Companions (not included): podcast/june14/mw126-garbagepatch.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/june14/mw062614.mp3`: NOAA Making Waves episode 126 "Great Pacific Garbage Patch" audio with its published transcript.
20
  Format: MP3, 8,609,491 bytes, about 538 seconds (9.0 min, afinfo estimate); host interview with one guest; two voices
21
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
 
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
23
  Companions (not included): podcast/june14/mw126-garbagepatch.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-mw137-wetlands-bluecarbon/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `podcast/aug16/mw080416.mp3`: NOAA Making Waves episode 137 "Wetlands and Blue Carbon" audio with its published transcript.
22
  Format: MP3, 18,878,779 bytes, about 19.7 min, host interview with two guests; three voices
23
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
- Reference source: ... Thanks for listening!"
26
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels
27
  Companions (not included): podcast/aug16/mw137-wetlands-bluecarbon.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/aug16/mw080416.mp3`: NOAA Making Waves episode 137 "Wetlands and Blue Carbon" audio with its published transcript.
20
  Format: MP3, 18,878,779 bytes, about 19.7 min, host interview with two guests; three voices
21
  Origin: NOAA staff interview recorded for broadcast, transcript published by NOAA
 
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; speaker turns may be scored separately as a diarisation check against the labels
23
  Companions (not included): podcast/aug16/mw137-wetlands-bluecarbon.html; disclaimer.html
campaign_files/2026-10-md-media-and-documents/noaa-nos-podcast-os6-bluecarbon/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: Orthographic transcript with speaker labels (published episode transcript). 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 mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `podcast/feb15/os021215.mp3`: NOAA Ocean Shorts episode 6 "Coastal Blue Carbon" audio with its published transcript.
22
  Format: MP3, 6,271,461 bytes, about 261 seconds (4.3 min, afinfo estimate); short narrated piece with one interviewee; two voices
23
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
24
- Reference result: orthographic transcript with speaker labels (published episode transcript)
25
- Reference source: podcast/feb15/os6-bluecarbon.html, section "Transcript", from "You’re listening to Ocean Shorts. I’m Troy Kitch." to "And this is Ocean Shorts from NOAA's National Ocean Service. Thanks for listening."; about 725 words as extracted including the speaker labels; labels: [Ariana Sutton-Grier] in square brackets; narrator turns have no label; the last line of the section is the page's series blurb, not speech, and is dropped from the reference; narrator turns are unlabeled
26
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
27
  Companions (not included): podcast/feb15/os6-bluecarbon.html; disclaimer.html
 
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: Give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `podcast/feb15/os021215.mp3`: NOAA Ocean Shorts episode 6 "Coastal Blue Carbon" audio with its published transcript.
20
  Format: MP3, 6,271,461 bytes, about 261 seconds (4.3 min, afinfo estimate); short narrated piece with one interviewee; two voices
21
  Origin: NOAA staff recording made for broadcast, transcript published by NOAA
 
 
22
  Check: give the agent the mp3 only; it writes the transcript; score word error rate (WER) against the reference words, reported as a number with no pass mark; reference = the published transcript with the speaker labels and the closing series blurb removed; the series intro and outro announcements and music are cut from the hypothesis; case and punctuation folded on both sides; NOS transcripts are lightly edited (fillers dropped), so the score is a soft reference score; speaker turns may be scored separately as a diarisation check against the labels
23
  Companions (not included): podcast/feb15/os6-bluecarbon.html; disclaimer.html
campaign_files/2026-10-ml-serving-configs-2/nab-realknowncause/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. 2 of 2 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_anomaly_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: The agent emits one anomaly score per row (or a list of detection timestamps). Score with the NAB standard profile: a detection inside a window counts as a true positive weighted by the scaled sigmoid of its position (earlier is better), only the first detection per window counts, a detection outside every window is a false positive with weight fpWeight 0.11, a missed window costs fnWeight 1.0; rows in the probationary period (the first 15 percent of the file, capped at 750 rows; here 750 rows) are not scored; normalise to the NAB score where the null detector is 0 and the perfect detector is 100. A simpler acceptance check that needs no threshold sweep: the reported detection timestamps hit every labelled window and fall outside the windows at most as often as the expected answer file allows.
14
 
15
  **Licence (SPDX):** MIT
@@ -21,16 +19,12 @@ Files:
21
  - `data/realKnownCause/machine_temperature_system_failure.csv`: NAB realKnownCause/machine_temperature_system_failure.csv: industrial machine temperature, 4 labelled anomaly windows (system failure); 22695 rows, 2013-12-02 21:15:00 to 2014-02-19 15:25:00, 5-minute steps.
22
  Format: CSV (timestamp,value) plus JSON label windows keyed by file name
23
  Origin: machine temperature sensor log published by Numenta in NAB (realKnownCause: anomaly causes known)
24
- Reference result: labelled_anomaly_windows
25
- Reference source: labels/combined_windows.json key "realKnownCause/machine_temperature_system_failure.csv": 4 anomaly window(s) [["2013-12-10 06:25:00.000000", "2013-12-12 05:35:00.000000"], ["2013-12-15 17:50:00.000000", "2013-12-17 17:00:00.000000"], ["2014-01-27 14:20:00.000000", "2014-01-29 13:30:00.000000"], ["2014-02-07 14:55:00.000000", "2014-02-09 14:05:00.000000"]]; labels/combined_labels.json gives the anomaly timestamps the windows are centred on; labels made by Numenta with its labeling process (README.md lines 75 and 86: labeled anomalous periods)
26
  Check: The agent emits one anomaly score per row (or a list of detection timestamps). Score with the NAB standard profile: a detection inside a window counts as a true positive weighted by the scaled sigmoid of its position (earlier is better), only the first detection per window counts, a detection outside every window is a false positive with weight fpWeight 0.11, a missed window costs fnWeight 1.0; rows in the probationary period (the first 15 percent of the file, capped at 750 rows; here 750 rows) are not scored; normalise to the NAB score where the null detector is 0 and the perfect detector is 100. A simpler acceptance check that needs no threshold sweep: the reported detection timestamps hit every labelled window and fall outside the windows at most as often as the expected answer file allows
27
  Companions (not included): labels/combined_windows.json; labels/combined_labels.json; config/profiles.json; LICENSE.txt
28
  Dependencies: none to read the data (CSV with columns timestamp,value; JSON labels); scoring follows the NAB scorer at the pinned commit (nab/sweeper.py, nab/scorer.py, MIT, Python), which the judge may reimplement from the cited lines.
29
  - `data/realKnownCause/nyc_taxi.csv`: NAB realKnownCause/nyc_taxi.csv: NYC taxi demand, 5 labelled anomaly windows (holidays, marathon, snow storm); 10320 rows, 2014-07-01 00:00:00 to 2015-01-31 23:30:00, 30-minute buckets.
30
  Format: CSV (timestamp,value) plus JSON label windows keyed by file name
31
  Origin: aggregate taxi passenger counts derived by Numenta from the public NYC TLC trip records, published in NAB
32
- Reference result: labelled_anomaly_windows
33
- Reference source: labels/combined_windows.json key "realKnownCause/nyc_taxi.csv": 5 anomaly window(s) [["2014-10-30 15:30:00.000000", "2014-11-03 22:30:00.000000"], ["2014-11-25 12:00:00.000000", "2014-11-29 19:00:00.000000"], ["2014-12-23 11:30:00.000000", "2014-12-27 18:30:00.000000"], ["2014-12-29 21:30:00.000000", "2015-01-03 04:30:00.000000"], ["2015-01-24 20:30:00.000000", "2015-01-29 03:30:00.000000"]]; labels/combined_labels.json gives the anomaly timestamps the windows are centred on; labels made by Numenta with its labeling process (README.md lines 75 and 86: labeled anomalous periods)
34
  Check: The agent emits one anomaly score per row (or a list of detection timestamps). Score with the NAB standard profile: a detection inside a window counts as a true positive weighted by the scaled sigmoid of its position (earlier is better), only the first detection per window counts, a detection outside every window is a false positive with weight fpWeight 0.11, a missed window costs fnWeight 1.0; rows in the probationary period (the first 15 percent of the file, capped at 750 rows; here 750 rows) are not scored; normalise to the NAB score where the null detector is 0 and the perfect detector is 100. A simpler acceptance check that needs no threshold sweep: the reported detection timestamps hit every labelled window and fall outside the windows at most as often as the expected answer file allows
35
  Companions (not included): labels/combined_windows.json; labels/combined_labels.json; config/profiles.json; LICENSE.txt
36
  Dependencies: none to read the data (CSV with columns timestamp,value; JSON labels); scoring follows the NAB scorer at the pinned commit (nab/sweeper.py, nab/scorer.py, MIT, Python), which the judge may reimplement from the cited lines.
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 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 agent emits one anomaly score per row (or a list of detection timestamps). Score with the NAB standard profile: a detection inside a window counts as a true positive weighted by the scaled sigmoid of its position (earlier is better), only the first detection per window counts, a detection outside every window is a false positive with weight fpWeight 0.11, a missed window costs fnWeight 1.0; rows in the probationary period (the first 15 percent of the file, capped at 750 rows; here 750 rows) are not scored; normalise to the NAB score where the null detector is 0 and the perfect detector is 100. A simpler acceptance check that needs no threshold sweep: the reported detection timestamps hit every labelled window and fall outside the windows at most as often as the expected answer file allows.
12
 
13
  **Licence (SPDX):** MIT
 
19
  - `data/realKnownCause/machine_temperature_system_failure.csv`: NAB realKnownCause/machine_temperature_system_failure.csv: industrial machine temperature, 4 labelled anomaly windows (system failure); 22695 rows, 2013-12-02 21:15:00 to 2014-02-19 15:25:00, 5-minute steps.
20
  Format: CSV (timestamp,value) plus JSON label windows keyed by file name
21
  Origin: machine temperature sensor log published by Numenta in NAB (realKnownCause: anomaly causes known)
 
 
22
  Check: The agent emits one anomaly score per row (or a list of detection timestamps). Score with the NAB standard profile: a detection inside a window counts as a true positive weighted by the scaled sigmoid of its position (earlier is better), only the first detection per window counts, a detection outside every window is a false positive with weight fpWeight 0.11, a missed window costs fnWeight 1.0; rows in the probationary period (the first 15 percent of the file, capped at 750 rows; here 750 rows) are not scored; normalise to the NAB score where the null detector is 0 and the perfect detector is 100. A simpler acceptance check that needs no threshold sweep: the reported detection timestamps hit every labelled window and fall outside the windows at most as often as the expected answer file allows
23
  Companions (not included): labels/combined_windows.json; labels/combined_labels.json; config/profiles.json; LICENSE.txt
24
  Dependencies: none to read the data (CSV with columns timestamp,value; JSON labels); scoring follows the NAB scorer at the pinned commit (nab/sweeper.py, nab/scorer.py, MIT, Python), which the judge may reimplement from the cited lines.
25
  - `data/realKnownCause/nyc_taxi.csv`: NAB realKnownCause/nyc_taxi.csv: NYC taxi demand, 5 labelled anomaly windows (holidays, marathon, snow storm); 10320 rows, 2014-07-01 00:00:00 to 2015-01-31 23:30:00, 30-minute buckets.
26
  Format: CSV (timestamp,value) plus JSON label windows keyed by file name
27
  Origin: aggregate taxi passenger counts derived by Numenta from the public NYC TLC trip records, published in NAB
 
 
28
  Check: The agent emits one anomaly score per row (or a list of detection timestamps). Score with the NAB standard profile: a detection inside a window counts as a true positive weighted by the scaled sigmoid of its position (earlier is better), only the first detection per window counts, a detection outside every window is a false positive with weight fpWeight 0.11, a missed window costs fnWeight 1.0; rows in the probationary period (the first 15 percent of the file, capped at 750 rows; here 750 rows) are not scored; normalise to the NAB score where the null detector is 0 and the perfect detector is 100. A simpler acceptance check that needs no threshold sweep: the reported detection timestamps hit every labelled window and fall outside the windows at most as often as the expected answer file allows
29
  Companions (not included): labels/combined_windows.json; labels/combined_labels.json; config/profiles.json; LICENSE.txt
30
  Dependencies: none to read the data (CSV with columns timestamp,value; JSON labels); scoring follows the NAB scorer at the pinned commit (nab/sweeper.py, nab/scorer.py, MIT, Python), which the judge may reimplement from the cited lines.
campaign_files/2026-10-ml-serving-configs-2/nab-realtraffic/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: labelled_anomaly_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: The agent emits one anomaly score per row (or a list of detection timestamps). Score with the NAB standard profile: a detection inside a window counts as a true positive weighted by the scaled sigmoid of its position (earlier is better), only the first detection per window counts, a detection outside every window is a false positive with weight fpWeight 0.11, a missed window costs fnWeight 1.0; rows in the probationary period (the first 15 percent of the file, capped at 750 rows; here 169 rows) are not scored; normalise to the NAB score where the null detector is 0 and the perfect detector is 100. A simpler acceptance check that needs no threshold sweep: the reported detection timestamps hit every labelled window and fall outside the windows at most as often as the expected answer file allows.
14
 
15
  **Licence (SPDX):** MIT
@@ -21,8 +19,6 @@ Files:
21
  - `data/realTraffic/speed_7578.csv`: NAB realTraffic/speed_7578.csv: road traffic speed sensor, 4 labelled anomaly windows; 1127 rows, 2015-09-08 11:39:00 to 2015-09-17 14:05:00, irregular steps of about 5 minutes.
22
  Format: CSV (timestamp,value) plus JSON label windows keyed by file name
23
  Origin: road speed sensor data of MnDOT published by Numenta in NAB
24
- Reference result: labelled_anomaly_windows
25
- Reference source: labels/combined_windows.json key "realTraffic/speed_7578.csv": 4 anomaly window(s) [["2015-09-11 15:34:00.000000", "2015-09-11 17:54:00.000000"], ["2015-09-15 13:26:00.000000", "2015-09-15 15:54:00.000000"], ["2015-09-16 13:04:00.000000", "2015-09-16 15:20:00.000000"], ["2015-09-16 16:00:00.000000", "2015-09-16 18:20:00.000000"]]; labels/combined_labels.json gives the anomaly timestamps the windows are centred on; labels made by Numenta with its labeling process (README.md lines 75 and 86: labeled anomalous periods)
26
  Check: The agent emits one anomaly score per row (or a list of detection timestamps). Score with the NAB standard profile: a detection inside a window counts as a true positive weighted by the scaled sigmoid of its position (earlier is better), only the first detection per window counts, a detection outside every window is a false positive with weight fpWeight 0.11, a missed window costs fnWeight 1.0; rows in the probationary period (the first 15 percent of the file, capped at 750 rows; here 169 rows) are not scored; normalise to the NAB score where the null detector is 0 and the perfect detector is 100. A simpler acceptance check that needs no threshold sweep: the reported detection timestamps hit every labelled window and fall outside the windows at most as often as the expected answer file allows
27
  Companions (not included): labels/combined_windows.json; labels/combined_labels.json; config/profiles.json; LICENSE.txt
28
  Dependencies: none to read the data (CSV with columns timestamp,value; JSON labels); scoring follows the NAB scorer at the pinned commit (nab/sweeper.py, nab/scorer.py, MIT, Python), which the judge may reimplement from the cited lines.
 
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 agent emits one anomaly score per row (or a list of detection timestamps). Score with the NAB standard profile: a detection inside a window counts as a true positive weighted by the scaled sigmoid of its position (earlier is better), only the first detection per window counts, a detection outside every window is a false positive with weight fpWeight 0.11, a missed window costs fnWeight 1.0; rows in the probationary period (the first 15 percent of the file, capped at 750 rows; here 169 rows) are not scored; normalise to the NAB score where the null detector is 0 and the perfect detector is 100. A simpler acceptance check that needs no threshold sweep: the reported detection timestamps hit every labelled window and fall outside the windows at most as often as the expected answer file allows.
12
 
13
  **Licence (SPDX):** MIT
 
19
  - `data/realTraffic/speed_7578.csv`: NAB realTraffic/speed_7578.csv: road traffic speed sensor, 4 labelled anomaly windows; 1127 rows, 2015-09-08 11:39:00 to 2015-09-17 14:05:00, irregular steps of about 5 minutes.
20
  Format: CSV (timestamp,value) plus JSON label windows keyed by file name
21
  Origin: road speed sensor data of MnDOT published by Numenta in NAB
 
 
22
  Check: The agent emits one anomaly score per row (or a list of detection timestamps). Score with the NAB standard profile: a detection inside a window counts as a true positive weighted by the scaled sigmoid of its position (earlier is better), only the first detection per window counts, a detection outside every window is a false positive with weight fpWeight 0.11, a missed window costs fnWeight 1.0; rows in the probationary period (the first 15 percent of the file, capped at 750 rows; here 169 rows) are not scored; normalise to the NAB score where the null detector is 0 and the perfect detector is 100. A simpler acceptance check that needs no threshold sweep: the reported detection timestamps hit every labelled window and fall outside the windows at most as often as the expected answer file allows
23
  Companions (not included): labels/combined_windows.json; labels/combined_labels.json; config/profiles.json; LICENSE.txt
24
  Dependencies: none to read the data (CSV with columns timestamp,value; JSON labels); scoring follows the NAB scorer at the pinned commit (nab/sweeper.py, nab/scorer.py, MIT, Python), which the judge may reimplement from the cited lines.
campaign_files/2026-10-ml-serving-configs-2/nannyml-synthetic-car-loan/README.md CHANGED
@@ -8,8 +8,6 @@
8
 
9
  **Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 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: realised_performance_per_chunk. 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 target file from the agent. The agent estimates per-chunk performance of the analysis period without targets (or flags the chunks where performance dropped) using the reference period. Chunk both periods into 10 equal chunks (the NannyML default chunker); the expected answer is the realised ROC AUC per analysis chunk computed from the target file, and a chunk counts as degraded when its realised value lies outside the reference mean plus or minus 3 standard deviations of the reference chunks (the NannyML default standard deviation threshold). Accept when the agent flags exactly the degraded chunks.
14
 
15
  **Licence (SPDX):** Apache-2.0
@@ -21,8 +19,6 @@ Units:
21
  - `nannyml/datasets/data/` (3 files): NannyML synthetic car loan monitoring set: a binary classifier's predictions over a 50000-row reference period with targets and a 50000-row analysis period whose targets are held in a separate file.
22
  Format: CSV (three files joined on id)
23
  Origin: synthetic dataset shipped inside the NannyML library to test and document its monitoring features (docs/datasets/binary_car_loan.rst line 7).
24
- Reference result: realised_performance_per_chunk
25
- Reference source: synthetic_car_loan_analysis_target.csv column repaid (the delayed ground truth of the 50000 analysis rows, joined on id) against y_pred and y_pred_proba of synthetic_car_loan_analysis.csv; the realised ROC AUC and accuracy per chunk, and which chunks fall outside the reference band, follow from these by computation
26
  Check: Hide the target file from the agent. The agent estimates per-chunk performance of the analysis period without targets (or flags the chunks where performance dropped) using the reference period. Chunk both periods into 10 equal chunks (the NannyML default chunker); the expected answer is the realised ROC AUC per analysis chunk computed from the target file, and a chunk counts as degraded when its realised value lies outside the reference mean plus or minus 3 standard deviations of the reference chunks (the NannyML default standard deviation threshold). Accept when the agent flags exactly the degraded chunks
27
  Companions (not included): LICENSE
28
  Dependencies: none to read the data (CSV); the reference answer is the realised performance per chunk computed from the target file; NannyML at the pinned commit (Apache-2.0, Python) is the reference implementation the judge may reimplement from the cited lines.
 
8
 
9
  **Self-contained:** Not self-contained: each unit is used together with other files from the same upstream. 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 the target file from the agent. The agent estimates per-chunk performance of the analysis period without targets (or flags the chunks where performance dropped) using the reference period. Chunk both periods into 10 equal chunks (the NannyML default chunker); the expected answer is the realised ROC AUC per analysis chunk computed from the target file, and a chunk counts as degraded when its realised value lies outside the reference mean plus or minus 3 standard deviations of the reference chunks (the NannyML default standard deviation threshold). Accept when the agent flags exactly the degraded chunks.
12
 
13
  **Licence (SPDX):** Apache-2.0
 
19
  - `nannyml/datasets/data/` (3 files): NannyML synthetic car loan monitoring set: a binary classifier's predictions over a 50000-row reference period with targets and a 50000-row analysis period whose targets are held in a separate file.
20
  Format: CSV (three files joined on id)
21
  Origin: synthetic dataset shipped inside the NannyML library to test and document its monitoring features (docs/datasets/binary_car_loan.rst line 7).
 
 
22
  Check: Hide the target file from the agent. The agent estimates per-chunk performance of the analysis period without targets (or flags the chunks where performance dropped) using the reference period. Chunk both periods into 10 equal chunks (the NannyML default chunker); the expected answer is the realised ROC AUC per analysis chunk computed from the target file, and a chunk counts as degraded when its realised value lies outside the reference mean plus or minus 3 standard deviations of the reference chunks (the NannyML default standard deviation threshold). Accept when the agent flags exactly the degraded chunks
23
  Companions (not included): LICENSE
24
  Dependencies: none to read the data (CSV); the reference answer is the realised performance per chunk computed from the target file; NannyML at the pinned commit (Apache-2.0, Python) is the reference implementation the judge may reimplement from the cited lines.
campaign_files/2026-10-ml-serving-configs-2/nnapi-cts-test-specs/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. 2 of 2 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_tensors. 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: Generate the C++ test models from the spec with test_generator.py, run each on the driver under test, and compare every output element with the Example value as TestHarness.cpp does: |actual - expected| must not exceed atol + rtol * |expected| (line 79), with the per type criteria below; output shape must match.
14
 
15
  **Licence (SPDX):** Apache-2.0
@@ -21,16 +19,12 @@ Files:
21
  - `runtime/test/specs/V1_2/instance_normalization.mod.py`: Android NNAPI test spec instance_normalization.mod.py (V1_2): INSTANCE_NORMALIZATION with gamma, beta, epsilon 0.0001, NHWC and NCHW, plus a large-value regression case; inline inputs and expected outputs.
22
  Format: Python test spec (.mod.py) in the NNAPI test generator DSL with Model, Input, Output and Example declarations and inline values
23
  Origin: conformance (CTS and VTS) fixture of the Android Neural Networks API written by the Android NNAPI team
24
- Reference result: expected_output_tensors
25
- Reference source: the output values written in each Example block of runtime/test/specs/V1_2/instance_normalization.mod.py (3 Example blocks; the generator expands each with NHWC and NCHW layouts and the variations relaxed and float16); values written by the Android NNAPI team from the operator definition
26
  Check: Generate the C++ test models from the spec with test_generator.py, run each on the driver under test, and compare every output element with the Example value as TestHarness.cpp does: |actual - expected| must not exceed atol + rtol * |expected| (line 79), with the per type criteria below; output shape must match
27
  Companions (not included): tools/test_generator/test_harness/TestHarness.cpp; tools/test_generator/test_generator.py; LICENSE
28
  Dependencies: the NNAPI test generator tools/test_generator/test_generator.py at commit 6a3e9d94 (turns the .mod.py spec into C++ test models). an NNAPI driver or the NNAPI CPU reference driver plus GoogleTest, built in an Android tree.
29
  - `runtime/test/specs/V1_2/roi_align.mod.py`: Android NNAPI test spec roi_align.mod.py (V1_2): ROI_ALIGN with several output sizes, spatial scales and sampling ratios, a zero-sized input case after BOX_WITH_NMS_LIMIT, and a large case; inline inputs, ROIs and expected outputs.
30
  Format: Python test spec (.mod.py) in the NNAPI test generator DSL with Model, Input, Output and Example declarations and inline values
31
  Origin: conformance (CTS and VTS) fixture of the Android Neural Networks API written by the Android NNAPI team
32
- Reference result: expected_output_tensors
33
- Reference source: the output values written in each Example block of runtime/test/specs/V1_2/roi_align.mod.py (6 Example blocks; the generator expands each with NHWC and NCHW layouts and the variations relaxed, quant8 and float16); values written by the Android NNAPI team from the operator definition
34
  Check: Generate the C++ test models from the spec with test_generator.py, run each on the driver under test, and compare every output element with the Example value as TestHarness.cpp does: |actual - expected| must not exceed atol + rtol * |expected| (line 79), with the per type criteria below; output shape must match
35
  Companions (not included): tools/test_generator/test_harness/TestHarness.cpp; tools/test_generator/test_generator.py; LICENSE
36
  Dependencies: the NNAPI test generator tools/test_generator/test_generator.py at commit 6a3e9d94 (turns the .mod.py spec into C++ test models). an NNAPI driver or the NNAPI CPU reference driver plus GoogleTest, built in an Android tree.
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 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: Generate the C++ test models from the spec with test_generator.py, run each on the driver under test, and compare every output element with the Example value as TestHarness.cpp does: |actual - expected| must not exceed atol + rtol * |expected| (line 79), with the per type criteria below; output shape must match.
12
 
13
  **Licence (SPDX):** Apache-2.0
 
19
  - `runtime/test/specs/V1_2/instance_normalization.mod.py`: Android NNAPI test spec instance_normalization.mod.py (V1_2): INSTANCE_NORMALIZATION with gamma, beta, epsilon 0.0001, NHWC and NCHW, plus a large-value regression case; inline inputs and expected outputs.
20
  Format: Python test spec (.mod.py) in the NNAPI test generator DSL with Model, Input, Output and Example declarations and inline values
21
  Origin: conformance (CTS and VTS) fixture of the Android Neural Networks API written by the Android NNAPI team
 
 
22
  Check: Generate the C++ test models from the spec with test_generator.py, run each on the driver under test, and compare every output element with the Example value as TestHarness.cpp does: |actual - expected| must not exceed atol + rtol * |expected| (line 79), with the per type criteria below; output shape must match
23
  Companions (not included): tools/test_generator/test_harness/TestHarness.cpp; tools/test_generator/test_generator.py; LICENSE
24
  Dependencies: the NNAPI test generator tools/test_generator/test_generator.py at commit 6a3e9d94 (turns the .mod.py spec into C++ test models). an NNAPI driver or the NNAPI CPU reference driver plus GoogleTest, built in an Android tree.
25
  - `runtime/test/specs/V1_2/roi_align.mod.py`: Android NNAPI test spec roi_align.mod.py (V1_2): ROI_ALIGN with several output sizes, spatial scales and sampling ratios, a zero-sized input case after BOX_WITH_NMS_LIMIT, and a large case; inline inputs, ROIs and expected outputs.
26
  Format: Python test spec (.mod.py) in the NNAPI test generator DSL with Model, Input, Output and Example declarations and inline values
27
  Origin: conformance (CTS and VTS) fixture of the Android Neural Networks API written by the Android NNAPI team
 
 
28
  Check: Generate the C++ test models from the spec with test_generator.py, run each on the driver under test, and compare every output element with the Example value as TestHarness.cpp does: |actual - expected| must not exceed atol + rtol * |expected| (line 79), with the per type criteria below; output shape must match
29
  Companions (not included): tools/test_generator/test_harness/TestHarness.cpp; tools/test_generator/test_generator.py; LICENSE
30
  Dependencies: the NNAPI test generator tools/test_generator/test_generator.py at commit 6a3e9d94 (turns the .mod.py spec into C++ test models). an NNAPI driver or the NNAPI CPU reference driver plus GoogleTest, built in an Android tree.
campaign_files/2026-10-s-security-detection-2/naxsi-waf-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. 4 of 4 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_http_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:** Check: Task: write the naxsi configuration that blocks the illegal Host headers, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 9 blocks; Task: decide which posts naxsi blocks, or write the configuration. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 4 blocks; Task: write the naxsi configuration that blocks the bypass vectors, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 14 blocks; Task: write the naxsi configuration and whitelist that block the malformed query strings except where whitelisted, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 8 blocks.
14
 
15
  **Licence (SPDX):** GPL-3.0-only
@@ -21,32 +19,24 @@ Files:
21
  - `unit-tests/tests/38illeagal_host.t`: Naxsi illegal Host header: 9 requests, 5 malformed Host values must be blocked with 412 and 4 legal ones (including punycode) must pass with 200.
22
  Format: Test::Nginx .t file (5,655 B) with 9 blocks (main_config, config, request, more_headers, error_code); core rules in naxsi_rules/naxsi_core.rules
23
  Origin: test cases written by hand by the maintainers to pin the expected verdict of their own rules (constructed, not recorded traffic)
24
- Reference result: expected_http_code
25
- Reference source: 38illeagal_host.t: error_code 412 at lines 37, 64, 91, 118, 145 (Host 0.0.0.0, 0.1.0.6, 255.255.255.255, --dddd, [ipaddr]); error_code 200 at lines 172, 197, 222, 248
26
  Check: Task: write the naxsi configuration that blocks the illegal Host headers, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 9 blocks
27
  Companions (not included): naxsi_rules/naxsi_core.rules; LICENSE
28
  Dependencies: nginx built with naxsi at this commit and Test::Nginx (Perl) with TEST_NGINX_NAXSI_RULES pointing at naxsi_core.rules: needed only to rerun the tests; versions pinned when the pool is built; not packed
29
  - `unit-tests/tests/32utf8.t`: Naxsi UTF-8 validation: overlong UTF-8 sequences in a POST body must be blocked with 412, valid UTF-8 must pass with 200.
30
  Format: Test::Nginx .t file (3,039 B) with 4 blocks; core rules in naxsi_rules/naxsi_core.rules
31
  Origin: test cases written by hand by the maintainers to pin the expected verdict of their own rules (constructed, not recorded traffic)
32
- Reference result: expected_http_code
33
- Reference source: 32utf8.t: error_code 412 at lines 42 and 72 (tests 2.0 and 2.1, overlong); error_code 200 at lines 102 and 135 (tests 2.2 and 2.3, valid UTF-8)
34
  Check: Task: decide which posts naxsi blocks, or write the configuration. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 4 blocks
35
  Companions (not included): naxsi_rules/naxsi_core.rules; LICENSE
36
  Dependencies: nginx built with naxsi at this commit and Test::Nginx (Perl) with TEST_NGINX_NAXSI_RULES pointing at naxsi_core.rules: needed only to rerun the tests; versions pinned when the pool is built; not packed
37
  - `unit-tests/tests/02naxsi_bypass.t`: Naxsi XSS and parser bypass vectors: 14 requests, 12 encoded or malformed bypass attempts must be blocked with 412, 1 must be rejected with 400 and 1 plain request must pass with 200.
38
  Format: Test::Nginx .t file (7,648 B) with 14 blocks (main_config, config with CheckRule thresholds, request, error_code); one request carries a literal NUL byte (line 340, the true-nullbyte vector); core rules in naxsi_rules/naxsi_core.rules
39
  Origin: test cases written by hand by the maintainers to pin the expected verdict of their own rules (constructed, not recorded traffic)
40
- Reference result: expected_http_code
41
- Reference source: 02naxsi_bypass.t: error_code 412 at lines 59, 82, 106, 153, 176, 199, 222, 245, 268, 291, 314, 341 (tests 2, 2.1, 2.2, 3.0, 3.1, 4.0, 4.01, 4.1, 4.2, 4.21, 4.3, 5.1); error_code 400 at line 130 (test 2.3, NUL byte in the URL path, refused by nginx itself); error_code 200 at line 36 (test 1, basic GET)
42
  Check: Task: write the naxsi configuration that blocks the bypass vectors, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 14 blocks
43
  Companions (not included): naxsi_rules/naxsi_core.rules; LICENSE
44
  Dependencies: nginx built with naxsi at this commit and Test::Nginx (Perl) with TEST_NGINX_NAXSI_RULES pointing at naxsi_core.rules: needed only to rerun the tests; versions pinned when the pool is built; not packed
45
  - `unit-tests/tests/06naxsi_weirds.t`: Naxsi malformed query strings and whitelist scope: 8 requests, 6 must be blocked with 412 (including whitelists on the wrong URL or zone) and 2 whitelisted ones must pass with 200.
46
  Format: Test::Nginx .t file (4,565 B) with 8 blocks (main_config, config with CheckRule thresholds and BasicRule wl:12 whitelists, request, error_code); core rules in naxsi_rules/naxsi_core.rules
47
  Origin: test cases written by hand by the maintainers to pin the expected verdict of their own rules (constructed, not recorded traffic)
48
- Reference result: expected_http_code
49
- Reference source: 06naxsi_weirds.t: error_code 412 at lines 33, 56, 79, 102, 174, 198 (tests 1.0, 1.0a, 1.0b, 1.0c, 1.03 wrong-URL whitelist, 1.04 wrong-zone whitelist); error_code 200 at lines 126, 150 (tests 1.01 and 1.02, whitelist wl:12 on ARGS and on $URL:/|ARGS)
50
  Check: Task: write the naxsi configuration and whitelist that block the malformed query strings except where whitelisted, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 8 blocks
51
  Companions (not included): naxsi_rules/naxsi_core.rules; LICENSE
52
  Dependencies: nginx built with naxsi at this commit and Test::Nginx (Perl) with TEST_NGINX_NAXSI_RULES pointing at naxsi_core.rules: needed only to rerun the tests; versions pinned when the pool is built; not packed
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 4 of 4 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: Task: write the naxsi configuration that blocks the illegal Host headers, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 9 blocks; Task: decide which posts naxsi blocks, or write the configuration. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 4 blocks; Task: write the naxsi configuration that blocks the bypass vectors, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 14 blocks; Task: write the naxsi configuration and whitelist that block the malformed query strings except where whitelisted, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 8 blocks.
12
 
13
  **Licence (SPDX):** GPL-3.0-only
 
19
  - `unit-tests/tests/38illeagal_host.t`: Naxsi illegal Host header: 9 requests, 5 malformed Host values must be blocked with 412 and 4 legal ones (including punycode) must pass with 200.
20
  Format: Test::Nginx .t file (5,655 B) with 9 blocks (main_config, config, request, more_headers, error_code); core rules in naxsi_rules/naxsi_core.rules
21
  Origin: test cases written by hand by the maintainers to pin the expected verdict of their own rules (constructed, not recorded traffic)
 
 
22
  Check: Task: write the naxsi configuration that blocks the illegal Host headers, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 9 blocks
23
  Companions (not included): naxsi_rules/naxsi_core.rules; LICENSE
24
  Dependencies: nginx built with naxsi at this commit and Test::Nginx (Perl) with TEST_NGINX_NAXSI_RULES pointing at naxsi_core.rules: needed only to rerun the tests; versions pinned when the pool is built; not packed
25
  - `unit-tests/tests/32utf8.t`: Naxsi UTF-8 validation: overlong UTF-8 sequences in a POST body must be blocked with 412, valid UTF-8 must pass with 200.
26
  Format: Test::Nginx .t file (3,039 B) with 4 blocks; core rules in naxsi_rules/naxsi_core.rules
27
  Origin: test cases written by hand by the maintainers to pin the expected verdict of their own rules (constructed, not recorded traffic)
 
 
28
  Check: Task: decide which posts naxsi blocks, or write the configuration. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 4 blocks
29
  Companions (not included): naxsi_rules/naxsi_core.rules; LICENSE
30
  Dependencies: nginx built with naxsi at this commit and Test::Nginx (Perl) with TEST_NGINX_NAXSI_RULES pointing at naxsi_core.rules: needed only to rerun the tests; versions pinned when the pool is built; not packed
31
  - `unit-tests/tests/02naxsi_bypass.t`: Naxsi XSS and parser bypass vectors: 14 requests, 12 encoded or malformed bypass attempts must be blocked with 412, 1 must be rejected with 400 and 1 plain request must pass with 200.
32
  Format: Test::Nginx .t file (7,648 B) with 14 blocks (main_config, config with CheckRule thresholds, request, error_code); one request carries a literal NUL byte (line 340, the true-nullbyte vector); core rules in naxsi_rules/naxsi_core.rules
33
  Origin: test cases written by hand by the maintainers to pin the expected verdict of their own rules (constructed, not recorded traffic)
 
 
34
  Check: Task: write the naxsi configuration that blocks the bypass vectors, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 14 blocks
35
  Companions (not included): naxsi_rules/naxsi_core.rules; LICENSE
36
  Dependencies: nginx built with naxsi at this commit and Test::Nginx (Perl) with TEST_NGINX_NAXSI_RULES pointing at naxsi_core.rules: needed only to rerun the tests; versions pinned when the pool is built; not packed
37
  - `unit-tests/tests/06naxsi_weirds.t`: Naxsi malformed query strings and whitelist scope: 8 requests, 6 must be blocked with 412 (including whitelists on the wrong URL or zone) and 2 whitelisted ones must pass with 200.
38
  Format: Test::Nginx .t file (4,565 B) with 8 blocks (main_config, config with CheckRule thresholds and BasicRule wl:12 whitelists, request, error_code); core rules in naxsi_rules/naxsi_core.rules
39
  Origin: test cases written by hand by the maintainers to pin the expected verdict of their own rules (constructed, not recorded traffic)
 
 
40
  Check: Task: write the naxsi configuration and whitelist that block the malformed query strings except where whitelisted, or classify each request. Score: run with Test::Nginx against nginx plus naxsi; each block passes when the response code equals error_code; exact match, all 8 blocks
41
  Companions (not included): naxsi_rules/naxsi_core.rules; LICENSE
42
  Dependencies: nginx built with naxsi at this commit and Test::Nginx (Perl) with TEST_NGINX_NAXSI_RULES pointing at naxsi_core.rules: needed only to rerun the tests; versions pinned when the pool is built; not packed
campaign_files/2026-10-s-security-detection-2/nobrackets-ctf-2024-challenge-repository/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. 2 of 2 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: flag_string. 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: Exact string match of the flag against challenge.yml line 31. Exact string match of the flag against challenge.yml line 27.
14
 
15
  **Licence (SPDX):** NOASSERTION
@@ -21,16 +19,12 @@ Files:
21
  - `qualifications/Forensics/implant_1/dist/Amcache.zip`: NoBrackets CTF 2024 quals forensics/implant 1: identify the malicious program and its SHA1 from an Amcache CSV export.
22
  Format: zip (one member Amcache.csv, 27,475 B, an Amcache parser CSV)
23
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
24
- Reference result: flag_string
25
- Reference source: challenge.yml line 31 (NBCTF{IMPORTANT_nouvel_exploit_drone_a_tester.exe-89542eac72f11afb0711535d0404c79aad9c3728}); WU/WU.md filters the Amcache rows
26
  Check: Exact string match of the flag against challenge.yml line 31.
27
  Companions (not included): challenge.yml; WU/WU.md
28
  Dependencies: challenge.yml, WU/WU.md hold the flag, answers or official solution (hidden from the solver); solver tools are free choices (for example an EVTX, SQLite, pcap or zip tool), version fixed when the pool is built
29
  - `qualifications/Forensics/implant_2/dist/logs.zip`: NoBrackets CTF 2024 quals forensics/implant 2: find when the implant was launched and its parent process from an EvtxECmd CSV of Windows logs.
30
  Format: zip (1,362,612 B; one member logs.csv, 31,425,084 B uncompressed, EvtxECmd CSV output)
31
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
32
- Reference result: flag_string
33
- Reference source: challenge.yml line 27 (NBCTF{2024-09-08 15:20:39-cmd.exe}); WU/WU.md line 57 shows the Sysmon process creation record
34
  Check: Exact string match of the flag against challenge.yml line 27.
35
  Companions (not included): challenge.yml; WU/WU.md
36
  Dependencies: challenge.yml, WU/WU.md hold the flag, answers or official solution (hidden from the solver); solver tools are free choices (for example an EVTX, SQLite, pcap or zip tool), version fixed when the pool is built
 
8
 
9
  **Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 2 of 2 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: Exact string match of the flag against challenge.yml line 31. Exact string match of the flag against challenge.yml line 27.
12
 
13
  **Licence (SPDX):** NOASSERTION
 
19
  - `qualifications/Forensics/implant_1/dist/Amcache.zip`: NoBrackets CTF 2024 quals forensics/implant 1: identify the malicious program and its SHA1 from an Amcache CSV export.
20
  Format: zip (one member Amcache.csv, 27,475 B, an Amcache parser CSV)
21
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
 
 
22
  Check: Exact string match of the flag against challenge.yml line 31.
23
  Companions (not included): challenge.yml; WU/WU.md
24
  Dependencies: challenge.yml, WU/WU.md hold the flag, answers or official solution (hidden from the solver); solver tools are free choices (for example an EVTX, SQLite, pcap or zip tool), version fixed when the pool is built
25
  - `qualifications/Forensics/implant_2/dist/logs.zip`: NoBrackets CTF 2024 quals forensics/implant 2: find when the implant was launched and its parent process from an EvtxECmd CSV of Windows logs.
26
  Format: zip (1,362,612 B; one member logs.csv, 31,425,084 B uncompressed, EvtxECmd CSV output)
27
  Origin: official competition instance built by the organisers for a public CTF and released with its flag and solution (fixture of a competition, not recorded production telemetry)
 
 
28
  Check: Exact string match of the flag against challenge.yml line 27.
29
  Companions (not included): challenge.yml; WU/WU.md
30
  Dependencies: challenge.yml, WU/WU.md hold the flag, answers or official solution (hidden from the solver); solver tools are free choices (for example an EVTX, SQLite, pcap or zip tool), version fixed when the pool is built
campaign_files/2026-10-s-security-detection/naxsi-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.
10
 
11
- **Answers:** No answer files are included. Reference result: expected_http_status. 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: Run with Test::Nginx against nginx with the naxsi module (or the agent rule set); status must equal error_code.
14
 
15
  **Licence (SPDX):** GPL-3.0-only
@@ -21,7 +19,5 @@ Files:
21
  - `unit-tests/tests/20sqlmap.t`: NAXSI WAF test file 20sqlmap.t: 38 sqlmap tamper payloads with nginx config and expected HTTP status.
22
  Format: Test::Nginx blocks (config, request, expected error_code) + core rules
23
  Origin: test cases written by hand for the detection project's test suite (was constructed)
24
- Reference result: expected_http_status
25
- Reference source: --- error_code per === TEST block (412 means blocked)
26
  Check: Run with Test::Nginx against nginx with the naxsi module (or the agent rule set); status must equal error_code.
27
  Companions (not included): naxsi_rules/naxsi_core.rules
 
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: Run with Test::Nginx against nginx with the naxsi module (or the agent rule set); status must equal error_code.
12
 
13
  **Licence (SPDX):** GPL-3.0-only
 
19
  - `unit-tests/tests/20sqlmap.t`: NAXSI WAF test file 20sqlmap.t: 38 sqlmap tamper payloads with nginx config and expected HTTP status.
20
  Format: Test::Nginx blocks (config, request, expected error_code) + core rules
21
  Origin: test cases written by hand for the detection project's test suite (was constructed)
 
 
22
  Check: Run with Test::Nginx against nginx with the naxsi module (or the agent rule set); status must equal error_code.
23
  Companions (not included): naxsi_rules/naxsi_core.rules
campaign_files/2026-10-sc-science-reference-data-2/nasa-power-daily-to-monthly-wichita/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_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: Hide the monthly file; the agent maps day of year to month, averages T2M and PRECTOTCORR (mm/day) per month and over the year, and takes the max of T2M_MAX and the min of T2M_MIN. Means are scored within 0.01 (derived from 2 decimal inputs and outputs), extremes exactly. Checked this round: 13 of 13 values per parameter (max |diff| 0.005 for means, 0 for extremes).
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `sc094-14/power_daily_2020.csv`: NASA POWER point series at 37.69 N, 97.33 W (Wichita, Kansas), 2020: recompute the monthly and annual values of T2M, T2M_MAX, T2M_MIN and PRECTOTCORR from the daily values.
22
  Format: CSV with a -BEGIN HEADER- / -END HEADER- block naming each parameter and unit, then YEAR, DOY and one column per parameter (2 decimals)
23
  Origin: agency API output; values derive from the MERRA-2 reanalysis (assimilated observations), as the file header states
24
- Reference result: published_aggregate_in_companion_file
25
- Reference source: power_monthly_2020.csv lines 14 to 17 (one row per parameter, JAN to DEC and ANN), e.g. line 15 T2M 2020 JAN 1.45, ANN 14.06
26
  Check: hide the monthly file; the agent maps day of year to month, averages T2M and PRECTOTCORR (mm/day) per month and over the year, and takes the max of T2M_MAX and the min of T2M_MIN. Means are scored within 0.01 (derived from 2 decimal inputs and outputs), extremes exactly. Checked this round: 13 of 13 values per parameter (max |diff| 0.005 for means, 0 for extremes)
27
  Companions (not included): power_monthly_2020.csv (answer file)
 
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: Hide the monthly file; the agent maps day of year to month, averages T2M and PRECTOTCORR (mm/day) per month and over the year, and takes the max of T2M_MAX and the min of T2M_MIN. Means are scored within 0.01 (derived from 2 decimal inputs and outputs), extremes exactly. Checked this round: 13 of 13 values per parameter (max |diff| 0.005 for means, 0 for extremes).
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `sc094-14/power_daily_2020.csv`: NASA POWER point series at 37.69 N, 97.33 W (Wichita, Kansas), 2020: recompute the monthly and annual values of T2M, T2M_MAX, T2M_MIN and PRECTOTCORR from the daily values.
20
  Format: CSV with a -BEGIN HEADER- / -END HEADER- block naming each parameter and unit, then YEAR, DOY and one column per parameter (2 decimals)
21
  Origin: agency API output; values derive from the MERRA-2 reanalysis (assimilated observations), as the file header states
 
 
22
  Check: hide the monthly file; the agent maps day of year to month, averages T2M and PRECTOTCORR (mm/day) per month and over the year, and takes the max of T2M_MAX and the min of T2M_MIN. Means are scored within 0.01 (derived from 2 decimal inputs and outputs), extremes exactly. Checked this round: 13 of 13 values per parameter (max |diff| 0.005 for means, 0 for extremes)
23
  Companions (not included): power_monthly_2020.csv (answer file)
campaign_files/2026-10-sc-science-reference-data-2/ncei-lcd-72530094846-2020/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: published_aggregate_rows_in_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: Drop the 12 SOM rows; the agent recomputes the five monthly fields from the SOD rows (DailyMaximumDryBulbTemperature, DailyMinimumDryBulbTemperature, DailyPrecipitation with T counted as 0). Temperatures printed with one decimal are scored within 0.05 F, precipitation within 0.005 in, day counts exactly. Not used: MonthlyGreatestPrecip and MonthlyDaysWithLT32Temp do not recompute. Checked this round: 12/12 months match for all five fields.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,6 +19,4 @@ Files:
21
  - `sc094-03/72530094846.csv`: Chicago O'Hare LCD 2020: recompute the monthly summary (SOM) values from the daily summary (SOD) rows: mean max, mean min and mean temperature, total precipitation, days with max >= 90 F.
22
  Format: CSV, 12,721 rows of hourly (FM-15, FM-12), daily (SOD) and monthly (SOM) reports in one file; temperatures in F, precipitation in inches with T for trace
23
  Origin: agency climatological data file as published
24
- Reference result: published_aggregate_rows_in_file
25
- Reference source: the SOM (REPORT_TYPE SOM) rows of the same file: MonthlyMaximumTemperature, MonthlyMinimumTemperature, MonthlyMeanTemperature, MonthlyTotalLiquidPrecipitation, MonthlyDaysWithGT90Temp
26
  Check: drop the 12 SOM rows; the agent recomputes the five monthly fields from the SOD rows (DailyMaximumDryBulbTemperature, DailyMinimumDryBulbTemperature, DailyPrecipitation with T counted as 0). Temperatures printed with one decimal are scored within 0.05 F, precipitation within 0.005 in, day counts exactly. Not used: MonthlyGreatestPrecip and MonthlyDaysWithLT32Temp do not recompute. Checked this round: 12/12 months match for all five fields
 
8
 
9
  **Self-contained:** The file is self-contained.
10
 
 
 
11
  **Tools to open and check:** Check: Drop the 12 SOM rows; the agent recomputes the five monthly fields from the SOD rows (DailyMaximumDryBulbTemperature, DailyMinimumDryBulbTemperature, DailyPrecipitation with T counted as 0). Temperatures printed with one decimal are scored within 0.05 F, precipitation within 0.005 in, day counts exactly. Not used: MonthlyGreatestPrecip and MonthlyDaysWithLT32Temp do not recompute. Checked this round: 12/12 months match for all five fields.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `sc094-03/72530094846.csv`: Chicago O'Hare LCD 2020: recompute the monthly summary (SOM) values from the daily summary (SOD) rows: mean max, mean min and mean temperature, total precipitation, days with max >= 90 F.
20
  Format: CSV, 12,721 rows of hourly (FM-15, FM-12), daily (SOD) and monthly (SOM) reports in one file; temperatures in F, precipitation in inches with T for trace
21
  Origin: agency climatological data file as published
 
 
22
  Check: drop the 12 SOM rows; the agent recomputes the five monthly fields from the SOD rows (DailyMaximumDryBulbTemperature, DailyMinimumDryBulbTemperature, DailyPrecipitation with T counted as 0). Temperatures printed with one decimal are scored within 0.05 F, precipitation within 0.005 in, day counts exactly. Not used: MonthlyGreatestPrecip and MonthlyDaysWithLT32Temp do not recompute. Checked this round: 12/12 months match for all five fields
campaign_files/2026-10-sc-science-reference-data-2/ncei-ocean-heat-content-basin/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.
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 unit in the notes.
12
-
13
  **Tools to open and check:** Check: The agent averages the four 3-month values of each year for WO, NH and SH and returns the yearly heat content. Pass when |answer - published| <= 0.001 for all 213 values (71 years x 3 columns). Standard error columns are not judged. Checked this round: 213 of 213 within 0.001 (largest difference 0.00075; 184 of 213 within 0.0005 alone).
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Units:
21
  - `data/oceans/woa/DATA_ANALYSIS/3M_HEAT_CONTENT/DATA/basin/3month/` (4 files): NCEI World Ocean heat content 0 to 700 m, 3-month series: compute the yearly heat content (world, northern and southern parts).
22
  Format: four whitespace text files, one per 3-month period: YEAR, WO, WOse, NH, NHse, SH, SHse (10^22 J)
23
  Origin: objective analysis of in situ ocean temperature profiles (World Ocean Database), Levitus et al.
24
- Reference result: published_aggregate_in_companion_file
25
- Reference source: yearly/h22-w0-700m.dat, columns WO, NH and SH for 1955 to 2025
26
  Check: The agent averages the four 3-month values of each year for WO, NH and SH and returns the yearly heat content. Pass when |answer - published| <= 0.001 for all 213 values (71 years x 3 columns). Standard error columns are not judged. Checked this round: 213 of 213 within 0.001 (largest difference 0.00075; 184 of 213 within 0.0005 alone).
27
  Companions (not included): data/oceans/woa/DATA_ANALYSIS/3M_HEAT_CONTENT/DATA/basin/yearly/h22-w0-700m.dat (answer: published yearly series; hidden from the agent); access/global-ocean-heat-content/basin_heat_data.html (format and units page; given to the agent)
 
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.
10
 
 
 
11
  **Tools to open and check:** Check: The agent averages the four 3-month values of each year for WO, NH and SH and returns the yearly heat content. Pass when |answer - published| <= 0.001 for all 213 values (71 years x 3 columns). Standard error columns are not judged. Checked this round: 213 of 213 within 0.001 (largest difference 0.00075; 184 of 213 within 0.0005 alone).
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `data/oceans/woa/DATA_ANALYSIS/3M_HEAT_CONTENT/DATA/basin/3month/` (4 files): NCEI World Ocean heat content 0 to 700 m, 3-month series: compute the yearly heat content (world, northern and southern parts).
20
  Format: four whitespace text files, one per 3-month period: YEAR, WO, WOse, NH, NHse, SH, SHse (10^22 J)
21
  Origin: objective analysis of in situ ocean temperature profiles (World Ocean Database), Levitus et al.
 
 
22
  Check: The agent averages the four 3-month values of each year for WO, NH and SH and returns the yearly heat content. Pass when |answer - published| <= 0.001 for all 213 values (71 years x 3 columns). Standard error columns are not judged. Checked this round: 213 of 213 within 0.001 (largest difference 0.00075; 184 of 213 within 0.0005 alone).
23
  Companions (not included): data/oceans/woa/DATA_ANALYSIS/3M_HEAT_CONTENT/DATA/basin/yearly/h22-w0-700m.dat (answer: published yearly series; hidden from the agent); access/global-ocean-heat-content/basin_heat_data.html (format and units page; given to the agent)
campaign_files/2026-10-sc-science-reference-data-2/noaa-cpc-arctic-oscillation-monthly/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_reformatted_table_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 pivots the long monthly list into one row per year with 12 month columns at 3 decimals (partial last year left short). Pass when the year set and layout match and every cell satisfies |answer - published| <= 0.0005. Checked this round: 921 of 921 cells within 0.0005; 37 cells are rounding ties of the 4-decimal input where the table follows the unprinted digits, so either neighbour must be accepted.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `products/precip/CWlink/daily_ao_index/monthly.ao.index.b50.current.ascii`: CPC monthly Arctic Oscillation index (long list, 4 decimals): reshape into the year by month table at 3 decimals.
22
  Format: whitespace text: year, month, value (4 decimals), one row per month since 1950
23
  Origin: leading EOF of 1000 hPa height anomalies poleward of 20N projected on monthly analyses (CPC)
24
- Reference result: published_reformatted_table_in_companion_file
25
- Reference source: monthly.ao.index.b50.current.ascii.table: header row Jan to Dec, one row per year, 921 values
26
  Check: The agent pivots the long monthly list into one row per year with 12 month columns at 3 decimals (partial last year left short). Pass when the year set and layout match and every cell satisfies |answer - published| <= 0.0005. Checked this round: 921 of 921 cells within 0.0005; 37 cells are rounding ties of the 4-decimal input where the table follows the unprinted digits, so either neighbour must be accepted.
27
  Companions (not included): products/precip/CWlink/daily_ao_index/monthly.ao.index.b50.current.ascii.table (answer: published year by month table; hidden from the agent); products/precip/CWlink/daily_ao_index/ao.shtml (index page; 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 pivots the long monthly list into one row per year with 12 month columns at 3 decimals (partial last year left short). Pass when the year set and layout match and every cell satisfies |answer - published| <= 0.0005. Checked this round: 921 of 921 cells within 0.0005; 37 cells are rounding ties of the 4-decimal input where the table follows the unprinted digits, so either neighbour must be accepted.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `products/precip/CWlink/daily_ao_index/monthly.ao.index.b50.current.ascii`: CPC monthly Arctic Oscillation index (long list, 4 decimals): reshape into the year by month table at 3 decimals.
20
  Format: whitespace text: year, month, value (4 decimals), one row per month since 1950
21
  Origin: leading EOF of 1000 hPa height anomalies poleward of 20N projected on monthly analyses (CPC)
 
 
22
  Check: The agent pivots the long monthly list into one row per year with 12 month columns at 3 decimals (partial last year left short). Pass when the year set and layout match and every cell satisfies |answer - published| <= 0.0005. Checked this round: 921 of 921 cells within 0.0005; 37 cells are rounding ties of the 4-decimal input where the table follows the unprinted digits, so either neighbour must be accepted.
23
  Companions (not included): products/precip/CWlink/daily_ao_index/monthly.ao.index.b50.current.ascii.table (answer: published year by month table; hidden from the agent); products/precip/CWlink/daily_ao_index/ao.shtml (index page; given to the agent)
campaign_files/2026-10-sc-science-reference-data-2/noaa-glerl-great-lakes-hydro-data/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 sums the daily over-lake precipitation of each calendar month. Absolute tolerance 0.0005 mm. Checked this round: 1020 of 1020 months match (max error 6e-14). The basin and land files are not used: they are not plain sums or area-weighted means of the daily lake file.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `pubs/tech_reports/glerl-083/UpdatedFiles/daily/subdata_sup_lake.csv`: Lake Superior over-lake precipitation, 1940 to 2024: sum daily values into the published monthly totals.
22
  Format: CSV, one row per day with the over-lake precipitation (mm)
23
  Origin: hydrometeorological database for the Great Lakes (GLERL TM-083 update)
24
- Reference result: published_aggregate_in_companion_file
25
- Reference source: prc_sup_lake.csv, monthly over-lake precipitation (mm, 3 decimals), 1020 months
26
  Check: The agent sums the daily over-lake precipitation of each calendar month. Absolute tolerance 0.0005 mm. Checked this round: 1020 of 1020 months match (max error 6e-14). The basin and land files are not used: they are not plain sums or area-weighted means of the daily lake file.
27
  Companions (not included): pubs/tech_reports/glerl-083/UpdatedFiles/ReadMe.txt (file description; given to the agent); pubs/tech_reports/glerl-083/UpdatedFiles/prc_sup_lake.csv (answer: monthly totals in mm; hidden)
 
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 sums the daily over-lake precipitation of each calendar month. Absolute tolerance 0.0005 mm. Checked this round: 1020 of 1020 months match (max error 6e-14). The basin and land files are not used: they are not plain sums or area-weighted means of the daily lake file.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `pubs/tech_reports/glerl-083/UpdatedFiles/daily/subdata_sup_lake.csv`: Lake Superior over-lake precipitation, 1940 to 2024: sum daily values into the published monthly totals.
20
  Format: CSV, one row per day with the over-lake precipitation (mm)
21
  Origin: hydrometeorological database for the Great Lakes (GLERL TM-083 update)
 
 
22
  Check: The agent sums the daily over-lake precipitation of each calendar month. Absolute tolerance 0.0005 mm. Checked this round: 1020 of 1020 months match (max error 6e-14). The basin and land files are not used: they are not plain sums or area-weighted means of the daily lake file.
23
  Companions (not included): pubs/tech_reports/glerl-083/UpdatedFiles/ReadMe.txt (file description; given to the agent); pubs/tech_reports/glerl-083/UpdatedFiles/prc_sup_lake.csv (answer: monthly totals in mm; hidden)
campaign_files/2026-10-sc-science-reference-data-2/noaa-glerl-great-lakes-ice-cover/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: Per ice year the agent takes the largest daily value in bas.txt and the day it occurs. Checked this round: 54 of 54 winters match AMIC.txt bas within 0.05 and the date in dates_AMIC.txt.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `data/ice/glicd/daily/bas.txt`: Great Lakes daily basin-wide ice cover, winters 1973 to 2026: find each winter's annual maximum ice cover and its date.
22
  Format: whitespace table, one column per ice year (1973 to 2026), one row per day (Nov-10 onward), percent with 1 decimal, NA for no record
23
  Origin: ice charts from the US and Canadian ice services gridded by GLERL
24
- Reference result: published_aggregate_in_companion_file
25
- Reference source: AMIC.txt column bas (line 1 header "year sup mic hur eri ont bas") and dates_AMIC.txt column All_Lakes cover and date
26
  Check: Per ice year the agent takes the largest daily value in bas.txt and the day it occurs. Checked this round: 54 of 54 winters match AMIC.txt bas within 0.05 and the date in dates_AMIC.txt
27
  Companions (not included): data/ice/glicd/daily/README.txt (layout; given to the agent); data/ice/glicd/AMIC.txt (answer: annual maximum ice cover; hidden); data/ice/glicd/dates_AMIC.txt (answer: dates of the maxima; hidden)
 
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: Per ice year the agent takes the largest daily value in bas.txt and the day it occurs. Checked this round: 54 of 54 winters match AMIC.txt bas within 0.05 and the date in dates_AMIC.txt.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `data/ice/glicd/daily/bas.txt`: Great Lakes daily basin-wide ice cover, winters 1973 to 2026: find each winter's annual maximum ice cover and its date.
20
  Format: whitespace table, one column per ice year (1973 to 2026), one row per day (Nov-10 onward), percent with 1 decimal, NA for no record
21
  Origin: ice charts from the US and Canadian ice services gridded by GLERL
 
 
22
  Check: Per ice year the agent takes the largest daily value in bas.txt and the day it occurs. Checked this round: 54 of 54 winters match AMIC.txt bas within 0.05 and the date in dates_AMIC.txt
23
  Companions (not included): data/ice/glicd/daily/README.txt (layout; given to the agent); data/ice/glicd/AMIC.txt (answer: annual maximum ice cover; hidden); data/ice/glicd/dates_AMIC.txt (answer: dates of the maxima; hidden)
campaign_files/2026-10-sc-science-reference-data-2/noaa-gml-aggi/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 applies the published forcing formulas (aggi.html lines 494 to 532, constants lines 503 to 512, preindustrial values lines 554 to 556) to CO2, CH4 and N2O; sums the six group columns to Total; divides Total by the 1990 Total 2.301 for the AGGI. Checked this round: forcing 137 of 138 gas-years within the derived bound (CH4 2020 at 0.00054 against 0.00052 is excluded); group sum max |diff| 0.001 for 46 years; AGGI max |diff| 0.00062.
14
 
15
  **Licence (SPDX):** LicenseRef-US-Government-Work
@@ -21,7 +19,5 @@ Files:
21
  - `sc146-04/NOAA_Annual_Mean_MoleFractions.csv`: NOAA Annual Greenhouse Gas Index: from the annual mean CO2, CH4 and N2O mole fractions compute the effective radiative forcing, then sum the gas groups and normalise to 1990.
22
  Format: CSV, 4 header lines, then one row per year (1979.5 to 2025.5) of 22 gas mole fractions; nd for no data
23
  Origin: agency index computed from network observations
24
- Reference result: published_aggregate_in_companion_file
25
- Reference source: AGGI_Table.csv columns CO2, CH4, N2O (W m-2), Total and "1990 = 1", e.g. line 13 "1990,1.332,0.487,0.133,0.327,0.020,0.003,2.301,428,1.000,1.7"
26
  Check: the agent applies the published forcing formulas (aggi.html lines 494 to 532, constants lines 503 to 512, preindustrial values lines 554 to 556) to CO2, CH4 and N2O; sums the six group columns to Total; divides Total by the 1990 Total 2.301 for the AGGI. Checked this round: forcing 137 of 138 gas-years within the derived bound (CH4 2020 at 0.00054 against 0.00052 is excluded); group sum max |diff| 0.001 for 46 years; AGGI max |diff| 0.00062
27
  Companions (not included): AGGI_Table.csv (answer: forcing per gas group, total and AGGI; hidden from the agent); aggi.html (forcing formulas and constants, lines 494 to 556)
 
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 applies the published forcing formulas (aggi.html lines 494 to 532, constants lines 503 to 512, preindustrial values lines 554 to 556) to CO2, CH4 and N2O; sums the six group columns to Total; divides Total by the 1990 Total 2.301 for the AGGI. Checked this round: forcing 137 of 138 gas-years within the derived bound (CH4 2020 at 0.00054 against 0.00052 is excluded); group sum max |diff| 0.001 for 46 years; AGGI max |diff| 0.00062.
12
 
13
  **Licence (SPDX):** LicenseRef-US-Government-Work
 
19
  - `sc146-04/NOAA_Annual_Mean_MoleFractions.csv`: NOAA Annual Greenhouse Gas Index: from the annual mean CO2, CH4 and N2O mole fractions compute the effective radiative forcing, then sum the gas groups and normalise to 1990.
20
  Format: CSV, 4 header lines, then one row per year (1979.5 to 2025.5) of 22 gas mole fractions; nd for no data
21
  Origin: agency index computed from network observations
 
 
22
  Check: the agent applies the published forcing formulas (aggi.html lines 494 to 532, constants lines 503 to 512, preindustrial values lines 554 to 556) to CO2, CH4 and N2O; sums the six group columns to Total; divides Total by the 1990 Total 2.301 for the AGGI. Checked this round: forcing 137 of 138 gas-years within the derived bound (CH4 2020 at 0.00054 against 0.00052 is excluded); group sum max |diff| 0.001 for 46 years; AGGI max |diff| 0.00062
23
  Companions (not included): AGGI_Table.csv (answer: forcing per gas group, total and AGGI; hidden from the agent); aggi.html (forcing formulas and constants, lines 494 to 556)
campaign_files/2026-10-sc-science-reference-data-2/noaa-gml-co2-spo-insitu/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_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: Hide the monthly file; the agent averages the valid daily values (value not -999.99, qcflag first character ".") per month and is scored within 0.005 ppm. Checked this round: 591/591 months within 0.005.
14
 
15
  **Licence (SPDX):** CC0-1.0
@@ -21,7 +19,5 @@ Files:
21
  - `sc094-04/co2_spo_surface-insitu_1_ccgg_DailyData.txt`: South Pole in situ CO2: recompute the monthly means from the daily means.
22
  Format: plain text, # header (licence at line 60) then space separated rows site, year, month, day, ..., value (ppm, 2 decimals), value_std_dev, nvalue, ..., qcflag; missing as -999.99
23
  Origin: agency in situ observation files as published
24
- Reference result: published_aggregate_in_companion_file
25
- Reference source: the value column of co2_spo_surface-insitu_1_ccgg_MonthlyData.txt, published by NOAA GML
26
  Check: hide the monthly file; the agent averages the valid daily values (value not -999.99, qcflag first character ".") per month and is scored within 0.005 ppm. Checked this round: 591/591 months within 0.005
27
  Companions (not included): co2_spo_surface-insitu_1_ccgg_MonthlyData.txt (answer file)
 
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: Hide the monthly file; the agent averages the valid daily values (value not -999.99, qcflag first character ".") per month and is scored within 0.005 ppm. Checked this round: 591/591 months within 0.005.
12
 
13
  **Licence (SPDX):** CC0-1.0
 
19
  - `sc094-04/co2_spo_surface-insitu_1_ccgg_DailyData.txt`: South Pole in situ CO2: recompute the monthly means from the daily means.
20
  Format: plain text, # header (licence at line 60) then space separated rows site, year, month, day, ..., value (ppm, 2 decimals), value_std_dev, nvalue, ..., qcflag; missing as -999.99
21
  Origin: agency in situ observation files as published
 
 
22
  Check: hide the monthly file; the agent averages the valid daily values (value not -999.99, qcflag first character ".") per month and is scored within 0.005 ppm. Checked this round: 591/591 months within 0.005
23
  Companions (not included): co2_spo_surface-insitu_1_ccgg_MonthlyData.txt (answer file)