Datasets:
Release [run release-20261111T090829Z]
#15
by Battam - opened
This view is limited to 50 files because it contains too many changes. See the raw diff here.
- CHANGELOG.md +16 -0
- README.md +27 -27
- README.zh.md +27 -27
- campaign_files/2026-10-a-spreadsheets-with-answers-2/goldstandard-tools-noassertion/README.md +0 -2
- campaign_files/2026-10-b-disk-images-3/gleapp-ntfs-deleted/README.md +0 -3
- campaign_files/2026-10-b-disk-images-3/go-filesystems-ext4-corrupt-fixtures/README.md +0 -3
- campaign_files/2026-10-b-disk-images-3/gomount-fs-fixtures-deleted/README.md +0 -4
- campaign_files/2026-10-c-repros-2/google-dp-accounting-repro/README.md +0 -2
- campaign_files/2026-10-c-repros-2/google-research-federated-repro/README.md +0 -2
- campaign_files/2026-10-g-solver-instances-2/grantm-sudoku-exchange-puzzle-bank/README.md +0 -4
- campaign_files/2026-10-gt-browser-tests-2/github-email-reply-parser/README.md +0 -4
- campaign_files/2026-10-gt-browser-tests-2/gnumeric-samples-selfcheck/README.md +0 -22
- campaign_files/2026-10-gt-browser-tests-2/golang-ical-serialization-input7/README.md +0 -4
- campaign_files/2026-10-hw-eda-tests-2/github-llvm-circt-test-conversion-exportverilog-lit-tests/README.md +0 -8
- campaign_files/2026-10-hw-eda-tests-2/github-nickg-nvc-test-regress-regression-suite-with-gold-files/README.md +0 -10
- campaign_files/2026-10-hw-eda-tests-2/github-zachjs-sv2v-test-core-regression-suite/README.md +0 -10
- campaign_files/2026-10-hw-eda-tests-2/gpx-github-markwal-gpx-master-at-commit-28f3460/README.md +0 -6
- campaign_files/2026-10-m-issue-trackers-2/gnu-help-gnu-emacs/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/gnupg-users/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/go-gerrit-changes/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/go-north-east-gtfs/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/gocornwallbus-passenger-gtfs/README.md +0 -4
- campaign_files/2026-10-m-issue-trackers-2/golang-maintner-mutlog/README.md +0 -22
- campaign_files/2026-10-md-media-and-documents/github-markup/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/gnome-pango-tests-layouts/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/gnu-groff-src-roff-groff-tests/README.md +0 -6
- campaign_files/2026-10-md-media-and-documents/go-org-testdata-tables/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/golang-image-testdata/README.md +0 -26
- campaign_files/2026-10-md-media-and-documents/goldmark-extension-testdata-footnote/README.md +0 -4
- campaign_files/2026-10-md-media-and-documents/gusbrs-zref-check-testfiles/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/github-amazon-science-petshop-root-cause-analysis/README.md +0 -8
- campaign_files/2026-10-ml-serving-configs-2/github-intelligentdds-nezha/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/github-markusthill-mgab/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/github-thufdd-thu-concept-drift-datasets/README.md +0 -4
- campaign_files/2026-10-ml-serving-configs-2/glibc-auto-libm-test-out/README.md +0 -18
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-1411-4/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-170a-4/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-199a-1/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-280f-7/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-36b-3/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-61-21/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-72-4/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1001-2/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1011-2/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1245-1/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1250-1/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1250-2/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1272-1/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1367-1/README.md +0 -4
- campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1377-1/README.md +0 -4
CHANGELOG.md
CHANGED
|
@@ -3065,3 +3065,19 @@ Changes to the content of this index, oldest first. There is one entry for each
|
|
| 3065 |
- hf-training-records: refused
|
| 3066 |
- npm: refused
|
| 3067 |
- stackexchange-api-posts: refused
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 3065 |
- hf-training-records: refused
|
| 3066 |
- npm: refused
|
| 3067 |
- stackexchange-api-posts: refused
|
| 3068 |
+
|
| 3069 |
+
## 2026-11-11: sources held back
|
| 3070 |
+
|
| 3071 |
+
- Each source below keeps its newest version that passed every check; its newer batch waits until it passes them:
|
| 3072 |
+
- 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
|
| 3073 |
+
- 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
|
| 3074 |
+
- cfpb-complaints: refused
|
| 3075 |
+
- 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
|
| 3076 |
+
- 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
|
| 3077 |
+
- 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
|
| 3078 |
+
- 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
|
| 3079 |
+
- 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
|
| 3080 |
+
- 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
|
| 3081 |
+
- hf-training-records: refused
|
| 3082 |
+
- npm: refused
|
| 3083 |
+
- 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/agentic-env-index/resolve/release-2026-11-11.
|
| 28 |
|
| 29 |
**Agentic Env Index:** 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/agentic-env-catalog) · [Usage video](https://huggingface.co/spaces/Battam/agentic-env-catalog#usage-video)
|
| 32 |
|
| 33 |
<picture class="not-prose">
|
| 34 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 35 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 36 |
</picture>
|
| 37 |
<picture class="not-prose">
|
| 38 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 39 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 40 |
</picture>
|
| 41 |
|
| 42 |
## Get data in one command
|
| 43 |
|
| 44 |
```sh
|
| 45 |
-
uv run https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 46 |
```
|
| 47 |
|
| 48 |
This fetches 3 units of every spreadsheet material set into `./data`, one folder per unit, and checks each file against the size and hashes its row records.
|
|
@@ -52,7 +52,7 @@ the same command takes the same units of this release.
|
|
| 52 |
<details>
|
| 53 |
<summary>What the command takes, and in which order</summary>
|
| 54 |
|
| 55 |
-
The command and the queries below are pinned to the release tag `release-2026-11-11.
|
| 56 |
[uv](https://docs.astral.sh/uv/) reads the script's dependencies, at the versions published before the day of this release.
|
| 57 |
|
| 58 |
The command returns units: 3 units from each material set whose form is `spreadsheets`, each in a folder of its own named after its `unit_id`.
|
|
@@ -79,7 +79,7 @@ Choose material sets from the catalog with [DuckDB](https://duckdb.org/):
|
|
| 79 |
|
| 80 |
```sql
|
| 81 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 82 |
-
FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.
|
| 83 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 84 |
ORDER BY collection, units DESC;
|
| 85 |
```
|
|
@@ -90,7 +90,7 @@ with `kind = 'corpus'` it returns corpora instead, counted in rows (`files`).
|
|
| 90 |
Choose files in one corpus:
|
| 91 |
|
| 92 |
```sql
|
| 93 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/agentic-env-index@release-2026-11-11.
|
| 94 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 95 |
FROM read_parquet(getvariable('files'))
|
| 96 |
WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
@@ -112,12 +112,12 @@ A data file may hold the rows of several sources, so the query keeps this one's
|
|
| 112 |
### Task material: units by collection
|
| 113 |
|
| 114 |
<picture class="not-prose">
|
| 115 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 116 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 117 |
</picture>
|
| 118 |
<picture class="not-prose">
|
| 119 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 120 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 121 |
</picture>
|
| 122 |
|
| 123 |
1,800 material sets with 4,184 units, in 14 collections (1 of them with no material set yet); 1 of the material sets are in no collection.
|
|
@@ -133,7 +133,7 @@ A data file may hold the rows of several sources, so the query keeps this one's
|
|
| 133 |
| SEC filing reviews | 0 | 0 | 0 | 0 | 0 B | 0 B |
|
| 134 |
| Solver instances | 64 | 188 | 335 | 61 | 127 MB | 127 MB |
|
| 135 |
| Browser tests | 123 | 439 | 852 | 88 | 32.0 MB | 32.0 MB |
|
| 136 |
-
| Hardware design (EDA) tests | 81 | 258 | 651 | 75 | 80.
|
| 137 |
| Issue trackers | 212 | 258 | 682 | 212 | 196 MB | 196 MB |
|
| 138 |
| Media and documents | 276 | 391 | 1,088 | 269 | 569 MB | 569 MB |
|
| 139 |
| Model serving configurations | 102 | 397 | 1,169 | 82 | 264 MB | 229 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/agentic-env-index/resolve/release-2026-11-11.
|
| 154 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 155 |
</picture>
|
| 156 |
<picture class="not-prose">
|
| 157 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 158 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 159 |
</picture>
|
| 160 |
|
| 161 |
139 corpora with 1,216,362,128 rows.
|
|
@@ -188,12 +188,12 @@ Every material set and every corpus, with its counts, size, license tier and log
|
|
| 188 |
## How it is made
|
| 189 |
|
| 190 |
<picture class="not-prose">
|
| 191 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 192 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 193 |
</picture>
|
| 194 |
<picture class="not-prose">
|
| 195 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 196 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 197 |
</picture>
|
| 198 |
|
| 199 |
The terms, each step and how every number is made are folded below.
|
|
@@ -247,9 +247,9 @@ only their sizes add up to the size of the whole index.
|
|
| 247 |
|
| 248 |
| Level | Recorded size | Deduplicated size | Rows read | Rows compared | Rows that match | Rows read, not compared | Rows without a recorded size | Their estimated size |
|
| 249 |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
|
| 250 |
-
| Whole index | 4.45 PB | 4.11 PB | 37,
|
| 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.89 GB | 2.82 GB |
|
| 253 |
|
| 254 |
Rows read are the sample of rows the check reads in `meta/sizes.parquet`;
|
| 255 |
a row compared matched its recorded size or did not, and a row read but not compared never reached its file.
|
|
@@ -444,9 +444,9 @@ Every row field and every column of the catalog: [`docs/fields.md`](docs/fields.
|
|
| 444 |
<details>
|
| 445 |
<summary>Releases</summary>
|
| 446 |
|
| 447 |
-
- Latest release: `release-2026-11-11.
|
| 448 |
- Releases are listed in [CHANGELOG.md](CHANGELOG.md);
|
| 449 |
-
each one is a commit with its own release tag (this one is [`release-2026-11-11.
|
| 450 |
so any earlier state stays readable at its tag.
|
| 451 |
- `meta/projection.json` records the release tag and the version of the program and templates that generated this card.
|
| 452 |
- Croissant metadata: [generated by the Hub](https://huggingface.co/api/datasets/Battam/agentic-env-index/croissant);
|
|
@@ -479,7 +479,7 @@ A removal covers the current version of this repository (the main branch) and th
|
|
| 479 |
@misc{agentic_env_index,
|
| 480 |
title = {agentic-env-index: an index of public materials for building agent environments},
|
| 481 |
howpublished = {https://huggingface.co/datasets/Battam/agentic-env-index},
|
| 482 |
-
note = {Release release-2026-11-11.
|
| 483 |
year = {2026}
|
| 484 |
}
|
| 485 |
```
|
|
|
|
| 24 |
<!-- artifact-pointer-layout: v2 -->
|
| 25 |
<!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
|
| 26 |
|
| 27 |
+
<img class="not-prose" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/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 |
**Agentic Env Index:** 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/agentic-env-catalog) · [Usage video](https://huggingface.co/spaces/Battam/agentic-env-catalog#usage-video)
|
| 32 |
|
| 33 |
<picture class="not-prose">
|
| 34 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/numbers-narrow-light.svg">
|
| 35 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/numbers-wide-light.svg" alt="1,800 material sets with 4,184 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 36,341 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/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/numbers-narrow-dark.svg">
|
| 39 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/numbers-wide-dark.svg" alt="1,800 material sets with 4,184 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 36,341 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/agentic-env-index/resolve/release-2026-11-11.8/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.8`.
|
| 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/agentic-env-index@release-2026-11-11.8/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/agentic-env-index@release-2026-11-11.8/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.8/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/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/material-narrow-light.svg">
|
| 116 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/material-wide-light.svg" alt="Units by collection, longest bar first: Spreadsheets 536; Browser tests 439; Tests and exercises 425; Model serving configurations 397; Media and documents 391; Science reference data 342; Rule calculations 329; Security detection 328; Hardware design (EDA) tests 258; Issue trackers 258; Solver instances 188; Disk images 179; Reproduction packages and runs 105; 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/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/material-narrow-dark.svg">
|
| 120 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/material-wide-dark.svg" alt="Units by collection, longest bar first: Spreadsheets 536; Browser tests 439; Tests and exercises 425; Model serving configurations 397; Media and documents 391; Science reference data 342; Rule calculations 329; Security detection 328; Hardware design (EDA) tests 258; Issue trackers 258; Solver instances 188; Disk images 179; Reproduction packages and runs 105; In no collection 9; SEC filing reviews 0.">
|
| 121 |
</picture>
|
| 122 |
|
| 123 |
1,800 material sets with 4,184 units, in 14 collections (1 of them with no material set yet); 1 of the material sets are in no collection.
|
|
|
|
| 133 |
| SEC filing reviews | 0 | 0 | 0 | 0 | 0 B | 0 B |
|
| 134 |
| Solver instances | 64 | 188 | 335 | 61 | 127 MB | 127 MB |
|
| 135 |
| Browser tests | 123 | 439 | 852 | 88 | 32.0 MB | 32.0 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 |
|
| 139 |
| Model serving configurations | 102 | 397 | 1,169 | 82 | 264 MB | 229 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/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/corpora-narrow-light.svg">
|
| 154 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/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/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/corpora-narrow-dark.svg">
|
| 158 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/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/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/steps-narrow-light.svg">
|
| 192 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/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.8.">
|
| 193 |
</picture>
|
| 194 |
<picture class="not-prose">
|
| 195 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/steps-narrow-dark.svg">
|
| 196 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/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.8.">
|
| 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 | 37,222 | 36,341 | 36,210 (99.6%) | 881: address unreachable 449, file gone 80, login needed 330, no size from the server 19, other error 3 | 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.89 GB | 2.82 GB | 5,628 | 5,618 | 5,600 (99.7%) | 10: login needed 8, other error 2 | 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.8` (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.8`](https://huggingface.co/datasets/Battam/agentic-env-index/tree/release-2026-11-11.8)),
|
| 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/agentic-env-index/croissant);
|
|
|
|
| 479 |
@misc{agentic_env_index,
|
| 480 |
title = {agentic-env-index: an index of public materials for building agent environments},
|
| 481 |
howpublished = {https://huggingface.co/datasets/Battam/agentic-env-index},
|
| 482 |
+
note = {Release release-2026-11-11.8},
|
| 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/agentic-env-index/resolve/release-2026-11-11.
|
| 15 |
|
| 16 |
**Agentic Env Index:**在这里找到可以用来构建智能体任务和环境的公开文件,并用一条命令把它们取下来。
|
| 17 |
|
| 18 |
[English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/agentic-env-catalog) · [使用示例视频](https://huggingface.co/spaces/Battam/agentic-env-catalog#usage-video)
|
| 19 |
|
| 20 |
<picture class="not-prose">
|
| 21 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 22 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 23 |
</picture>
|
| 24 |
<picture class="not-prose">
|
| 25 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 26 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 27 |
</picture>
|
| 28 |
|
| 29 |
## 一条命令取数据
|
| 30 |
|
| 31 |
```sh
|
| 32 |
-
uv run https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 33 |
```
|
| 34 |
|
| 35 |
这条命令从每个电子表格材料集各取 3 个单元放进 `./data`,每个单元一个文件夹,并按每个文件所在行记录的大小和哈希值校验它。
|
|
@@ -39,7 +39,7 @@ uv run https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-
|
|
| 39 |
<details>
|
| 40 |
<summary>命令取什么、按什么顺序取</summary>
|
| 41 |
|
| 42 |
-
这条命令和下面的查询都固定在发布标签 `release-2026-11-11.
|
| 43 |
[uv](https://docs.astral.sh/uv/) 会读取脚本声明的依赖,取这个发布当天之前发布的版本。
|
| 44 |
|
| 45 |
命令返回单元:形式为 `spreadsheets` 的每个材料集各 3 个单元,每个单元放在以它的 `unit_id` 命名的单独文件夹里。
|
|
@@ -66,7 +66,7 @@ uv run https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-
|
|
| 66 |
|
| 67 |
```sql
|
| 68 |
SELECT source, collection, title, units, files, top_types, license.tier AS license_tier, needs_auth
|
| 69 |
-
FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.
|
| 70 |
WHERE kind = 'material_set' AND needs_auth = 'no' AND license.tier IN ('permissive', 'share-alike')
|
| 71 |
ORDER BY collection, units DESC;
|
| 72 |
```
|
|
@@ -77,7 +77,7 @@ ORDER BY collection, units DESC;
|
|
| 77 |
在一个语料库里挑选文件:
|
| 78 |
|
| 79 |
```sql
|
| 80 |
-
SET VARIABLE files = (SELECT list('hf://datasets/Battam/agentic-env-index@release-2026-11-11.
|
| 81 |
SELECT uri, size_bytes, lower(hex(sha256)) AS sha256
|
| 82 |
FROM read_parquet(getvariable('files'))
|
| 83 |
WHERE source = 'if-archive' AND ext = 'pdf' AND size_bytes BETWEEN 100000 AND 5000000
|
|
@@ -99,12 +99,12 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 99 |
### 任务材料:按合集的单元数
|
| 100 |
|
| 101 |
<picture class="not-prose">
|
| 102 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 103 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 104 |
</picture>
|
| 105 |
<picture class="not-prose">
|
| 106 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 107 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 108 |
</picture>
|
| 109 |
|
| 110 |
1,800 个材料集,共 4,184 个单元,分在 14 个合集中(其中 1 个合集还没有材料集);其中 1 个材料集不属于任何合集。
|
|
@@ -120,7 +120,7 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 120 |
| SEC 申报审查 | 0 | 0 | 0 | 0 | 0 B | 0 B |
|
| 121 |
| 求解器实例 | 64 | 188 | 335 | 61 | 127 MB | 127 MB |
|
| 122 |
| 浏览器测试 | 123 | 439 | 852 | 88 | 32.0 MB | 32.0 MB |
|
| 123 |
-
| 硬件设计(EDA)测试 | 81 | 258 | 651 | 75 | 80.
|
| 124 |
| 问题跟踪系统 | 212 | 258 | 682 | 212 | 196 MB | 196 MB |
|
| 125 |
| 媒体和文档 | 276 | 391 | 1,088 | 269 | 569 MB | 569 MB |
|
| 126 |
| 模型服务配置 | 102 | 397 | 1,169 | 82 | 264 MB | 229 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/agentic-env-index/resolve/release-2026-11-11.
|
| 141 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 142 |
</picture>
|
| 143 |
<picture class="not-prose">
|
| 144 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 145 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 146 |
</picture>
|
| 147 |
|
| 148 |
139 个语料库,共 1,216,362,128 行。
|
|
@@ -175,12 +175,12 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 175 |
## 怎样做成
|
| 176 |
|
| 177 |
<picture class="not-prose">
|
| 178 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 179 |
-
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 180 |
</picture>
|
| 181 |
<picture class="not-prose">
|
| 182 |
-
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 183 |
-
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.
|
| 184 |
</picture>
|
| 185 |
|
| 186 |
术语、每一步,以及每个数字怎样得出,都折叠在下面。
|
|
@@ -234,9 +234,9 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 234 |
|
| 235 |
| 层级 | 记录的大小 | 去重后大小 | 读过的行 | 比对过的行 | 一致的行 | 读过但未比对的行 | 没有记录大小的行 | 这些行的估计大小 |
|
| 236 |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
|
| 237 |
-
| 整个索引 | 4.45 PB | 4.11 PB | 37,
|
| 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.89 GB | 2.82 GB |
|
| 240 |
|
| 241 |
读过的行是核对在 `meta/sizes.parquet` 中读取的抽样行;
|
| 242 |
比对过的行与记录的大小一致或不一致,读过但未比对的行没有取到它的文件。
|
|
@@ -433,9 +433,9 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 433 |
<details>
|
| 434 |
<summary>发布</summary>
|
| 435 |
|
| 436 |
-
- 最新发布:`release-2026-11-11.
|
| 437 |
- 各次发布列在 [CHANGELOG.md](CHANGELOG.md) 中;
|
| 438 |
-
每次发布是一个带有自己发布标签的提交(本次为 [`release-2026-11-11.
|
| 439 |
因此任何较早的状态都可以在它的标签处读到。
|
| 440 |
- `meta/projection.json` 记录发布标签,以及生成本卡片的程序和模板的版本。
|
| 441 |
- Croissant 元数据:[由 Hub 生成](https://huggingface.co/api/datasets/Battam/agentic-env-index/croissant);
|
|
@@ -476,7 +476,7 @@ ORDER BY size_bytes LIMIT 20;
|
|
| 476 |
@misc{agentic_env_index,
|
| 477 |
title = {agentic-env-index: an index of public materials for building agent environments},
|
| 478 |
howpublished = {https://huggingface.co/datasets/Battam/agentic-env-index},
|
| 479 |
-
note = {Release release-2026-11-11.
|
| 480 |
year = {2026}
|
| 481 |
}
|
| 482 |
```
|
|
|
|
| 11 |
---
|
| 12 |
<!-- Generated by artpool.index_projection from meta/, cards/*.yaml, the field registry and its templates. Every release regenerates it, so edits to this file do not last. -->
|
| 13 |
|
| 14 |
+
<img class="not-prose" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/banner.zh.svg" alt="公开网络,分两层(按合集的任务材料;语料库),每个文件一行(地址、大小、SHA-256、许可证),你的选择,下载并校验">
|
| 15 |
|
| 16 |
**Agentic Env Index:**在这里找到可以用来构建智能体任务和环境的公开文件,并用一条命令把它们取下来。
|
| 17 |
|
| 18 |
[English](README.md) | 简体中文 · [数据页](https://huggingface.co/spaces/Battam/agentic-env-catalog) · [使用示例视频](https://huggingface.co/spaces/Battam/agentic-env-catalog#usage-video)
|
| 19 |
|
| 20 |
<picture class="not-prose">
|
| 21 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/numbers-narrow-light.zh.svg">
|
| 22 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/numbers-wide-light.zh.svg" alt="1,800 个材料集,共 4,184 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 36,341 行中,99.6% 与记录的大小一致。">
|
| 23 |
</picture>
|
| 24 |
<picture class="not-prose">
|
| 25 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/numbers-narrow-dark.zh.svg">
|
| 26 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/numbers-wide-dark.zh.svg" alt="1,800 个材料集,共 4,184 个单元,分在 14 个合集;139 个语料库,共 1,216,362,128 行;指向的大小共 4.45 PB,索引存的是地址,不是文件副本;比对过的 36,341 行中,99.6% 与记录的大小一致。">
|
| 27 |
</picture>
|
| 28 |
|
| 29 |
## 一条命令取数据
|
| 30 |
|
| 31 |
```sh
|
| 32 |
+
uv run https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/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.8` 上。
|
| 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/agentic-env-index@release-2026-11-11.8/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/agentic-env-index@release-2026-11-11.8/' || f) FROM (SELECT unnest(data_files) AS f FROM 'hf://datasets/Battam/agentic-env-index@release-2026-11-11.8/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/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/material-narrow-light.zh.svg">
|
| 103 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/material-wide-light.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 397;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 188;磁盘镜像 179;复现包和运行 105;不属于任何合集 9;SEC 申报审查 0。">
|
| 104 |
</picture>
|
| 105 |
<picture class="not-prose">
|
| 106 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/material-narrow-dark.zh.svg">
|
| 107 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/material-wide-dark.zh.svg" alt="按合集的单元数,条形由长到短:电子表格 536;浏览器测试 439;测试和练习 425;模型服务配置 397;媒体和文档 391;科学参考数据 342;规则计算 329;安全检测 328;硬件设计(EDA)测试 258;问题跟踪系统 258;求解器实例 188;磁盘镜像 179;复现包和运行 105;不属于任何合集 9;SEC 申报审查 0。">
|
| 108 |
</picture>
|
| 109 |
|
| 110 |
1,800 个材料集,共 4,184 个单元,分在 14 个合集中(其中 1 个合集还没有材料集);其中 1 个材料集不属于任何合集。
|
|
|
|
| 120 |
| SEC 申报审查 | 0 | 0 | 0 | 0 | 0 B | 0 B |
|
| 121 |
| 求解器实例 | 64 | 188 | 335 | 61 | 127 MB | 127 MB |
|
| 122 |
| 浏览器测试 | 123 | 439 | 852 | 88 | 32.0 MB | 32.0 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 |
|
| 126 |
| 模型服务配置 | 102 | 397 | 1,169 | 82 | 264 MB | 229 MB |
|
|
|
|
| 137 |
### 语料库:按主要领域的行数
|
| 138 |
|
| 139 |
<picture class="not-prose">
|
| 140 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/corpora-narrow-light.zh.svg">
|
| 141 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/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/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/corpora-narrow-dark.zh.svg">
|
| 145 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/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/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/steps-narrow-light.zh.svg">
|
| 179 |
+
<img class="not-prose dark:hidden" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/steps-wide-light.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.8。">
|
| 180 |
</picture>
|
| 181 |
<picture class="not-prose">
|
| 182 |
+
<source media="(max-width: 1023px)" srcset="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/steps-narrow-dark.zh.svg">
|
| 183 |
+
<img class="not-prose hidden dark:block" src="https://huggingface.co/datasets/Battam/agentic-env-index/resolve/release-2026-11-11.8/docs/figures/steps-wide-dark.zh.svg" alt="索引分四步做成。1,采集:采集器整批读取完整上游,每个文件或每条记录记一行,成为语料库。2,收录:检索在上游找到的作品和成组的语料库行,收录为材料集。3,检查:发布前核对许可证、个人信息、与基准测试的重叠和大小。4,发布:一个带有自己标签的提交,release-2026-11-11.8。">
|
| 184 |
</picture>
|
| 185 |
|
| 186 |
术语、每一步,以及每个数字怎样得出,都折叠在下面。
|
|
|
|
| 234 |
|
| 235 |
| 层级 | 记录的大小 | 去重后大小 | 读过的行 | 比对过的行 | 一致的行 | 读过但未比对的行 | 没有记录大小的行 | 这些行的估计大小 |
|
| 236 |
|---|---:|---:|---:|---:|---:|---:|---:|---:|
|
| 237 |
+
| 整个索引 | 4.45 PB | 4.11 PB | 37,222 | 36,341 | 36,210(99.6%) | 881:地址无法访问 449 行、文件已不存在 80 行、需要登录 330 行、服务器未给出大小 19 行、其他错误 3 行 | 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.89 GB | 2.82 GB | 5,628 | 5,618 | 5,600(99.7%) | 10:需要登录 8 行、其他错误 2 行 | 0 | 无 |
|
| 240 |
|
| 241 |
读过的行是核对在 `meta/sizes.parquet` 中读取的抽样行;
|
| 242 |
比对过的行与记录的大小一致或不一致,读过但未比对的行没有取到它的文件。
|
|
|
|
| 433 |
<details>
|
| 434 |
<summary>发布</summary>
|
| 435 |
|
| 436 |
+
- 最新发布:`release-2026-11-11.8`(其最新的 CHANGELOG 条目日期为 2026-11-11)。
|
| 437 |
- 各次发布列在 [CHANGELOG.md](CHANGELOG.md) 中;
|
| 438 |
+
每次发布是一个带有自己发布标签的提交(本次为 [`release-2026-11-11.8`](https://huggingface.co/datasets/Battam/agentic-env-index/tree/release-2026-11-11.8)),
|
| 439 |
因此任何较早的状态都可以在它的标签处读到。
|
| 440 |
- `meta/projection.json` 记录发布标签,以及生成本卡片的程序和模板的版本。
|
| 441 |
- Croissant 元数据:[由 Hub 生成](https://huggingface.co/api/datasets/Battam/agentic-env-index/croissant);
|
|
|
|
| 476 |
@misc{agentic_env_index,
|
| 477 |
title = {agentic-env-index: an index of public materials for building agent environments},
|
| 478 |
howpublished = {https://huggingface.co/datasets/Battam/agentic-env-index},
|
| 479 |
+
note = {Release release-2026-11-11.8},
|
| 480 |
year = {2026}
|
| 481 |
}
|
| 482 |
```
|
campaign_files/2026-10-a-spreadsheets-with-answers-2/goldstandard-tools-noassertion/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Each 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:** Each 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-b-disk-images-3/gleapp-ntfs-deleted/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** Each file with an answer has one answer file, at answer/<unit path>.json (the unit path plus .json). Reference result kind: deleted_files.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Open with tools for these file types: .gz.
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -19,5 +17,4 @@
|
|
| 19 |
Files:
|
| 20 |
|
| 21 |
- `tests/fixtures/ntfs-deleted.img.gz`: GLEAPP test image: NTFS image with one resident and one non-resident deleted JPEG.
|
| 22 |
-
Reference result: deleted_files
|
| 23 |
Dependencies: gzip; sleuthkit fls
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Open with tools for these file types: .gz.
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 17 |
Files:
|
| 18 |
|
| 19 |
- `tests/fixtures/ntfs-deleted.img.gz`: GLEAPP test image: NTFS image with one resident and one non-resident deleted JPEG.
|
|
|
|
| 20 |
Dependencies: gzip; sleuthkit fls
|
campaign_files/2026-10-b-disk-images-3/go-filesystems-ext4-corrupt-fixtures/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: corruption_desc.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Open with tools for these file types: .gz.
|
| 14 |
|
| 15 |
**Licence (SPDX):** BSD-3-Clause
|
|
@@ -20,5 +18,4 @@ Files:
|
|
| 20 |
|
| 21 |
- `testdata/fixtures.tar.gz`: ext4 test corpus with four images each with one damaged superblock field, go-filesystems/ext4.
|
| 22 |
Origin: Upstream test fixture: made by e2fsprogs mke2fs, then one superblock field patched by upstream's generator.
|
| 23 |
-
Reference result: corruption_desc
|
| 24 |
Dependencies: gzip and tar or Python gzip and tarfile to unpack; only needed to rerun the exercise, not to grade the answer
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Open with tools for these file types: .gz.
|
| 12 |
|
| 13 |
**Licence (SPDX):** BSD-3-Clause
|
|
|
|
| 18 |
|
| 19 |
- `testdata/fixtures.tar.gz`: ext4 test corpus with four images each with one damaged superblock field, go-filesystems/ext4.
|
| 20 |
Origin: Upstream test fixture: made by e2fsprogs mke2fs, then one superblock field patched by upstream's generator.
|
|
|
|
| 21 |
Dependencies: gzip and tar or Python gzip and tarfile to unpack; only needed to rerun the exercise, not to grade the answer
|
campaign_files/2026-10-b-disk-images-3/gomount-fs-fixtures-deleted/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether each file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 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: deleted_files.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Open with tools for these file types: .gz.
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
@@ -19,8 +17,6 @@
|
|
| 19 |
Files:
|
| 20 |
|
| 21 |
- `fsx/testdata/ext4.img.gz`: Gomount test image: ext4 image with two orphan inodes and one deleted directory entry.
|
| 22 |
-
Reference result: deleted_files
|
| 23 |
Dependencies: sleuthkit fls; gzip or Python gzip to decompress
|
| 24 |
- `fsx/testdata/fat12.img.gz`: Gomount test image: FAT12 image with a deleted 8.3 file and a deleted long-name file.
|
| 25 |
-
Reference result: deleted_files
|
| 26 |
Dependencies: sleuthkit fls; gzip or Python gzip to decompress
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether each file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Open with tools for these file types: .gz.
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 17 |
Files:
|
| 18 |
|
| 19 |
- `fsx/testdata/ext4.img.gz`: Gomount test image: ext4 image with two orphan inodes and one deleted directory entry.
|
|
|
|
| 20 |
Dependencies: sleuthkit fls; gzip or Python gzip to decompress
|
| 21 |
- `fsx/testdata/fat12.img.gz`: Gomount test image: FAT12 image with a deleted 8.3 file and a deleted long-name file.
|
|
|
|
| 22 |
Dependencies: sleuthkit fls; gzip or Python gzip to decompress
|
campaign_files/2026-10-c-repros-2/google-dp-accounting-repro/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** Each unit with an answer has one answer file, at answer/<package>/reported.json.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Open with tools for these file types: .py.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Open with tools for these file types: .py.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
campaign_files/2026-10-c-repros-2/google-research-federated-repro/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether each unit needs other upstream files is not stated. 1 of 2 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:** Each unit with an answer has one answer file, at answer/<package>/reported.json.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Open with tools for these file types: .py; .txt; .md.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether each unit needs other upstream files is not stated. 1 of 2 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:** Open with tools for these file types: .py; .txt; .md.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
campaign_files/2026-10-g-solver-instances-2/grantm-sudoku-exchange-puzzle-bank/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: Unique solution grid (plus difficulty rating). 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 returns a full 9x9 grid; correct when every row, column and 3x3 box holds 1 to 9 once and every given digit is kept (rule check; with a unique solution this equals comparing with the solved grid). The rating column is a secondary difficulty label. No solver is needed at judge time.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Unlicense
|
|
@@ -20,8 +18,6 @@ Files:
|
|
| 20 |
|
| 21 |
- `g285-33/easy.txt`: easy.txt: 100,000 easy sudoku puzzles of the Sudoku Exchange puzzle bank.
|
| 22 |
Format: plain text, LF; 100,000 lines of 100 B: 12-hex-digit id, space, 81 digits row-major with 0 for an empty cell, two spaces, rating; a case is one line
|
| 23 |
-
Reference result: unique solution grid (plus difficulty rating)
|
| 24 |
-
Reference source: No solution grid ships. README: puzzles come from QQWing, which makes puzzles with a unique solution. all 100,000 lines distinct and 81 digits long.
|
| 25 |
Check: The agent returns a full 9x9 grid; correct when every row, column and 3x3 box holds 1 to 9 once and every given digit is kept (rule check; with a unique solution this equals comparing with the solved grid). The rating column is a secondary difficulty label. No solver is needed at judge time.
|
| 26 |
Companions (not included): LICENSE.txt; README.md
|
| 27 |
Dependencies: not packed
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: The agent returns a full 9x9 grid; correct when every row, column and 3x3 box holds 1 to 9 once and every given digit is kept (rule check; with a unique solution this equals comparing with the solved grid). The rating column is a secondary difficulty label. No solver is needed at judge time.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Unlicense
|
|
|
|
| 18 |
|
| 19 |
- `g285-33/easy.txt`: easy.txt: 100,000 easy sudoku puzzles of the Sudoku Exchange puzzle bank.
|
| 20 |
Format: plain text, LF; 100,000 lines of 100 B: 12-hex-digit id, space, 81 digits row-major with 0 for an empty cell, two spaces, rating; a case is one line
|
|
|
|
|
|
|
| 21 |
Check: The agent returns a full 9x9 grid; correct when every row, column and 3x3 box holds 1 to 9 once and every given digit is kept (rule check; with a unique solution this equals comparing with the solved grid). The rating column is a secondary difficulty label. No solver is needed at judge time.
|
| 22 |
Companions (not included): LICENSE.txt; README.md
|
| 23 |
Dependencies: not packed
|
campaign_files/2026-10-gt-browser-tests-2/github-email-reply-parser/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. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_values_in_test_code. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** EmailReplyParser.parse_reply (Ruby) or a port (email-reply-parser for Python or JavaScript), or a hand-written regex; the script writes the visible reply to a file
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `test/emails/email_2_1.txt`: Keep only the top reply of an Outlook message.
|
| 22 |
Format: plain-text message body (.txt); expected string in Ruby test code
|
| 23 |
Origin: email_reply_parser test fixture (tool_fixture)
|
| 24 |
-
Reference result: expected_values_in_test_code
|
| 25 |
-
Reference source: test/email_reply_parser_test.rb lines 154-157: parse_reply returns "Outlook with a reply"
|
| 26 |
Check: Final file state: the agent writes the visible reply to a file; its content must equal the string Outlook with a reply exactly. No screenshot
|
| 27 |
Tools: EmailReplyParser.parse_reply (Ruby) or a port (email-reply-parser for Python or JavaScript), or a hand-written regex; the script writes the visible reply to a file
|
| 28 |
Companions (not included): test/email_reply_parser_test.rb
|
|
|
|
| 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. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** EmailReplyParser.parse_reply (Ruby) or a port (email-reply-parser for Python or JavaScript), or a hand-written regex; the script writes the visible reply to a file
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `test/emails/email_2_1.txt`: Keep only the top reply of an Outlook message.
|
| 20 |
Format: plain-text message body (.txt); expected string in Ruby test code
|
| 21 |
Origin: email_reply_parser test fixture (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: Final file state: the agent writes the visible reply to a file; its content must equal the string Outlook with a reply exactly. No screenshot
|
| 23 |
Tools: EmailReplyParser.parse_reply (Ruby) or a port (email-reply-parser for Python or JavaScript), or a hand-written regex; the script writes the visible reply to a file
|
| 24 |
Companions (not included): test/email_reply_parser_test.rb
|
campaign_files/2026-10-gt-browser-tests-2/gnumeric-samples-selfcheck/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. 10 of 10 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: self_check_cell; expected_output_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:** Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1000-statfuns.pl); LibreOffice headless recalculation is a second engine. Other files: see the notes.
|
| 14 |
|
| 15 |
**Licence (SPDX):** (GPL-2.0-only OR GPL-3.0-only) AND NOASSERTION AND ((GPL-2.0-only OR GPL-3.0-only) AND CC-BY-SA-4.0 AND LicenseRef-US-Government-Work)
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `samples/excel/statfuns.xls`: Gnumeric self-check workbook statfuns.xls: statistical functions with expected values; A4 reports All ok.
|
| 22 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values and a summary cell
|
| 23 |
Origin: self-checking test workbooks kept by Gnumeric developers for regression testing of spreadsheet functions (tool_fixture); the drivers test/t1000-statfuns.pl and test/GnumericTest.pm (test_sheet_calc runs ssconvert --recalc and reads one cell) are named for provenance only: not in companions, not bundled, not run
|
| 24 |
-
Reference result: self_check_cell
|
| 25 |
-
Reference source: the workbook computes its own verdict: the regex /All ok/i (t1000-statfuns.pl); the expected values sit inside the workbook next to each function call
|
| 26 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match the regex /All ok/i (t1000-statfuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate and read the verdict cell. No screenshot needed
|
| 27 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1000-statfuns.pl); LibreOffice headless recalculation is a second engine
|
| 28 |
Companions (not included): COPYING
|
|
@@ -30,8 +26,6 @@ Files:
|
|
| 30 |
- `samples/excel/finfuns.xls`: Gnumeric self-check workbook finfuns.xls: financial functions with expected values; A4 reports All ok.
|
| 31 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values and a summary cell
|
| 32 |
Origin: self-checking test workbooks kept by Gnumeric developers for regression testing of spreadsheet functions (tool_fixture); the drivers test/t1002-finfuns.pl and test/GnumericTest.pm (test_sheet_calc runs ssconvert --recalc and reads one cell) are named for provenance only: not in companions, not bundled, not run
|
| 33 |
-
Reference result: self_check_cell
|
| 34 |
-
Reference source: the workbook computes its own verdict: the regex /All ok/i (t1002-finfuns.pl); the expected values sit inside the workbook next to each function call
|
| 35 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match the regex /All ok/i (t1002-finfuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate and read the verdict cell. No screenshot needed
|
| 36 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1002-finfuns.pl); LibreOffice headless recalculation is a second engine
|
| 37 |
Companions (not included): COPYING
|
|
@@ -39,8 +33,6 @@ Files:
|
|
| 39 |
- `samples/excel/textfuns.xls`: Gnumeric self-check workbook textfuns.xls: text functions with expected values; A4 reports All ok.
|
| 40 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values and a summary cell
|
| 41 |
Origin: self-checking test workbooks kept by Gnumeric developers for regression testing of spreadsheet functions (tool_fixture); the drivers test/t1004-textfuns.pl and test/GnumericTest.pm (test_sheet_calc runs ssconvert --recalc and reads one cell) are named for provenance only: not in companions, not bundled, not run
|
| 42 |
-
Reference result: self_check_cell
|
| 43 |
-
Reference source: the workbook computes its own verdict: the regex /All ok/i (t1004-textfuns.pl); the expected values sit inside the workbook next to each function call
|
| 44 |
Check: Final file state: recalculate under the en_US locale (LC_ALL=en_US.UTF-8 for ssconvert; locale en-US for soffice), because the DOLLAR, FIXED and TEXT expected values are US-formatted ("$12,345.00", "($30)", "1,234.57", "April, 15, 99"); recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match the regex /All ok/i (t1004-textfuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate under en_US and read the verdict cell. No screenshot needed
|
| 45 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1004-textfuns.pl); LibreOffice headless recalculation is a second engine
|
| 46 |
Companions (not included): COPYING
|
|
@@ -48,8 +40,6 @@ Files:
|
|
| 48 |
- `samples/xlookup.gnumeric`: Gnumeric self-check workbook xlookup.gnumeric: XMATCH and XLOOKUP cases with expected results; D1 is TRUE when all pass.
|
| 49 |
Format: Gnumeric XML workbook (gzip-compressed .gnumeric) with lookup formulas, expected values and a verdict cell
|
| 50 |
Origin: self-checking test workbooks kept by Gnumeric developers for regression testing of spreadsheet functions (tool_fixture); the drivers test/t1110-xlookup.pl and test/GnumericTest.pm (test_sheet_calc runs ssconvert --recalc and reads one cell) are named for provenance only: not in companions, not bundled, not run
|
| 51 |
-
Reference result: self_check_cell
|
| 52 |
-
Reference source: the workbook computes its own verdict: the regex /TRUE/i (t1110-xlookup.pl); D1 is =and(D11:D65536); the expected values sit inside the workbook next to each function call
|
| 53 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read D1; it must match the regex /TRUE/i (t1110-xlookup.pl); D1 is =and(D11:D65536). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate and read the verdict cell. No screenshot needed
|
| 54 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=D1 FILE out.csv (exactly the check in test/t1110-xlookup.pl); LibreOffice headless recalculation is a second engine
|
| 55 |
Companions (not included): COPYING
|
|
@@ -57,8 +47,6 @@ Files:
|
|
| 57 |
- `samples/linest.xls`: Gnumeric self-check workbook linest.xls: LINEST regression on 11 NIST StRD datasets (Norris, Pontius, NoInt1, NoInt2, Filip, Longley, Wampler1 to 5) against their certified values; A1 reports Ok!
|
| 58 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with LINEST array formulas, NIST StRD data and certified values, and an overview verdict
|
| 59 |
Origin: self-checking test workbooks kept by Gnumeric developers for regression testing of spreadsheet functions (tool_fixture); the drivers test/t1104-linest.pl and test/GnumericTest.pm (test_sheet_calc runs ssconvert --recalc and reads one cell) are named for provenance only: not in companions, not bundled, not run; the data and certified values on the 11 dataset sheets are copied from NIST StRD (Standard Reference Database 140, linear regression datasets), each sheet keeps the NIST header ("NIST/ITL StRD", "Dataset Name: Norris (Norris.dat)", "Certified Values")
|
| 60 |
-
Reference result: self_check_cell
|
| 61 |
-
Reference source: the workbook computes its own verdict: the regex /\bOk\!/i (t1104-linest.pl); the expected values sit inside the workbook next to each function call
|
| 62 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A1; it must match the regex /\bOk\!/i (t1104-linest.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate and read the verdict cell. No screenshot needed
|
| 63 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A1 FILE out.csv (exactly the check in test/t1104-linest.pl); LibreOffice headless recalculation is a second engine
|
| 64 |
Companions (not included): COPYING
|
|
@@ -66,8 +54,6 @@ Files:
|
|
| 66 |
- `samples/excel/engfuns.xls`: Gnumeric self-check workbook engfuns.xls: engineering functions (complex-number functions, base conversion and other engineering functions) with expected values; A4 reports All ok.
|
| 67 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values, per-row status cells and a summary cell
|
| 68 |
Origin: self-checking test files kept by Gnumeric developers for regression testing (tool_fixture); the drivers test/t1003-engfuns.pl and test/GnumericTest.pm are named for provenance only: not in companions, not bundled, not run
|
| 69 |
-
Reference result: self_check_cell
|
| 70 |
-
Reference source: the workbook computes its own verdict: A4 = IF(H51,"All ok.","FAILED!!"), H51 = B8=SUM(H13:H50), A8 = SUM(H13:H50); the expected values sit beside each function call (B/C, D/E, F/G); t1003-engfuns.pl line 10 checks A4 against /All ok/i
|
| 71 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match the regex /All ok/i (t1003-engfuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate and read the verdict cell; numeric rows compare with an absolute limit of 1E-4 and complex-string rows by exact equality, as the status formulas do. No screenshot needed Rows judged by exact equality, no tolerance (not a judge parameter): exact rows: result = correct for all 3 tests (12 rows: complex-number and base-conversion strings) (GNOME/gnumeric@2b0350cb6136cd82fd04105822d3de920fa7eafa samples/excel/engfuns.xls status formulas of the form IF(AND(B=C,D=E,F=G),1,0) (BIFF tokens), 12 rows of Sheet1 H13:H50).
|
| 72 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1003-engfuns.pl); LibreOffice headless recalculation is a second engine
|
| 73 |
Companions (not included): COPYING
|
|
@@ -75,8 +61,6 @@ Files:
|
|
| 75 |
- `samples/excel/datefuns.xls`: Gnumeric self-check workbook datefuns.xls: date and time functions (TIME, TIMEVALUE and other date functions) with expected values; A4 reports All ok.
|
| 76 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values, per-row status cells and a summary cell
|
| 77 |
Origin: self-checking test files kept by Gnumeric developers for regression testing (tool_fixture); the drivers test/t1006-datefuns.pl and test/GnumericTest.pm are named for provenance only: not in companions, not bundled, not run
|
| 78 |
-
Reference result: self_check_cell
|
| 79 |
-
Reference source: the workbook computes its own verdict: A4 = IF(A8=B8,"All ok.","FAILED!!"), A8 = SUM(H21:H38), H39 = COUNT(H21:H38)=SUM(H21:H38); the expected values sit beside each function call; t1006-datefuns.pl line 10 checks A4 against /All ok/i
|
| 80 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match /All ok/i (t1006-datefuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, recalculate and read the verdict cell; rows compare by exact equality except the TIME and TIMEVALUE rows, which use an absolute limit of 1E-7 days. Rows 31 (NOW()) and 35 (TODAY()) have no expected value and a constant status of 1, so they are not judged and are left out of tasks. No screenshot needed Rows judged by exact equality, no tolerance (not a judge parameter): exact rows: result = correct for all tests (14 rows) (GNOME/gnumeric@2b0350cb6136cd82fd04105822d3de920fa7eafa samples/excel/datefuns.xls status formulas of the form IF(AND(B=C,D=E,F=G),1,0) (BIFF tokens), 14 rows of Sheet1 H21:H38); untested rows: rows 31 (NOW) and 35 (TODAY): status H is the constant 1, not judged (GNOME/gnumeric@2b0350cb6136cd82fd04105822d3de920fa7eafa samples/excel/datefuns.xls Sheet1 B31 = NOW(), B35 = TODAY(), H31 and H35 hold the number 1 (no formula), no C31 or C35 cell).
|
| 81 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1006-datefuns.pl); LibreOffice headless recalculation is a second engine
|
| 82 |
Companions (not included): COPYING
|
|
@@ -84,8 +68,6 @@ Files:
|
|
| 84 |
- `samples/excel/mathfuns.xls`: Gnumeric self-check workbook mathfuns.xls: math and trigonometry functions with expected values; A4 reports All ok.
|
| 85 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values, per-row status cells and a summary cell
|
| 86 |
Origin: self-checking test files kept by Gnumeric developers for regression testing (tool_fixture); the drivers test/t1001-mathfuns.pl and test/GnumericTest.pm are named for provenance only: not in companions, not bundled, not run
|
| 87 |
-
Reference result: self_check_cell
|
| 88 |
-
Reference source: the workbook computes its own verdict: A4 = IF(H81,"All ok.","FAILED!!"), H81 compares B8 with the sum over H21:H80; the expected values sit beside each function call; t1001-mathfuns.pl line 10 checks A4 against /All ok/i
|
| 89 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match /All ok/i (t1001-mathfuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, recalculate and read the verdict cell; numeric rows compare with a relative limit of 1E-13, the rest by exact equality, as the status formulas do. No screenshot needed Rows judged by exact equality, no tolerance (not a judge parameter): exact rows: result - correct = 0 for every test (12 rows) (GNOME/gnumeric@2b0350cb6136cd82fd04105822d3de920fa7eafa samples/excel/mathfuns.xls status formulas of the form (B-C=0)*(D-E=0)*(F-G=0) (BIFF tokens), 12 rows of Sheet1 H21:H80).
|
| 90 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1001-mathfuns.pl); LibreOffice headless recalculation is a second engine
|
| 91 |
Companions (not included): COPYING
|
|
@@ -93,8 +75,6 @@ Files:
|
|
| 93 |
- `samples/cronbach.gnumeric`: Gnumeric self-check workbook cronbach.gnumeric: Cronbach's alpha (internal-consistency reliability) for two binary questionnaires (11 items by 12 respondents, 10 items by 9 respondents), computed by hand from item variances and by the CRONBACH function; B2 reports TRUE.
|
| 94 |
Format: Gnumeric workbook (.gnumeric, gzip-compressed XML) with two response tables, hand computation, the CRONBACH function and a TRUE/FALSE check cell
|
| 95 |
Origin: self-checking test files kept by Gnumeric developers for regression testing (tool_fixture); the drivers test/t1107-cronbach.pl and test/GnumericTest.pm are named for provenance only: not in companions, not bundled, not run
|
| 96 |
-
Reference result: self_check_cell
|
| 97 |
-
Reference source: the workbook computes its own verdict: cell B2 = and(abs(B25-B27)<0.0001,abs(B47-B49)<0.0001), comparing for each dataset alpha computed from the variance formula with the CRONBACH function; t1107-cronbach.pl line 10 checks B2 against /\bTRUE\b/i
|
| 98 |
Check: Final file state: recalculate with ssconvert --recalc --export-range=B2 (GnumericTest.pm test_sheet_calc, lines 401 to 412) and read B2; it must match /\bTRUE\b/i. For a task built from it, give the agent the two response tables, have it compute Cronbach's alpha in the hand-computation cells (B25, B47) by the variance formula, then recalculate and check |alpha - CRONBACH value| < 1E-4 as B2 does. No screenshot needed
|
| 99 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=B2 FILE out.csv (the check in test/t1107-cronbach.pl); the file is gzip-compressed XML, so the hand-computation cells can also be written with any XML library; LibreOffice has no CRONBACH function, so Gnumeric is the engine
|
| 100 |
Companions (not included): COPYING
|
|
@@ -102,8 +82,6 @@ Files:
|
|
| 102 |
- `samples/tool-tests.gnumeric`: Gnumeric analysis-tool tests on tool-tests.gnumeric: three tasks on one workbook, the anova tool (single-factor ANOVA on 3 groups of 5 values), the regression tool (least-squares linear regression of y on x, 30 points) and the descriptive-statistics tool (30 values); expected output CSVs in test/t7201-anova.pl, test/t7200-regression.pl and test/t7203-descriptive-statistics.pl.
|
| 103 |
Format: Gnumeric workbook (.gnumeric, gzip-compressed XML) holding the input sheets; the expected tool output is the CSV after __DATA__ in the Perl test script
|
| 104 |
Origin: self-checking test files kept by Gnumeric developers for regression testing (tool_fixture); the drivers test/GnumericTest.pm are named for provenance only: not in companions, not bundled, not run
|
| 105 |
-
Reference result: expected_output_file
|
| 106 |
-
Reference source: [anova] the expected CSV of the anova tool output (summary per group, SS, df, MS, F = 9.591107036442812, P-value = 0.0032482226008593005, F critical) in the __DATA__ section of test/t7201-anova.pl (from line 32); the input is the NIST e-Handbook 7.4.3.3 example, whose published F is about 9.59. | [descriptive-statistics] the expected CSV of the descriptive-statistics tool output, range A1:B26 (Mean = 4.150147712176364 and the other statistics) in the __DATA__ section of test/t7203-descriptive-statistics.pl (from line 31).
|
| 107 |
Check: [anova] Final file state: run the anova tool on the input sheet headless, then compare the exported CSV with the __DATA__ block of test/t7201-anova.pl by exact string equality, as upstream does. For a task built from it, give the agent the input workbook and ask it to produce the anova tool output: 14 rows, Summary and ANOVA tables in a new sheet (with the Gnumeric tool or by formulas), export the range and compare; since upstream compares text exactly, a task that lets the agent use formulas should also accept numerically equal output, but no tolerance is given upstream, so the only cited judge is exact text equality. No screenshot needed | [regression] Final file state: run the regression tool on the input sheet headless, then compare the exported CSV with the __DATA__ block of test/t7200-regression.pl by exact string equality, as upstream does. For a task built from it, give the agent the input workbook and ask it to produce the regression output range A1:G18 in a new sheet (with the Gnumeric tool or by formulas), export the range and compare; since upstream compares text exactly, a task that lets the agent use formulas should also accept numerically equal output, but no tolerance is given upstream, so the only cited judge is exact text equality. No screenshot needed | [descriptive-statistics] Final file state: run the descriptive-statistics tool on the input sheet headless, then compare the exported CSV with the __DATA__ block of test/t7203-descriptive-statistics.pl by exact string equality, as upstream does. For a task built from it, give the agent the input workbook and ask it to produce the descriptive statistics output range A1:B26 in a new sheet (with the Gnumeric tool or by formulas), export the range and compare; since upstream compares text exactly, a task that lets the agent use formulas should also accept numerically equal output, but no tolerance is given upstream, so the only cited judge is exact text equality. No screenshot needed
|
| 108 |
Tools: Gnumeric headless: ssconvert [--export-range=RANGE] --tool-test=TOOL --tool-test=ARG:VALUE ... FILE out.csv with TOOL anova, regression or descriptive-statistics (export range A1:B26) (the command test_tool builds in test/GnumericTest.pm line 947); LibreOffice has Analysis of Variance / Regression / Descriptive Statistics dialogs but no headless switch for them, so Gnumeric ssconvert is the terminal route
|
| 109 |
Companions (not included): COPYING; test/t7201-anova.pl; test/t7200-regression.pl; test/t7203-descriptive-statistics.pl
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 10 of 10 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:** Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1000-statfuns.pl); LibreOffice headless recalculation is a second engine. Other files: see the notes.
|
| 12 |
|
| 13 |
**Licence (SPDX):** (GPL-2.0-only OR GPL-3.0-only) AND NOASSERTION AND ((GPL-2.0-only OR GPL-3.0-only) AND CC-BY-SA-4.0 AND LicenseRef-US-Government-Work)
|
|
|
|
| 19 |
- `samples/excel/statfuns.xls`: Gnumeric self-check workbook statfuns.xls: statistical functions with expected values; A4 reports All ok.
|
| 20 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values and a summary cell
|
| 21 |
Origin: self-checking test workbooks kept by Gnumeric developers for regression testing of spreadsheet functions (tool_fixture); the drivers test/t1000-statfuns.pl and test/GnumericTest.pm (test_sheet_calc runs ssconvert --recalc and reads one cell) are named for provenance only: not in companions, not bundled, not run
|
|
|
|
|
|
|
| 22 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match the regex /All ok/i (t1000-statfuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate and read the verdict cell. No screenshot needed
|
| 23 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1000-statfuns.pl); LibreOffice headless recalculation is a second engine
|
| 24 |
Companions (not included): COPYING
|
|
|
|
| 26 |
- `samples/excel/finfuns.xls`: Gnumeric self-check workbook finfuns.xls: financial functions with expected values; A4 reports All ok.
|
| 27 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values and a summary cell
|
| 28 |
Origin: self-checking test workbooks kept by Gnumeric developers for regression testing of spreadsheet functions (tool_fixture); the drivers test/t1002-finfuns.pl and test/GnumericTest.pm (test_sheet_calc runs ssconvert --recalc and reads one cell) are named for provenance only: not in companions, not bundled, not run
|
|
|
|
|
|
|
| 29 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match the regex /All ok/i (t1002-finfuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate and read the verdict cell. No screenshot needed
|
| 30 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1002-finfuns.pl); LibreOffice headless recalculation is a second engine
|
| 31 |
Companions (not included): COPYING
|
|
|
|
| 33 |
- `samples/excel/textfuns.xls`: Gnumeric self-check workbook textfuns.xls: text functions with expected values; A4 reports All ok.
|
| 34 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values and a summary cell
|
| 35 |
Origin: self-checking test workbooks kept by Gnumeric developers for regression testing of spreadsheet functions (tool_fixture); the drivers test/t1004-textfuns.pl and test/GnumericTest.pm (test_sheet_calc runs ssconvert --recalc and reads one cell) are named for provenance only: not in companions, not bundled, not run
|
|
|
|
|
|
|
| 36 |
Check: Final file state: recalculate under the en_US locale (LC_ALL=en_US.UTF-8 for ssconvert; locale en-US for soffice), because the DOLLAR, FIXED and TEXT expected values are US-formatted ("$12,345.00", "($30)", "1,234.57", "April, 15, 99"); recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match the regex /All ok/i (t1004-textfuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate under en_US and read the verdict cell. No screenshot needed
|
| 37 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1004-textfuns.pl); LibreOffice headless recalculation is a second engine
|
| 38 |
Companions (not included): COPYING
|
|
|
|
| 40 |
- `samples/xlookup.gnumeric`: Gnumeric self-check workbook xlookup.gnumeric: XMATCH and XLOOKUP cases with expected results; D1 is TRUE when all pass.
|
| 41 |
Format: Gnumeric XML workbook (gzip-compressed .gnumeric) with lookup formulas, expected values and a verdict cell
|
| 42 |
Origin: self-checking test workbooks kept by Gnumeric developers for regression testing of spreadsheet functions (tool_fixture); the drivers test/t1110-xlookup.pl and test/GnumericTest.pm (test_sheet_calc runs ssconvert --recalc and reads one cell) are named for provenance only: not in companions, not bundled, not run
|
|
|
|
|
|
|
| 43 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read D1; it must match the regex /TRUE/i (t1110-xlookup.pl); D1 is =and(D11:D65536). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate and read the verdict cell. No screenshot needed
|
| 44 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=D1 FILE out.csv (exactly the check in test/t1110-xlookup.pl); LibreOffice headless recalculation is a second engine
|
| 45 |
Companions (not included): COPYING
|
|
|
|
| 47 |
- `samples/linest.xls`: Gnumeric self-check workbook linest.xls: LINEST regression on 11 NIST StRD datasets (Norris, Pontius, NoInt1, NoInt2, Filip, Longley, Wampler1 to 5) against their certified values; A1 reports Ok!
|
| 48 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with LINEST array formulas, NIST StRD data and certified values, and an overview verdict
|
| 49 |
Origin: self-checking test workbooks kept by Gnumeric developers for regression testing of spreadsheet functions (tool_fixture); the drivers test/t1104-linest.pl and test/GnumericTest.pm (test_sheet_calc runs ssconvert --recalc and reads one cell) are named for provenance only: not in companions, not bundled, not run; the data and certified values on the 11 dataset sheets are copied from NIST StRD (Standard Reference Database 140, linear regression datasets), each sheet keeps the NIST header ("NIST/ITL StRD", "Dataset Name: Norris (Norris.dat)", "Certified Values")
|
|
|
|
|
|
|
| 50 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A1; it must match the regex /\bOk\!/i (t1104-linest.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate and read the verdict cell. No screenshot needed
|
| 51 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A1 FILE out.csv (exactly the check in test/t1104-linest.pl); LibreOffice headless recalculation is a second engine
|
| 52 |
Companions (not included): COPYING
|
|
|
|
| 54 |
- `samples/excel/engfuns.xls`: Gnumeric self-check workbook engfuns.xls: engineering functions (complex-number functions, base conversion and other engineering functions) with expected values; A4 reports All ok.
|
| 55 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values, per-row status cells and a summary cell
|
| 56 |
Origin: self-checking test files kept by Gnumeric developers for regression testing (tool_fixture); the drivers test/t1003-engfuns.pl and test/GnumericTest.pm are named for provenance only: not in companions, not bundled, not run
|
|
|
|
|
|
|
| 57 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match the regex /All ok/i (t1003-engfuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, then recalculate and read the verdict cell; numeric rows compare with an absolute limit of 1E-4 and complex-string rows by exact equality, as the status formulas do. No screenshot needed Rows judged by exact equality, no tolerance (not a judge parameter): exact rows: result = correct for all 3 tests (12 rows: complex-number and base-conversion strings) (GNOME/gnumeric@2b0350cb6136cd82fd04105822d3de920fa7eafa samples/excel/engfuns.xls status formulas of the form IF(AND(B=C,D=E,F=G),1,0) (BIFF tokens), 12 rows of Sheet1 H13:H50).
|
| 58 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1003-engfuns.pl); LibreOffice headless recalculation is a second engine
|
| 59 |
Companions (not included): COPYING
|
|
|
|
| 61 |
- `samples/excel/datefuns.xls`: Gnumeric self-check workbook datefuns.xls: date and time functions (TIME, TIMEVALUE and other date functions) with expected values; A4 reports All ok.
|
| 62 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values, per-row status cells and a summary cell
|
| 63 |
Origin: self-checking test files kept by Gnumeric developers for regression testing (tool_fixture); the drivers test/t1006-datefuns.pl and test/GnumericTest.pm are named for provenance only: not in companions, not bundled, not run
|
|
|
|
|
|
|
| 64 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match /All ok/i (t1006-datefuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, recalculate and read the verdict cell; rows compare by exact equality except the TIME and TIMEVALUE rows, which use an absolute limit of 1E-7 days. Rows 31 (NOW()) and 35 (TODAY()) have no expected value and a constant status of 1, so they are not judged and are left out of tasks. No screenshot needed Rows judged by exact equality, no tolerance (not a judge parameter): exact rows: result = correct for all tests (14 rows) (GNOME/gnumeric@2b0350cb6136cd82fd04105822d3de920fa7eafa samples/excel/datefuns.xls status formulas of the form IF(AND(B=C,D=E,F=G),1,0) (BIFF tokens), 14 rows of Sheet1 H21:H38); untested rows: rows 31 (NOW) and 35 (TODAY): status H is the constant 1, not judged (GNOME/gnumeric@2b0350cb6136cd82fd04105822d3de920fa7eafa samples/excel/datefuns.xls Sheet1 B31 = NOW(), B35 = TODAY(), H31 and H35 hold the number 1 (no formula), no C31 or C35 cell).
|
| 65 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1006-datefuns.pl); LibreOffice headless recalculation is a second engine
|
| 66 |
Companions (not included): COPYING
|
|
|
|
| 68 |
- `samples/excel/mathfuns.xls`: Gnumeric self-check workbook mathfuns.xls: math and trigonometry functions with expected values; A4 reports All ok.
|
| 69 |
Format: Excel 97-2003 workbook (BIFF8 .xls) with function calls, expected values, per-row status cells and a summary cell
|
| 70 |
Origin: self-checking test files kept by Gnumeric developers for regression testing (tool_fixture); the drivers test/t1001-mathfuns.pl and test/GnumericTest.pm are named for provenance only: not in companions, not bundled, not run
|
|
|
|
|
|
|
| 71 |
Check: Final file state: recalculate with ssconvert --recalc (or soffice --headless) and read A4; it must match /All ok/i (t1001-mathfuns.pl). For a task built from it, empty the function cells and hide the expected columns, let the agent write them, recalculate and read the verdict cell; numeric rows compare with a relative limit of 1E-13, the rest by exact equality, as the status formulas do. No screenshot needed Rows judged by exact equality, no tolerance (not a judge parameter): exact rows: result - correct = 0 for every test (12 rows) (GNOME/gnumeric@2b0350cb6136cd82fd04105822d3de920fa7eafa samples/excel/mathfuns.xls status formulas of the form (B-C=0)*(D-E=0)*(F-G=0) (BIFF tokens), 12 rows of Sheet1 H21:H80).
|
| 72 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=A4 FILE out.csv (exactly the check in test/t1001-mathfuns.pl); LibreOffice headless recalculation is a second engine
|
| 73 |
Companions (not included): COPYING
|
|
|
|
| 75 |
- `samples/cronbach.gnumeric`: Gnumeric self-check workbook cronbach.gnumeric: Cronbach's alpha (internal-consistency reliability) for two binary questionnaires (11 items by 12 respondents, 10 items by 9 respondents), computed by hand from item variances and by the CRONBACH function; B2 reports TRUE.
|
| 76 |
Format: Gnumeric workbook (.gnumeric, gzip-compressed XML) with two response tables, hand computation, the CRONBACH function and a TRUE/FALSE check cell
|
| 77 |
Origin: self-checking test files kept by Gnumeric developers for regression testing (tool_fixture); the drivers test/t1107-cronbach.pl and test/GnumericTest.pm are named for provenance only: not in companions, not bundled, not run
|
|
|
|
|
|
|
| 78 |
Check: Final file state: recalculate with ssconvert --recalc --export-range=B2 (GnumericTest.pm test_sheet_calc, lines 401 to 412) and read B2; it must match /\bTRUE\b/i. For a task built from it, give the agent the two response tables, have it compute Cronbach's alpha in the hand-computation cells (B25, B47) by the variance formula, then recalculate and check |alpha - CRONBACH value| < 1E-4 as B2 does. No screenshot needed
|
| 79 |
Tools: Gnumeric headless: ssconvert --recalc --export-range=B2 FILE out.csv (the check in test/t1107-cronbach.pl); the file is gzip-compressed XML, so the hand-computation cells can also be written with any XML library; LibreOffice has no CRONBACH function, so Gnumeric is the engine
|
| 80 |
Companions (not included): COPYING
|
|
|
|
| 82 |
- `samples/tool-tests.gnumeric`: Gnumeric analysis-tool tests on tool-tests.gnumeric: three tasks on one workbook, the anova tool (single-factor ANOVA on 3 groups of 5 values), the regression tool (least-squares linear regression of y on x, 30 points) and the descriptive-statistics tool (30 values); expected output CSVs in test/t7201-anova.pl, test/t7200-regression.pl and test/t7203-descriptive-statistics.pl.
|
| 83 |
Format: Gnumeric workbook (.gnumeric, gzip-compressed XML) holding the input sheets; the expected tool output is the CSV after __DATA__ in the Perl test script
|
| 84 |
Origin: self-checking test files kept by Gnumeric developers for regression testing (tool_fixture); the drivers test/GnumericTest.pm are named for provenance only: not in companions, not bundled, not run
|
|
|
|
|
|
|
| 85 |
Check: [anova] Final file state: run the anova tool on the input sheet headless, then compare the exported CSV with the __DATA__ block of test/t7201-anova.pl by exact string equality, as upstream does. For a task built from it, give the agent the input workbook and ask it to produce the anova tool output: 14 rows, Summary and ANOVA tables in a new sheet (with the Gnumeric tool or by formulas), export the range and compare; since upstream compares text exactly, a task that lets the agent use formulas should also accept numerically equal output, but no tolerance is given upstream, so the only cited judge is exact text equality. No screenshot needed | [regression] Final file state: run the regression tool on the input sheet headless, then compare the exported CSV with the __DATA__ block of test/t7200-regression.pl by exact string equality, as upstream does. For a task built from it, give the agent the input workbook and ask it to produce the regression output range A1:G18 in a new sheet (with the Gnumeric tool or by formulas), export the range and compare; since upstream compares text exactly, a task that lets the agent use formulas should also accept numerically equal output, but no tolerance is given upstream, so the only cited judge is exact text equality. No screenshot needed | [descriptive-statistics] Final file state: run the descriptive-statistics tool on the input sheet headless, then compare the exported CSV with the __DATA__ block of test/t7203-descriptive-statistics.pl by exact string equality, as upstream does. For a task built from it, give the agent the input workbook and ask it to produce the descriptive statistics output range A1:B26 in a new sheet (with the Gnumeric tool or by formulas), export the range and compare; since upstream compares text exactly, a task that lets the agent use formulas should also accept numerically equal output, but no tolerance is given upstream, so the only cited judge is exact text equality. No screenshot needed
|
| 86 |
Tools: Gnumeric headless: ssconvert [--export-range=RANGE] --tool-test=TOOL --tool-test=ARG:VALUE ... FILE out.csv with TOOL anova, regression or descriptive-statistics (export range A1:B26) (the command test_tool builds in test/GnumericTest.pm line 947); LibreOffice has Analysis of Variance / Regression / Descriptive Statistics dialogs but no headless switch for them, so Gnumeric ssconvert is the terminal route
|
| 87 |
Companions (not included): COPYING; test/t7201-anova.pl; test/t7200-regression.pl; test/t7203-descriptive-statistics.pl
|
campaign_files/2026-10-gt-browser-tests-2/golang-ical-serialization-input7/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: expected_output_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:** Go golang-ical (ParseCalendar, Serialize(WithNewLineWindows)) or Python icalendar to_ical; a script re-serialises the calendar with CRLF line endings and writes the new .ics
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testdata/serialization/input7.ics`: Re-serialise an RFC 5545 sample calendar with CRLF line endings.
|
| 22 |
Format: iCalendar input and expected output (.ics pair); Go test file
|
| 23 |
Origin: golang-ical serialization test pair (tool_fixture)
|
| 24 |
-
Reference result: expected_output_files
|
| 25 |
-
Reference source: testdata/serialization/expected/input7.ics is the expected re-serialised calendar (calendar_serialization_test.go lines 44-49)
|
| 26 |
Check: Final file state: the agent writes the re-serialised calendar; after unfolding, its content lines must equal those of expected/input7.ics exactly and every line must end in CRLF; fold positions are not judged because the upstream fold width is implementation-specific. No screenshot
|
| 27 |
Tools: Go golang-ical (ParseCalendar, Serialize(WithNewLineWindows)) or Python icalendar to_ical; a script re-serialises the calendar with CRLF line endings and writes the new .ics
|
| 28 |
Companions (not included): calendar_serialization_test.go; testdata/serialization/expected/input7.ics
|
|
|
|
| 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:** Go golang-ical (ParseCalendar, Serialize(WithNewLineWindows)) or Python icalendar to_ical; a script re-serialises the calendar with CRLF line endings and writes the new .ics
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0
|
|
|
|
| 19 |
- `testdata/serialization/input7.ics`: Re-serialise an RFC 5545 sample calendar with CRLF line endings.
|
| 20 |
Format: iCalendar input and expected output (.ics pair); Go test file
|
| 21 |
Origin: golang-ical serialization test pair (tool_fixture)
|
|
|
|
|
|
|
| 22 |
Check: Final file state: the agent writes the re-serialised calendar; after unfolding, its content lines must equal those of expected/input7.ics exactly and every line must end in CRLF; fold positions are not judged because the upstream fold width is implementation-specific. No screenshot
|
| 23 |
Tools: Go golang-ical (ParseCalendar, Serialize(WithNewLineWindows)) or Python icalendar to_ical; a script re-serialises the calendar with CRLF line endings and writes the new .ics
|
| 24 |
Companions (not included): calendar_serialization_test.go; testdata/serialization/expected/input7.ics
|
campaign_files/2026-10-hw-eda-tests-2/github-llvm-circt-test-conversion-exportverilog-lit-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Each file is self-contained. 3 of 3 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 emitted SystemVerilog text as FileCheck patterns. 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 for the agent: write the expected Verilog for the given hw/sv IR, or change the emitter so that it prints the checked text.
|
| 14 |
|
| 15 |
**Licence (SPDX):** Apache-2.0 WITH LLVM-exception
|
|
@@ -21,24 +19,18 @@ Files:
|
|
| 21 |
- `test/Conversion/ExportVerilog/sv-interfaces-modport-ports.mlir`: CIRCT ExportVerilog lit test sv-interfaces-modport-ports: hw/sv dialect interfaces with modports exported as SystemVerilog interface ports.
|
| 22 |
Format: MLIR input with lit RUN line and FileCheck CHECK lines giving the expected SystemVerilog text
|
| 23 |
Origin: hw/sv dialect interfaces with modports exported as SystemVerilog interface ports.
|
| 24 |
-
Reference result: expected emitted SystemVerilog text as FileCheck patterns
|
| 25 |
-
Reference source: CHECK lines in test/Conversion/ExportVerilog/sv-interfaces-modport-ports.mlir, written by the CIRCT authors
|
| 26 |
Check: Task for the agent: write the expected Verilog for the given hw/sv IR, or change the emitter so that it prints the checked text.
|
| 27 |
Companions (not included): LICENSE
|
| 28 |
Dependencies: circt-opt at the pinned commit (the hardware compiler under test); LLVM FileCheck (and lit to run the RUN line)
|
| 29 |
- `test/Conversion/ExportVerilog/port-decl-sharing.mlir`: CIRCT ExportVerilog lit test port-decl-sharing: ExportVerilog sharing of port declarations across ports with the same type and direction.
|
| 30 |
Format: MLIR input with lit RUN line and FileCheck CHECK lines giving the expected SystemVerilog text
|
| 31 |
Origin: ExportVerilog sharing of port declarations across ports with the same type and direction.
|
| 32 |
-
Reference result: expected emitted SystemVerilog text as FileCheck patterns
|
| 33 |
-
Reference source: CHECK lines in test/Conversion/ExportVerilog/port-decl-sharing.mlir, written by the CIRCT authors
|
| 34 |
Check: Task for the agent: write the expected Verilog for the given hw/sv IR, or change the emitter so that it prints the checked text.
|
| 35 |
Companions (not included): LICENSE
|
| 36 |
Dependencies: circt-opt at the pinned commit (the hardware compiler under test); LLVM FileCheck (and lit to run the RUN line)
|
| 37 |
- `test/Conversion/ExportVerilog/max-terms.mlir`: CIRCT ExportVerilog lit test max-terms: ExportVerilog splitting of long expressions under maximumNumberOfTermsPerExpression=4.
|
| 38 |
Format: MLIR input with lit RUN line and FileCheck CHECK lines giving the expected SystemVerilog text
|
| 39 |
Origin: ExportVerilog splitting of long expressions under maximumNumberOfTermsPerExpression=4.
|
| 40 |
-
Reference result: expected emitted SystemVerilog text as FileCheck patterns
|
| 41 |
-
Reference source: CHECK lines in test/Conversion/ExportVerilog/max-terms.mlir, written by the CIRCT authors
|
| 42 |
Check: Task for the agent: write the expected Verilog for the given hw/sv IR, or change the emitter so that it prints the checked text.
|
| 43 |
Companions (not included): LICENSE
|
| 44 |
Dependencies: circt-opt at the pinned commit (the hardware compiler under test); LLVM FileCheck (and lit to run the RUN line)
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Each file is self-contained. 3 of 3 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 for the agent: write the expected Verilog for the given hw/sv IR, or change the emitter so that it prints the checked text.
|
| 12 |
|
| 13 |
**Licence (SPDX):** Apache-2.0 WITH LLVM-exception
|
|
|
|
| 19 |
- `test/Conversion/ExportVerilog/sv-interfaces-modport-ports.mlir`: CIRCT ExportVerilog lit test sv-interfaces-modport-ports: hw/sv dialect interfaces with modports exported as SystemVerilog interface ports.
|
| 20 |
Format: MLIR input with lit RUN line and FileCheck CHECK lines giving the expected SystemVerilog text
|
| 21 |
Origin: hw/sv dialect interfaces with modports exported as SystemVerilog interface ports.
|
|
|
|
|
|
|
| 22 |
Check: Task for the agent: write the expected Verilog for the given hw/sv IR, or change the emitter so that it prints the checked text.
|
| 23 |
Companions (not included): LICENSE
|
| 24 |
Dependencies: circt-opt at the pinned commit (the hardware compiler under test); LLVM FileCheck (and lit to run the RUN line)
|
| 25 |
- `test/Conversion/ExportVerilog/port-decl-sharing.mlir`: CIRCT ExportVerilog lit test port-decl-sharing: ExportVerilog sharing of port declarations across ports with the same type and direction.
|
| 26 |
Format: MLIR input with lit RUN line and FileCheck CHECK lines giving the expected SystemVerilog text
|
| 27 |
Origin: ExportVerilog sharing of port declarations across ports with the same type and direction.
|
|
|
|
|
|
|
| 28 |
Check: Task for the agent: write the expected Verilog for the given hw/sv IR, or change the emitter so that it prints the checked text.
|
| 29 |
Companions (not included): LICENSE
|
| 30 |
Dependencies: circt-opt at the pinned commit (the hardware compiler under test); LLVM FileCheck (and lit to run the RUN line)
|
| 31 |
- `test/Conversion/ExportVerilog/max-terms.mlir`: CIRCT ExportVerilog lit test max-terms: ExportVerilog splitting of long expressions under maximumNumberOfTermsPerExpression=4.
|
| 32 |
Format: MLIR input with lit RUN line and FileCheck CHECK lines giving the expected SystemVerilog text
|
| 33 |
Origin: ExportVerilog splitting of long expressions under maximumNumberOfTermsPerExpression=4.
|
|
|
|
|
|
|
| 34 |
Check: Task for the agent: write the expected Verilog for the given hw/sv IR, or change the emitter so that it prints the checked text.
|
| 35 |
Companions (not included): LICENSE
|
| 36 |
Dependencies: circt-opt at the pinned commit (the hardware compiler under test); LLVM FileCheck (and lit to run the RUN line)
|
campaign_files/2026-10-hw-eda-tests-2/github-nickg-nvc-test-regress-regression-suite-with-gold-files/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Each file is self-contained. 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 simulator output lines (report and textio output with simulation time stamps). 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:** Tools are named in the check written per file in the notes.
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-3.0-or-later
|
|
@@ -21,32 +19,24 @@ Files:
|
|
| 21 |
- `test/regress/fact.vhd`: Nvc regression test fact: VHDL simulation with gold output (factorial loop that overflows INTEGER; expected runtime error with source excerpt).
|
| 22 |
Format: VHDL source file plus gold output text (test/regress/<name>.vhd, test/regress/gold/<name>.txt)
|
| 23 |
Origin: factorial loop that overflows INTEGER; expected runtime error with source excerpt. Task for the agent: predict or produce the exact simulation output of the VHDL design, or fix or write a VHDL design that produces the gold output.
|
| 24 |
-
Reference result: expected simulator output lines (report and textio output with simulation time stamps)
|
| 25 |
-
Reference source: test/regress/gold/fact.txt, kept in the nvc repository by its authors as the expected output
|
| 26 |
Check: Analyse, elaborate and run test/regress/fact.vhd with nvc (top entity fact, standard as the testlist flags select), capture stdout and stderr, and pass when every line of gold/fact.txt is found in order as a substring of the output and the exit status matches the flag (an error exit is required); this is the rule of test/run_regr.c. The gold file is the expected simulator output kept by the nvc authors.
|
| 27 |
Companions (not included): COPYING
|
| 28 |
Dependencies: nvc at the pinned commit (the VHDL simulator under test) or another VHDL simulator whose report format matches the gold lines; test/regress/testlist.txt; test/run_regr.c
|
| 29 |
- `test/regress/image1.vhd`: Nvc regression test image1: VHDL simulation with gold output ('image attribute on integers, reals, enumerations and physical types).
|
| 30 |
Format: VHDL source file plus gold output text (test/regress/<name>.vhd, test/regress/gold/<name>.txt)
|
| 31 |
Origin: 'image attribute on integers, reals, enumerations and physical types. Task for the agent: predict or produce the exact simulation output of the VHDL design, or fix or write a VHDL design that produces the gold output.
|
| 32 |
-
Reference result: expected simulator output lines (report and textio output with simulation time stamps)
|
| 33 |
-
Reference source: test/regress/gold/image1.txt, kept in the nvc repository by its authors as the expected output
|
| 34 |
Check: Analyse, elaborate and run test/regress/image1.vhd with nvc (top entity image1, standard as the testlist flags select), capture stdout and stderr, and pass when every line of gold/image1.txt is found in order as a substring of the output and the exit status matches the flag (a clean exit is required); this is the rule of test/run_regr.c. The gold file is the expected simulator output kept by the nvc authors.
|
| 35 |
Companions (not included): COPYING
|
| 36 |
Dependencies: nvc at the pinned commit (the VHDL simulator under test) or another VHDL simulator whose report format matches the gold lines; test/regress/testlist.txt; test/run_regr.c
|
| 37 |
- `test/regress/range1.vhd`: Nvc regression test range1: VHDL simulation with gold output (ascending and descending slice ranges with strided assignment over simulation time).
|
| 38 |
Format: VHDL source file plus gold output text (test/regress/<name>.vhd, test/regress/gold/<name>.txt)
|
| 39 |
Origin: ascending and descending slice ranges with strided assignment over simulation time. Task for the agent: predict or produce the exact simulation output of the VHDL design, or fix or write a VHDL design that produces the gold output.
|
| 40 |
-
Reference result: expected simulator output lines (report and textio output with simulation time stamps)
|
| 41 |
-
Reference source: test/regress/gold/range1.txt, kept in the nvc repository by its authors as the expected output
|
| 42 |
Check: Analyse, elaborate and run test/regress/range1.vhd with nvc (top entity range1, standard as the testlist flags select), capture stdout and stderr, and pass when every line of gold/range1.txt is found in order as a substring of the output and the exit status matches the flag (a clean exit is required); this is the rule of test/run_regr.c. The gold file is the expected simulator output kept by the nvc authors.
|
| 43 |
Companions (not included): COPYING
|
| 44 |
Dependencies: nvc at the pinned commit (the VHDL simulator under test) or another VHDL simulator whose report format matches the gold lines; test/regress/testlist.txt; test/run_regr.c
|
| 45 |
- `test/regress/textio1.vhd`: Nvc regression test textio1: VHDL simulation with gold output (std.textio write and writeline with justification and field widths).
|
| 46 |
Format: VHDL source file plus gold output text (test/regress/<name>.vhd, test/regress/gold/<name>.txt)
|
| 47 |
Origin: std.textio write and writeline with justification and field widths. Task for the agent: predict or produce the exact simulation output of the VHDL design, or fix or write a VHDL design that produces the gold output.
|
| 48 |
-
Reference result: expected simulator output lines (report and textio output with simulation time stamps)
|
| 49 |
-
Reference source: test/regress/gold/textio1.txt, kept in the nvc repository by its authors as the expected output
|
| 50 |
Check: Analyse, elaborate and run test/regress/textio1.vhd with nvc (top entity textio1, standard as the testlist flags select), capture stdout and stderr, and pass when every line of gold/textio1.txt is found in order as a substring of the output and the exit status matches the flag (a clean exit is required); this is the rule of test/run_regr.c. The gold file is the expected simulator output kept by the nvc authors.
|
| 51 |
Companions (not included): COPYING
|
| 52 |
Dependencies: nvc at the pinned commit (the VHDL simulator under test) or another VHDL simulator whose report format matches the gold lines; test/regress/testlist.txt; test/run_regr.c
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Each file is self-contained. 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:** Tools are named in the check written per file in the notes.
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-3.0-or-later
|
|
|
|
| 19 |
- `test/regress/fact.vhd`: Nvc regression test fact: VHDL simulation with gold output (factorial loop that overflows INTEGER; expected runtime error with source excerpt).
|
| 20 |
Format: VHDL source file plus gold output text (test/regress/<name>.vhd, test/regress/gold/<name>.txt)
|
| 21 |
Origin: factorial loop that overflows INTEGER; expected runtime error with source excerpt. Task for the agent: predict or produce the exact simulation output of the VHDL design, or fix or write a VHDL design that produces the gold output.
|
|
|
|
|
|
|
| 22 |
Check: Analyse, elaborate and run test/regress/fact.vhd with nvc (top entity fact, standard as the testlist flags select), capture stdout and stderr, and pass when every line of gold/fact.txt is found in order as a substring of the output and the exit status matches the flag (an error exit is required); this is the rule of test/run_regr.c. The gold file is the expected simulator output kept by the nvc authors.
|
| 23 |
Companions (not included): COPYING
|
| 24 |
Dependencies: nvc at the pinned commit (the VHDL simulator under test) or another VHDL simulator whose report format matches the gold lines; test/regress/testlist.txt; test/run_regr.c
|
| 25 |
- `test/regress/image1.vhd`: Nvc regression test image1: VHDL simulation with gold output ('image attribute on integers, reals, enumerations and physical types).
|
| 26 |
Format: VHDL source file plus gold output text (test/regress/<name>.vhd, test/regress/gold/<name>.txt)
|
| 27 |
Origin: 'image attribute on integers, reals, enumerations and physical types. Task for the agent: predict or produce the exact simulation output of the VHDL design, or fix or write a VHDL design that produces the gold output.
|
|
|
|
|
|
|
| 28 |
Check: Analyse, elaborate and run test/regress/image1.vhd with nvc (top entity image1, standard as the testlist flags select), capture stdout and stderr, and pass when every line of gold/image1.txt is found in order as a substring of the output and the exit status matches the flag (a clean exit is required); this is the rule of test/run_regr.c. The gold file is the expected simulator output kept by the nvc authors.
|
| 29 |
Companions (not included): COPYING
|
| 30 |
Dependencies: nvc at the pinned commit (the VHDL simulator under test) or another VHDL simulator whose report format matches the gold lines; test/regress/testlist.txt; test/run_regr.c
|
| 31 |
- `test/regress/range1.vhd`: Nvc regression test range1: VHDL simulation with gold output (ascending and descending slice ranges with strided assignment over simulation time).
|
| 32 |
Format: VHDL source file plus gold output text (test/regress/<name>.vhd, test/regress/gold/<name>.txt)
|
| 33 |
Origin: ascending and descending slice ranges with strided assignment over simulation time. Task for the agent: predict or produce the exact simulation output of the VHDL design, or fix or write a VHDL design that produces the gold output.
|
|
|
|
|
|
|
| 34 |
Check: Analyse, elaborate and run test/regress/range1.vhd with nvc (top entity range1, standard as the testlist flags select), capture stdout and stderr, and pass when every line of gold/range1.txt is found in order as a substring of the output and the exit status matches the flag (a clean exit is required); this is the rule of test/run_regr.c. The gold file is the expected simulator output kept by the nvc authors.
|
| 35 |
Companions (not included): COPYING
|
| 36 |
Dependencies: nvc at the pinned commit (the VHDL simulator under test) or another VHDL simulator whose report format matches the gold lines; test/regress/testlist.txt; test/run_regr.c
|
| 37 |
- `test/regress/textio1.vhd`: Nvc regression test textio1: VHDL simulation with gold output (std.textio write and writeline with justification and field widths).
|
| 38 |
Format: VHDL source file plus gold output text (test/regress/<name>.vhd, test/regress/gold/<name>.txt)
|
| 39 |
Origin: std.textio write and writeline with justification and field widths. Task for the agent: predict or produce the exact simulation output of the VHDL design, or fix or write a VHDL design that produces the gold output.
|
|
|
|
|
|
|
| 40 |
Check: Analyse, elaborate and run test/regress/textio1.vhd with nvc (top entity textio1, standard as the testlist flags select), capture stdout and stderr, and pass when every line of gold/textio1.txt is found in order as a substring of the output and the exit status matches the flag (a clean exit is required); this is the rule of test/run_regr.c. The gold file is the expected simulator output kept by the nvc authors.
|
| 41 |
Companions (not included): COPYING
|
| 42 |
Dependencies: nvc at the pinned commit (the VHDL simulator under test) or another VHDL simulator whose report format matches the gold lines; test/regress/testlist.txt; test/run_regr.c
|
campaign_files/2026-10-hw-eda-tests-2/github-zachjs-sv2v-test-core-regression-suite/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: Reference Verilog-2005 module behaviourally equivalent to the SystemVerilog input (checked by simulation trace equality). 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 harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written interface_modport.v. the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written struct_array.v. the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written union.v. the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written stream_exhaust.v.
|
| 14 |
|
| 15 |
**Licence (SPDX):** BSD-3-Clause
|
|
@@ -21,32 +19,24 @@ Files:
|
|
| 21 |
- `test/core/interface_modport.sv`: sv2v regression test interface_modport: SystemVerilog to Verilog-2005 conversion (interface with modport ports converted to flattened Verilog ports).
|
| 22 |
Format: SystemVerilog source plus hand-written reference Verilog-2005 and a Verilog testbench (test/core/<name>.sv, .v, _tb.v)
|
| 23 |
Origin: SystemVerilog interface with modports, nested instance and port binding to plain Verilog. Task for the agent: rewrite the SystemVerilog module in Verilog-2005 (or implement the conversion) so that it simulates identically to the reference under the given testbench.
|
| 24 |
-
Reference result: reference Verilog-2005 module behaviourally equivalent to the SystemVerilog input (checked by simulation trace equality)
|
| 25 |
-
Reference source: test/core/interface_modport.v, written by hand by the sv2v authors (test/README.md lines 18-20)
|
| 26 |
Check: the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written interface_modport.v.
|
| 27 |
Companions (not included): test/lib/functions.sh; test/lib/runner.sh; test/lib/discover.sh; test/lib/tb_dumper.v; test/lib/clean_vcd.py; test/lib/empty.v; test/core/run.sh; test/README.md; LICENSE
|
| 28 |
Dependencies: sv2v at the pinned commit (Haskell, the tool under test); iverilog (Icarus Verilog); shunit2; bash; python3 (clean_vcd.py imports only sys and collections)
|
| 29 |
- `test/core/struct_array.sv`: sv2v regression test struct_array: SystemVerilog to Verilog-2005 conversion (packed struct arrays).
|
| 30 |
Format: SystemVerilog source plus hand-written reference Verilog-2005 and a Verilog testbench (test/core/<name>.sv, .v, _tb.v)
|
| 31 |
Origin: packed struct array indexing converted to Verilog bit slices. Task for the agent: rewrite the SystemVerilog module in Verilog-2005 (or implement the conversion) so that it simulates identically to the reference under the given testbench.
|
| 32 |
-
Reference result: reference Verilog-2005 module behaviourally equivalent to the SystemVerilog input (checked by simulation trace equality)
|
| 33 |
-
Reference source: test/core/struct_array.v, written by hand by the sv2v authors (test/README.md lines 18-20)
|
| 34 |
Check: the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written struct_array.v.
|
| 35 |
Companions (not included): test/lib/functions.sh; test/lib/runner.sh; test/lib/discover.sh; test/lib/tb_dumper.v; test/lib/clean_vcd.py; test/lib/empty.v; test/core/run.sh; test/README.md; LICENSE
|
| 36 |
Dependencies: sv2v at the pinned commit (Haskell, the tool under test); iverilog (Icarus Verilog); shunit2; bash; python3 (clean_vcd.py imports only sys and collections)
|
| 37 |
- `test/core/union.sv`: sv2v regression test union: SystemVerilog to Verilog-2005 conversion (packed unions).
|
| 38 |
Format: SystemVerilog source plus hand-written reference Verilog-2005 and a Verilog testbench (test/core/<name>.sv, .v, _tb.v)
|
| 39 |
Origin: packed unions with member overlay and nested struct members. Task for the agent: rewrite the SystemVerilog module in Verilog-2005 (or implement the conversion) so that it simulates identically to the reference under the given testbench.
|
| 40 |
-
Reference result: reference Verilog-2005 module behaviourally equivalent to the SystemVerilog input (checked by simulation trace equality)
|
| 41 |
-
Reference source: test/core/union.v, written by hand by the sv2v authors (test/README.md lines 18-20)
|
| 42 |
Check: the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written union.v.
|
| 43 |
Companions (not included): test/lib/functions.sh; test/lib/runner.sh; test/lib/discover.sh; test/lib/tb_dumper.v; test/lib/clean_vcd.py; test/lib/empty.v; test/core/run.sh; test/README.md; LICENSE
|
| 44 |
Dependencies: sv2v at the pinned commit (Haskell, the tool under test); iverilog (Icarus Verilog); shunit2; bash; python3 (clean_vcd.py imports only sys and collections)
|
| 45 |
- `test/core/stream_exhaust.sv`: sv2v regression test stream_exhaust: SystemVerilog to Verilog-2005 conversion (streaming concatenation exhaustive widths).
|
| 46 |
Format: SystemVerilog source plus hand-written reference Verilog-2005 and a Verilog testbench (test/core/<name>.sv, .v, _tb.v)
|
| 47 |
Origin: streaming operators {<<{}} and {>>{}} over many slice widths. Task for the agent: rewrite the SystemVerilog module in Verilog-2005 (or implement the conversion) so that it simulates identically to the reference under the given testbench.
|
| 48 |
-
Reference result: reference Verilog-2005 module behaviourally equivalent to the SystemVerilog input (checked by simulation trace equality)
|
| 49 |
-
Reference source: test/core/stream_exhaust.v, written by hand by the sv2v authors (test/README.md lines 18-20)
|
| 50 |
Check: the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written stream_exhaust.v.
|
| 51 |
Companions (not included): test/lib/functions.sh; test/lib/runner.sh; test/lib/discover.sh; test/lib/tb_dumper.v; test/lib/clean_vcd.py; test/lib/empty.v; test/core/run.sh; test/README.md; LICENSE
|
| 52 |
Dependencies: sv2v at the pinned commit (Haskell, the tool under test); iverilog (Icarus Verilog); shunit2; bash; python3 (clean_vcd.py imports only sys and collections)
|
|
|
|
| 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: The harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written interface_modport.v. the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written struct_array.v. the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written union.v. the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written stream_exhaust.v.
|
| 12 |
|
| 13 |
**Licence (SPDX):** BSD-3-Clause
|
|
|
|
| 19 |
- `test/core/interface_modport.sv`: sv2v regression test interface_modport: SystemVerilog to Verilog-2005 conversion (interface with modport ports converted to flattened Verilog ports).
|
| 20 |
Format: SystemVerilog source plus hand-written reference Verilog-2005 and a Verilog testbench (test/core/<name>.sv, .v, _tb.v)
|
| 21 |
Origin: SystemVerilog interface with modports, nested instance and port binding to plain Verilog. Task for the agent: rewrite the SystemVerilog module in Verilog-2005 (or implement the conversion) so that it simulates identically to the reference under the given testbench.
|
|
|
|
|
|
|
| 22 |
Check: the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written interface_modport.v.
|
| 23 |
Companions (not included): test/lib/functions.sh; test/lib/runner.sh; test/lib/discover.sh; test/lib/tb_dumper.v; test/lib/clean_vcd.py; test/lib/empty.v; test/core/run.sh; test/README.md; LICENSE
|
| 24 |
Dependencies: sv2v at the pinned commit (Haskell, the tool under test); iverilog (Icarus Verilog); shunit2; bash; python3 (clean_vcd.py imports only sys and collections)
|
| 25 |
- `test/core/struct_array.sv`: sv2v regression test struct_array: SystemVerilog to Verilog-2005 conversion (packed struct arrays).
|
| 26 |
Format: SystemVerilog source plus hand-written reference Verilog-2005 and a Verilog testbench (test/core/<name>.sv, .v, _tb.v)
|
| 27 |
Origin: packed struct array indexing converted to Verilog bit slices. Task for the agent: rewrite the SystemVerilog module in Verilog-2005 (or implement the conversion) so that it simulates identically to the reference under the given testbench.
|
|
|
|
|
|
|
| 28 |
Check: the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written struct_array.v.
|
| 29 |
Companions (not included): test/lib/functions.sh; test/lib/runner.sh; test/lib/discover.sh; test/lib/tb_dumper.v; test/lib/clean_vcd.py; test/lib/empty.v; test/core/run.sh; test/README.md; LICENSE
|
| 30 |
Dependencies: sv2v at the pinned commit (Haskell, the tool under test); iverilog (Icarus Verilog); shunit2; bash; python3 (clean_vcd.py imports only sys and collections)
|
| 31 |
- `test/core/union.sv`: sv2v regression test union: SystemVerilog to Verilog-2005 conversion (packed unions).
|
| 32 |
Format: SystemVerilog source plus hand-written reference Verilog-2005 and a Verilog testbench (test/core/<name>.sv, .v, _tb.v)
|
| 33 |
Origin: packed unions with member overlay and nested struct members. Task for the agent: rewrite the SystemVerilog module in Verilog-2005 (or implement the conversion) so that it simulates identically to the reference under the given testbench.
|
|
|
|
|
|
|
| 34 |
Check: the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written union.v.
|
| 35 |
Companions (not included): test/lib/functions.sh; test/lib/runner.sh; test/lib/discover.sh; test/lib/tb_dumper.v; test/lib/clean_vcd.py; test/lib/empty.v; test/core/run.sh; test/README.md; LICENSE
|
| 36 |
Dependencies: sv2v at the pinned commit (Haskell, the tool under test); iverilog (Icarus Verilog); shunit2; bash; python3 (clean_vcd.py imports only sys and collections)
|
| 37 |
- `test/core/stream_exhaust.sv`: sv2v regression test stream_exhaust: SystemVerilog to Verilog-2005 conversion (streaming concatenation exhaustive widths).
|
| 38 |
Format: SystemVerilog source plus hand-written reference Verilog-2005 and a Verilog testbench (test/core/<name>.sv, .v, _tb.v)
|
| 39 |
Origin: streaming operators {<<{}} and {>>{}} over many slice widths. Task for the agent: rewrite the SystemVerilog module in Verilog-2005 (or implement the conversion) so that it simulates identically to the reference under the given testbench.
|
|
|
|
|
|
|
| 40 |
Check: the harness is test/core/run.sh sourcing test/lib/runner.sh (shunit2). Reference behaviour comes from the hand-written stream_exhaust.v.
|
| 41 |
Companions (not included): test/lib/functions.sh; test/lib/runner.sh; test/lib/discover.sh; test/lib/tb_dumper.v; test/lib/clean_vcd.py; test/lib/empty.v; test/core/run.sh; test/README.md; LICENSE
|
| 42 |
Dependencies: sv2v at the pinned commit (Haskell, the tool under test); iverilog (Icarus Verilog); shunit2; bash; python3 (clean_vcd.py imports only sys and collections)
|
campaign_files/2026-10-hw-eda-tests-2/gpx-github-markwal-gpx-master-at-commit-28f3460/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether each file needs other upstream files is not stated. 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: translator_output_x3g_and_decompiled_listing. 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:** GPX command line translator (headless): `gpx -I -p -m r2x lint.gcode lint.x3g > lint.log 2>&1` (and with -g for the -g files), then `python scripts/s3g-decompiler.py lint.x3g > lint.txt`; G-code is a plain text file and X3G a binary command stream; GPX command line translator (headless): `gpx -I -p -m r2x issue13.gcode issue13.x3g > issue13.log 2>&1` (and with -g for the -g files), then `python scripts/s3g-decompiler.py issue13.x3g > issue13.txt`; G-code is a plain text file and X3G a binary command stream
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-2.0-or-later
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `src/gpx/tests/lint.gcode`: GPX lint program (a 3D printer G-code file exercising most supported codes: tool changes, M70 messages, M73 progress, G92, G10 offsets, nested comment) translated for a MakerBot Replicator 2X: produce the X3G command stream, its decompiled listing and the warnings log, in both default and -g (Gcode build progress) mode.
|
| 22 |
Format: RepRap/MakerBot G-code text (.gcode); reference outputs are X3G binary command streams (.x3g), their decompiled text listings (.txt) and the translator warnings (.log)
|
| 23 |
Origin: translator regression test from the GPX repository
|
| 24 |
-
Reference result: translator_output_x3g_and_decompiled_listing
|
| 25 |
-
Reference source: src/gpx/tests/lint.x3g, lint.txt and lint.log (and the -g files): the reference outputs of GPX for this program, compared by `make test` (src/gpx/Makefile.am lines 26 to 37); the log warns of a nested comment at line 27 and of G92 emulation at line 123
|
| 26 |
Check: Task: given the G-code program and the machine profile r2x, produce what the translator emits (the X3G stream as its decompiled listing lint.txt, and the warnings lint.log; the -g pair for build-progress mode). Judge: run GPX and the decompiler as the Makefile does, or take the agent output, and compare each file with its reference with `diff -b` as `make test` does (the X3G binaries must match byte for byte). values traced by hand.
|
| 27 |
Tools: GPX command line translator (headless): `gpx -I -p -m r2x lint.gcode lint.x3g > lint.log 2>&1` (and with -g for the -g files), then `python scripts/s3g-decompiler.py lint.x3g > lint.txt`; G-code is a plain text file and X3G a binary command stream
|
| 28 |
Companions (not included): src/gpx/tests/lint.x3g; src/gpx/tests/lint.txt; src/gpx/tests/lint.log; src/gpx/tests/lint-g.x3g; src/gpx/tests/lint-g.txt; src/gpx/tests/lint-g.log; scripts/s3g-decompiler.py; src/gpx/Makefile.am; configure.ac; LICENSE
|
|
@@ -30,8 +26,6 @@ Files:
|
|
| 30 |
- `src/gpx/tests/issue13.gcode`: GPX regression for issue 13 (a short Slic3r-style 3D print with relative extrusion M83 and M73 progress) translated for a MakerBot Replicator 2X: produce the X3G command stream and its decompiled listing, in default and -g mode.
|
| 31 |
Format: RepRap/MakerBot G-code text (.gcode); reference outputs are X3G binary command streams (.x3g), their decompiled text listings (.txt) and the translator warnings (.log)
|
| 32 |
Origin: translator regression test from the GPX repository
|
| 33 |
-
Reference result: translator_output_x3g_and_decompiled_listing
|
| 34 |
-
Reference source: src/gpx/tests/issue13.x3g, issue13.txt and issue13.log (and the -g files): the reference outputs of GPX for this program, compared by `make test` (src/gpx/Makefile.am lines 26 to 37); the expected logs are empty (no warnings)
|
| 35 |
Check: Task: given the G-code program and the machine profile r2x, produce what the translator emits (the X3G stream as its decompiled listing issue13.txt, and the warnings issue13.log; the -g pair for build-progress mode). Judge: run GPX and the decompiler as the Makefile does, or take the agent output, and compare each file with its reference with `diff -b` as `make test` does (the X3G binaries must match byte for byte). values traced by hand.
|
| 36 |
Tools: GPX command line translator (headless): `gpx -I -p -m r2x issue13.gcode issue13.x3g > issue13.log 2>&1` (and with -g for the -g files), then `python scripts/s3g-decompiler.py issue13.x3g > issue13.txt`; G-code is a plain text file and X3G a binary command stream
|
| 37 |
Companions (not included): src/gpx/tests/issue13.x3g; src/gpx/tests/issue13.txt; src/gpx/tests/issue13.log; src/gpx/tests/issue13-g.x3g; src/gpx/tests/issue13-g.txt; src/gpx/tests/issue13-g.log; scripts/s3g-decompiler.py; src/gpx/Makefile.am; configure.ac; LICENSE
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether each file needs other upstream files is not stated. 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:** GPX command line translator (headless): `gpx -I -p -m r2x lint.gcode lint.x3g > lint.log 2>&1` (and with -g for the -g files), then `python scripts/s3g-decompiler.py lint.x3g > lint.txt`; G-code is a plain text file and X3G a binary command stream; GPX command line translator (headless): `gpx -I -p -m r2x issue13.gcode issue13.x3g > issue13.log 2>&1` (and with -g for the -g files), then `python scripts/s3g-decompiler.py issue13.x3g > issue13.txt`; G-code is a plain text file and X3G a binary command stream
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-2.0-or-later
|
|
|
|
| 19 |
- `src/gpx/tests/lint.gcode`: GPX lint program (a 3D printer G-code file exercising most supported codes: tool changes, M70 messages, M73 progress, G92, G10 offsets, nested comment) translated for a MakerBot Replicator 2X: produce the X3G command stream, its decompiled listing and the warnings log, in both default and -g (Gcode build progress) mode.
|
| 20 |
Format: RepRap/MakerBot G-code text (.gcode); reference outputs are X3G binary command streams (.x3g), their decompiled text listings (.txt) and the translator warnings (.log)
|
| 21 |
Origin: translator regression test from the GPX repository
|
|
|
|
|
|
|
| 22 |
Check: Task: given the G-code program and the machine profile r2x, produce what the translator emits (the X3G stream as its decompiled listing lint.txt, and the warnings lint.log; the -g pair for build-progress mode). Judge: run GPX and the decompiler as the Makefile does, or take the agent output, and compare each file with its reference with `diff -b` as `make test` does (the X3G binaries must match byte for byte). values traced by hand.
|
| 23 |
Tools: GPX command line translator (headless): `gpx -I -p -m r2x lint.gcode lint.x3g > lint.log 2>&1` (and with -g for the -g files), then `python scripts/s3g-decompiler.py lint.x3g > lint.txt`; G-code is a plain text file and X3G a binary command stream
|
| 24 |
Companions (not included): src/gpx/tests/lint.x3g; src/gpx/tests/lint.txt; src/gpx/tests/lint.log; src/gpx/tests/lint-g.x3g; src/gpx/tests/lint-g.txt; src/gpx/tests/lint-g.log; scripts/s3g-decompiler.py; src/gpx/Makefile.am; configure.ac; LICENSE
|
|
|
|
| 26 |
- `src/gpx/tests/issue13.gcode`: GPX regression for issue 13 (a short Slic3r-style 3D print with relative extrusion M83 and M73 progress) translated for a MakerBot Replicator 2X: produce the X3G command stream and its decompiled listing, in default and -g mode.
|
| 27 |
Format: RepRap/MakerBot G-code text (.gcode); reference outputs are X3G binary command streams (.x3g), their decompiled text listings (.txt) and the translator warnings (.log)
|
| 28 |
Origin: translator regression test from the GPX repository
|
|
|
|
|
|
|
| 29 |
Check: Task: given the G-code program and the machine profile r2x, produce what the translator emits (the X3G stream as its decompiled listing issue13.txt, and the warnings issue13.log; the -g pair for build-progress mode). Judge: run GPX and the decompiler as the Makefile does, or take the agent output, and compare each file with its reference with `diff -b` as `make test` does (the X3G binaries must match byte for byte). values traced by hand.
|
| 30 |
Tools: GPX command line translator (headless): `gpx -I -p -m r2x issue13.gcode issue13.x3g > issue13.log 2>&1` (and with -g for the -g files), then `python scripts/s3g-decompiler.py issue13.x3g > issue13.txt`; G-code is a plain text file and X3G a binary command stream
|
| 31 |
Companions (not included): src/gpx/tests/issue13.x3g; src/gpx/tests/issue13.txt; src/gpx/tests/issue13.log; src/gpx/tests/issue13-g.x3g; src/gpx/tests/issue13-g.txt; src/gpx/tests/issue13-g.log; scripts/s3g-decompiler.py; src/gpx/Makefile.am; configure.ac; LICENSE
|
campaign_files/2026-10-m-issue-trackers-2/gnu-help-gnu-emacs/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 |
- `m209-05/2019-03`: Emacs or mutt ? (10 messages, 2019-03-10 to 2019-03-13).
|
| 22 |
Format: GNU mbox month archive (lists.gnu.org/archive/mbox), plain mbox text, not compressed: full headers (From with plain address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 23 |
Origin: Real list traffic in a closed past month of the list's archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer and is delivered whole.
|
| 24 |
-
Reference result: facts computed from the thread headers
|
| 25 |
-
Reference source: Message-ID, In-Reply-To, References, From and Date headers of the messages in the thread, read from the pinned month file.
|
| 26 |
Check: Exact match against values computed from the pinned month file: parse it as mbox, drop repeated copies of a Message-ID already seen (first copy kept), take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC (a Date header without zone is read as UTC) and compare sender names. Message-IDs are compared after removing angle brackets and double quotes. People are counted by person: From entries with the same address, or the same name after removing accents and letter case, are one person (the names in scale are the first spelling of each). This archive is a plain (uncompressed) mbox and keeps senders' addresses unobfuscated. One sender (tomas@tuxteam.de) gives no display name; that person is named by address. The first-reply interval is the exact difference in whole seconds between the Date headers of the root and the earliest reply, converted to UTC; Date headers have one-second resolution, so no rounding is involved. Deterministic. The program was checked on 2 threads of this source by a second, independent parser (splits the raw text on mbox From lines and reads headers with regular expressions, no mailbox or email module): the chosen thread (also read message by message) and 'autoload seems inconsistent' (7 messages, root <87pnqtxt9y.fsf@mail.de>); message count, last message time, first-reply seconds and the file's distinct message count agreed on both.
|
| 27 |
Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 19 |
- `m209-05/2019-03`: Emacs or mutt ? (10 messages, 2019-03-10 to 2019-03-13).
|
| 20 |
Format: GNU mbox month archive (lists.gnu.org/archive/mbox), plain mbox text, not compressed: full headers (From with plain address and name, Date, Subject, Message-ID, In-Reply-To, References) and plain-text bodies. Cut the thread by root Message-ID through the In-Reply-To closure (last References entry when In-Reply-To is missing).
|
| 21 |
Origin: Real list traffic in a closed past month of the list's archive. The unit is one thread, cut out of the month file by its root Message-ID; the month file is the pinned pointer and is delivered whole.
|
|
|
|
|
|
|
| 22 |
Check: Exact match against values computed from the pinned month file: parse it as mbox, drop repeated copies of a Message-ID already seen (first copy kept), take the root Message-ID, collect every message whose In-Reply-To (or last References entry when In-Reply-To is missing) chains back to it, then count, take dates in UTC (a Date header without zone is read as UTC) and compare sender names. Message-IDs are compared after removing angle brackets and double quotes. People are counted by person: From entries with the same address, or the same name after removing accents and letter case, are one person (the names in scale are the first spelling of each). This archive is a plain (uncompressed) mbox and keeps senders' addresses unobfuscated. One sender (tomas@tuxteam.de) gives no display name; that person is named by address. The first-reply interval is the exact difference in whole seconds between the Date headers of the root and the earliest reply, converted to UTC; Date headers have one-second resolution, so no rounding is involved. Deterministic. The program was checked on 2 threads of this source by a second, independent parser (splits the raw text on mbox From lines and reads headers with regular expressions, no mailbox or email module): the chosen thread (also read message by message) and 'autoload seems inconsistent' (7 messages, root <87pnqtxt9y.fsf@mail.de>); message count, last message time, first-reply seconds and the file's distinct message count agreed on both.
|
| 23 |
Tools: Read the archive as mbox with Python's mailbox and email modules (or mutt -f / notmuch on the decompressed file); rebuild the thread from Message-ID, In-Reply-To and References headers.
|
campaign_files/2026-10-m-issue-trackers-2/gnupg-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. 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-11/2019-March.txt`: Several GnuPG instances, with their corresponding agents (5 messages, 2019-03-10 to 2019-03-12).
|
| 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'.
|
| 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: 'Identifying one of multiple authentication subkeys' (22 messages by headers; 4 under 'Please start a new thread' linked by In-Reply-To).
|
| 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-11/2019-March.txt`: Several GnuPG instances, with their corresponding agents (5 messages, 2019-03-10 to 2019-03-12).
|
| 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'.
|
| 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: 'Identifying one of multiple authentication subkeys' (22 messages by headers; 4 under 'Please start a new thread' linked by In-Reply-To).
|
| 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/go-gerrit-changes/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 change's own review timeline (status, submit time and submitter, patch sets, votes, reviewers added or removed, review comments). 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:** curl the Gerrit REST API (GET https://go-review.googlesource.com/changes/{number}/detail), strip the first line ")]}'" and read the JSON with jq or Python json; the git-review CLI and Gerrit's ssh 'gerrit query --format=JSON --all-approvals --comments' reach the same data where ssh access is open
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `changes/675596/detail.json`: Go change 675596: internal/pkgbits: explain the rationale for reference tables.
|
| 22 |
Format: Gerrit REST API ChangeInfo JSON from the /detail endpoint, preceded by the anti-XSSI line ")]}'": status, created, updated, submitted, submitter, owner, labels with every vote (DETAILED_LABELS), messages (author, real_author, date, tag, _revision_number, message text) and reviewer_updates (updated, updated_by, reviewer, state REVIEWER/CC/REMOVED). Patch-set uploads are messages tagged autogenerated:gerrit:newPatchSet; votes appear in message text as 'Patch Set N: Label+V' and in labels.*.all. The endpoint returns all messages and reviewer updates of the change, so the record is complete.
|
| 23 |
Origin: Live Gerrit REST interface of a closed (merged) code review change, collected as a NOASSERTION pointer row under spec general rule 4: the detail JSON was fetched twice apart and was byte-identical. Unit file kept only outside the repository for checking and then deleted.
|
| 24 |
-
Reference result: facts computed from the change's own review timeline (status, submit time and submitter, patch sets, votes, reviewers added or removed, review comments)
|
| 25 |
-
Reference source: The pinned response: changes/675596/detail.json.
|
| 26 |
Check: Exact match against values read from the pinned JSON: status, submitted and submitter; reviewer_updates entries (reviewer, state, updated_by, updated); messages tagged autogenerated:gerrit:newPatchSet (patch-set count, _revision_number); votes from labels.*.all (value, _account_id) and from message first lines 'Patch Set N: Label+V'. A human review comment is a message whose author is not a bot or service account, whose tag does not start with 'autogenerated:', and whose text has content beyond the 'Patch Set N: votes' first line or names inline comments '(N comments)'. Bot and service accounts excluded from the comment count: Gopher Robot, golang-scoped@luci-project-accounts.iam.gserviceaccount.com, accounts tagged SERVICE_USER, and any account whose name, username or email matches the pattern (bot|zuul|jenkins|ci|luci|gerrit code review|service user|automation|buildbot|lint|sonar|tryjob|cq|autosubmit|copybara|tricium|gerritforge|verifier|checker|scheduler). Deterministic, no model judgement. Before answers are issued, the extraction program must pass on 2 hand-checked units of this source (spec general rule 5); hand-checking is pending for the delivery step.
|
| 27 |
Tools: curl the Gerrit REST API (GET https://go-review.googlesource.com/changes/{number}/detail), strip the first line ")]}'" and read the JSON with jq or Python json; the git-review CLI and Gerrit's ssh 'gerrit query --format=JSON --all-approvals --comments' reach the same data where ssh access is open
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** curl the Gerrit REST API (GET https://go-review.googlesource.com/changes/{number}/detail), strip the first line ")]}'" and read the JSON with jq or Python json; the git-review CLI and Gerrit's ssh 'gerrit query --format=JSON --all-approvals --comments' reach the same data where ssh access is open
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 19 |
- `changes/675596/detail.json`: Go change 675596: internal/pkgbits: explain the rationale for reference tables.
|
| 20 |
Format: Gerrit REST API ChangeInfo JSON from the /detail endpoint, preceded by the anti-XSSI line ")]}'": status, created, updated, submitted, submitter, owner, labels with every vote (DETAILED_LABELS), messages (author, real_author, date, tag, _revision_number, message text) and reviewer_updates (updated, updated_by, reviewer, state REVIEWER/CC/REMOVED). Patch-set uploads are messages tagged autogenerated:gerrit:newPatchSet; votes appear in message text as 'Patch Set N: Label+V' and in labels.*.all. The endpoint returns all messages and reviewer updates of the change, so the record is complete.
|
| 21 |
Origin: Live Gerrit REST interface of a closed (merged) code review change, collected as a NOASSERTION pointer row under spec general rule 4: the detail JSON was fetched twice apart and was byte-identical. Unit file kept only outside the repository for checking and then deleted.
|
|
|
|
|
|
|
| 22 |
Check: Exact match against values read from the pinned JSON: status, submitted and submitter; reviewer_updates entries (reviewer, state, updated_by, updated); messages tagged autogenerated:gerrit:newPatchSet (patch-set count, _revision_number); votes from labels.*.all (value, _account_id) and from message first lines 'Patch Set N: Label+V'. A human review comment is a message whose author is not a bot or service account, whose tag does not start with 'autogenerated:', and whose text has content beyond the 'Patch Set N: votes' first line or names inline comments '(N comments)'. Bot and service accounts excluded from the comment count: Gopher Robot, golang-scoped@luci-project-accounts.iam.gserviceaccount.com, accounts tagged SERVICE_USER, and any account whose name, username or email matches the pattern (bot|zuul|jenkins|ci|luci|gerrit code review|service user|automation|buildbot|lint|sonar|tryjob|cq|autosubmit|copybara|tricium|gerritforge|verifier|checker|scheduler). Deterministic, no model judgement. Before answers are issued, the extraction program must pass on 2 hand-checked units of this source (spec general rule 5); hand-checking is pending for the delivery step.
|
| 23 |
Tools: curl the Gerrit REST API (GET https://go-review.googlesource.com/changes/{number}/detail), strip the first line ")]}'" and read the JSON with jq or Python json; the git-review CLI and Gerrit's ssh 'gerrit query --format=JSON --all-approvals --comments' reach the same data where ssh access is open
|
campaign_files/2026-10-m-issue-trackers-2/go-north-east-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/gonortheast/gtfs/gonortheast_1791284168.zip
|
| 23 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 24 |
Origin: Live static GTFS feed published by Go North East (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/gonortheast/gtfs/gonortheast_1791284168.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/gonortheast/gtfs/gonortheast_1791284168.zip
|
| 21 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 22 |
Origin: Live static GTFS feed published by Go North East (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/gonortheast/gtfs/gonortheast_1791284168.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/gocornwallbus-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/gocornwallbus/gtfs/gocornwallbus_1790941473.zip
|
| 23 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 24 |
Origin: Live static GTFS feed published by Transport For Cornwall (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/gocornwallbus/gtfs/gocornwallbus_1790941473.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/gocornwallbus/gtfs/gocornwallbus_1790941473.zip
|
| 21 |
Format: text/csv (GTFS Schedule calendar.txt; companions calendar_dates.txt, agency.txt)
|
| 22 |
Origin: Live static GTFS feed published by Transport For Cornwall (published through Passenger, data.discoverpassenger.com) at https://s3-eu-west-1.amazonaws.com/passenger-sources/gocornwallbus/gtfs/gocornwallbus_1790941473.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/golang-maintner-mutlog/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. 10 of 10 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: Facts computed from the ticket event timeline. 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 log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
@@ -21,80 +19,60 @@ Files:
|
|
| 21 |
- `m025-01/0150.800b223053e85c6a91da7a43449b4586abdc8cc531e0075058121b5f.mutlog`: Go maintner mutation log segment 0150 (GitHub issue timelines of golang/* repositories, window ending Wed, 15 Mar 2023 20:48:44 GMT).
|
| 22 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 23 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
| 24 |
-
Reference result: facts computed from the ticket event timeline
|
| 25 |
-
Reference source: The answer anchors on the FIRST closed event: later reopen or re-close history can fall after the segment cut, the first close cannot change. Logins come from GithubUser records in the same unit.
|
| 26 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 12 tickets before, 4 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 27 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 28 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 29 |
- `m025-02/0170.7c786b04efa19fdbdbc95085e77dd27f00689cd81a0c9ab8016fc252.mutlog`: Go maintner mutation log segment 0170 (GitHub issue timelines of golang/* repositories, window ending Tue, 20 Feb 2024 13:23:46 GMT).
|
| 30 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 31 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
| 32 |
-
Reference result: facts computed from the ticket event timeline
|
| 33 |
-
Reference source: The answer anchors on the FIRST closed event: later reopen or re-close history can fall after the segment cut, the first close cannot change. Logins come from GithubUser records in the same unit.
|
| 34 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 9 tickets before, 4 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 35 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 36 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 37 |
- `m025-03/0190.90b482f14e56707cb54f8913939ae72351099ac2fe2d79ba4f92ae5b.mutlog`: Go maintner mutation log segment 0190 (GitHub issue timelines of golang/* repositories, window ending Wed, 05 Feb 2025 22:31:53 GMT).
|
| 38 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 39 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
| 40 |
-
Reference result: facts computed from the ticket event timeline
|
| 41 |
-
Reference source: The answer anchors on the FIRST closed event: later reopen or re-close history can fall after the segment cut, the first close cannot change. Logins come from GithubUser records in the same unit.
|
| 42 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 13 tickets before, 6 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 43 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 44 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 45 |
- `m025-04/0200.c85c1ebf8874fa35dd2c78f1a8dbda43f70ce2aa6bdd5cba9437b5ac.mutlog`: Go maintner mutation log segment 0200 (GitHub issue timelines of golang/* repositories, window ending Thu, 14 Aug 2025 18:18:52 GMT).
|
| 46 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 47 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
| 48 |
-
Reference result: facts computed from the ticket event timeline
|
| 49 |
-
Reference source: The answer anchors on the FIRST closed event: later reopen or re-close history can fall after the segment cut, the first close cannot change. Logins come from GithubUser records in the same unit.
|
| 50 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 12 tickets before, 9 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 51 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 52 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 53 |
- `m025-05/0210.01129d568296238ff08a73897a6ee8dd5ed430e483305214dff90391.mutlog`: Go maintner mutation log segment 0210 (GitHub issue timelines of golang/* repositories, window ending Tue, 17 Feb 2026 21:07:17 GMT).
|
| 54 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 55 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
| 56 |
-
Reference result: facts computed from the ticket event timeline
|
| 57 |
-
Reference source: The answer anchors on the FIRST closed event: later reopen or re-close history can fall after the segment cut, the first close cannot change. Logins come from GithubUser records in the same unit.
|
| 58 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 12 tickets before, 7 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 59 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 60 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 61 |
- `m025-06/0215.2a0e3b2967923d3ee7ab2e94ebfeee8a0a613f1e074215a66d5630be.mutlog`: Go maintner mutation log segment 0215 (GitHub issue timelines of golang/* repositories, window ending Fri, 13 Mar 2026 10:06:04 GMT).
|
| 62 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 63 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
| 64 |
-
Reference result: facts computed from the ticket event timeline
|
| 65 |
-
Reference source: The answer anchors on the FIRST closed event: later reopen or re-close history can fall after the segment cut, the first close cannot change. Logins come from GithubUser records in the same unit.
|
| 66 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 3 tickets before, 2 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 67 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 68 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 69 |
- `m025-07/0220.380691826eeebfa16fb808d0fed4ad216a4d7da40a692763fd435fad.mutlog`: Go maintner mutation log segment 0220 (GitHub issue timelines of golang/* repositories, window ending Sun, 10 May 2026 11:52:28 GMT).
|
| 70 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 71 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
| 72 |
-
Reference result: facts computed from the ticket event timeline
|
| 73 |
-
Reference source: The answer anchors on the FIRST closed event: later reopen or re-close history can fall after the segment cut, the first close cannot change. Logins come from GithubUser records in the same unit.
|
| 74 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 6 tickets before, 3 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 75 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 76 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 77 |
- `m025-08/0225.8d2fd86dd8974974adccbcadfe6a9cde334c6b2fc79a042a36fabdd4.mutlog`: Go maintner mutation log segment 0225 (GitHub issue timelines of golang/* repositories, window ending Fri, 24 Jul 2026 16:00:26 GMT).
|
| 78 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 79 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
| 80 |
-
Reference result: facts computed from the ticket event timeline
|
| 81 |
-
Reference source: The answer anchors on the FIRST closed event: later reopen or re-close history can fall after the segment cut, the first close cannot change. Logins come from GithubUser records in the same unit.
|
| 82 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 11 tickets before, 5 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 83 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 84 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 85 |
- `m025-09/0228.1991a45883f2634f344993f454dcd16682ac01e073d033d55b621c62.mutlog`: Go maintner mutation log segment 0228 (GitHub issue timelines of golang/* repositories, window ending Tue, 01 Sep 2026 18:41:25 GMT).
|
| 86 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 87 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
| 88 |
-
Reference result: facts computed from the ticket event timeline
|
| 89 |
-
Reference source: The answer anchors on the FIRST closed event: later reopen or re-close history can fall after the segment cut, the first close cannot change. Logins come from GithubUser records in the same unit.
|
| 90 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 13 tickets before, 4 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 91 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 92 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 93 |
- `m025-10/0230.5da30ef574b895b0b5b663bc86163f158630571dc9a764c504109d93.mutlog`: Go maintner mutation log segment 0230 (GitHub issue timelines of golang/* repositories, window ending Mon, 28 Sep 2026 19:32:20 GMT).
|
| 94 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 95 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
| 96 |
-
Reference result: facts computed from the ticket event timeline
|
| 97 |
-
Reference source: The answer anchors on the FIRST closed event: later reopen or re-close history can fall after the segment cut, the first close cannot change. Logins come from GithubUser records in the same unit.
|
| 98 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 3 tickets before, 2 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 99 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 100 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 10 of 10 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 19 |
- `m025-01/0150.800b223053e85c6a91da7a43449b4586abdc8cc531e0075058121b5f.mutlog`: Go maintner mutation log segment 0150 (GitHub issue timelines of golang/* repositories, window ending Wed, 15 Mar 2023 20:48:44 GMT).
|
| 20 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 21 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
|
|
|
|
|
|
| 22 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 12 tickets before, 4 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 23 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 24 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 25 |
- `m025-02/0170.7c786b04efa19fdbdbc95085e77dd27f00689cd81a0c9ab8016fc252.mutlog`: Go maintner mutation log segment 0170 (GitHub issue timelines of golang/* repositories, window ending Tue, 20 Feb 2024 13:23:46 GMT).
|
| 26 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 27 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
|
|
|
|
|
|
| 28 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 9 tickets before, 4 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 29 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 30 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 31 |
- `m025-03/0190.90b482f14e56707cb54f8913939ae72351099ac2fe2d79ba4f92ae5b.mutlog`: Go maintner mutation log segment 0190 (GitHub issue timelines of golang/* repositories, window ending Wed, 05 Feb 2025 22:31:53 GMT).
|
| 32 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 33 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
|
|
|
|
|
|
| 34 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 13 tickets before, 6 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 35 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 36 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 37 |
- `m025-04/0200.c85c1ebf8874fa35dd2c78f1a8dbda43f70ce2aa6bdd5cba9437b5ac.mutlog`: Go maintner mutation log segment 0200 (GitHub issue timelines of golang/* repositories, window ending Thu, 14 Aug 2025 18:18:52 GMT).
|
| 38 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 39 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
|
|
|
|
|
|
| 40 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 12 tickets before, 9 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 41 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 42 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 43 |
- `m025-05/0210.01129d568296238ff08a73897a6ee8dd5ed430e483305214dff90391.mutlog`: Go maintner mutation log segment 0210 (GitHub issue timelines of golang/* repositories, window ending Tue, 17 Feb 2026 21:07:17 GMT).
|
| 44 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 45 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
|
|
|
|
|
|
| 46 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 12 tickets before, 7 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 47 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 48 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 49 |
- `m025-06/0215.2a0e3b2967923d3ee7ab2e94ebfeee8a0a613f1e074215a66d5630be.mutlog`: Go maintner mutation log segment 0215 (GitHub issue timelines of golang/* repositories, window ending Fri, 13 Mar 2026 10:06:04 GMT).
|
| 50 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 51 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
|
|
|
|
|
|
| 52 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 3 tickets before, 2 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 53 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 54 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 55 |
- `m025-07/0220.380691826eeebfa16fb808d0fed4ad216a4d7da40a692763fd435fad.mutlog`: Go maintner mutation log segment 0220 (GitHub issue timelines of golang/* repositories, window ending Sun, 10 May 2026 11:52:28 GMT).
|
| 56 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 57 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
|
|
|
|
|
|
| 58 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 6 tickets before, 3 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 59 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 60 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 61 |
- `m025-08/0225.8d2fd86dd8974974adccbcadfe6a9cde334c6b2fc79a042a36fabdd4.mutlog`: Go maintner mutation log segment 0225 (GitHub issue timelines of golang/* repositories, window ending Fri, 24 Jul 2026 16:00:26 GMT).
|
| 62 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 63 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
|
|
|
|
|
|
| 64 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 11 tickets before, 5 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 65 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 66 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 67 |
- `m025-09/0228.1991a45883f2634f344993f454dcd16682ac01e073d033d55b621c62.mutlog`: Go maintner mutation log segment 0228 (GitHub issue timelines of golang/* repositories, window ending Tue, 01 Sep 2026 18:41:25 GMT).
|
| 68 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 69 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
|
|
|
|
|
|
| 70 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 13 tickets before, 4 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 71 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 72 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
| 73 |
- `m025-10/0230.5da30ef574b895b0b5b663bc86163f158630571dc9a764c504109d93.mutlog`: Go maintner mutation log segment 0230 (GitHub issue timelines of golang/* repositories, window ending Mon, 28 Sep 2026 19:32:20 GMT).
|
| 74 |
Format: Binary append-only log: repeated 'REC@<hexoff>+<hexlen>=' headers each followed by a protobuf maintpb.MutationLog message. Decodable with any protobuf library (or a generic wire-format reader) and the companion .proto; no maintner code needs to run.
|
| 75 |
Origin: Sealed, content-addressed segment of the Go project's maintner mutation log: an append-only record of every GitHub issue/PR change (creation, title and body edits, comments, events such as closed, reopened, assigned, unassigned, labeled, milestoned) and of Gerrit code-review changes on go.googlesource.com, written by the Go team's corpus mirror. Each segment is about 16.8 MB, named by its SHA-224 and never rewritten once sealed (only the last segment, number 231 when listed, still grows and is excluded). Record framing: 'REC@<hex offset>+<hex length>=' then one protobuf maintpb.MutationLog message; MutationLog field 1 is a GitHub issue mutation, field 4 a Gerrit mutation, field 2 a git commit mutation.
|
|
|
|
|
|
|
| 76 |
Check: The unit is delivered as the whole upstream segment file, several cases in one file, not split or reordered per ticket (115 spec general rule 5); For now questions use only the GitHub part of the segment (MutationLog field 1, the only part whose decoding is validated); the Gerrit code-review records (field 4) are not used for questions until the decoder replays them, the review thickness threshold of line M is applied and at least 2 changes are hand-checked against go-review.googlesource.com with all fields matching, after which qualifying_changes will be added. Thickness counts human comments only: a comment is a bot comment when its author's login ends in '[bot]' (GitHub's marker for app accounts) or is one of this source's automated accounts gopherbot and gabyhelp (BOT_LOGINS in maintner_timeline.py). How the list was derived: maintner_timeline.py SEGMENT commenters listed every comment author on the issues of all 10 segments (1,712 logins) with comment count and distinct opening lines; the only logins containing 'bot' were gopherbot (8,924 comments, templated: CL-mention notices, dashboard flake reports, backport notices), rtribotte and work-robot (1 comment each), and the only accounts with at least 20 comments and fewer distinct opening lines than half their comments were gopherbot and gabyhelp (786 comments, nearly all '**Related Issues/Code Changes/Documentation**'); api.github.com/users shows gopherbot (name GopherBot, company Google) and gabyhelp (bio 'Go AI bot ... Run by @rsc') as automated accounts (both type User, so GitHub's own bot marker does not catch them) and work-robot as a person (Robert Schneider, SAP); rtribotte contains 'bot' only inside a surname (not looked up), so rtribotte and work-robot stay human. In this segment bot comments were found from dependabot[bot], gabyhelp, google-cla[bot], gopherbot (the '[bot]' accounts only on pull requests); on the qualifying tickets from gabyhelp, gopherbot. Bot comments stay in the timeline, in n_comments and in the answer fields and may be asked about; only the threshold leaves them out (n_human_comments). Recount 2026-10-06: 3 tickets before, 2 after. Deterministic, no model judgement. GitHub Projects (v2) events are not in maintner, so event counts are those of the log, not of today's page.
|
| 77 |
Tools: Read the log without a browser: decode the segment with any protobuf library and the companion maintner.proto (REC@ headers, then maintpb.MutationLog messages) and replay one ticket's mutations in file order; the judge reads only the replayed timeline (events with actor and UTC time), no screenshot needed.
|
| 78 |
Companions (not included): maintner/maintpb/maintner.proto (golang/build at 785db46b4b29423ce42e2d75628cd31304aecc1e; the protobuf schema needed to decode the unit; fetched); LICENSE (golang/build at the same commit; BSD-3-Clause text covering the schema; fetched)
|
campaign_files/2026-10-md-media-and-documents/github-markup/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected HTML of a MediaWiki-markup README. 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:** github-markup bin (GitHub::Markup.render via the wikicloth gem) run on the file in a Ruby script; output compared with the expected HTML after the normalisation of test/markup_test.rb
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `test/markups/README.mediawiki`: Github-markup test: README in MediaWiki markup rendered to HTML.
|
| 22 |
Format: MediaWiki markup input and one expected HTML file (README.mediawiki.html)
|
| 23 |
Origin: sample README in MediaWiki markup and its expected HTML written by the github/markup maintainers; test/markup_test.rb is the judge
|
| 24 |
-
Reference result: expected HTML of a MediaWiki-markup README
|
| 25 |
-
Reference source: test/markups/README.mediawiki.html
|
| 26 |
Check: give the agent README.mediawiki and ask for the HTML github-markup renders; parse both with Nokogiri (noblanks), normalise every text node (strip, collapse runs of whitespace, smart quotes to straight quotes, ellipsis to three dots) and diff the trees; an added id attribute is ignored, any other node difference fails
|
| 27 |
Tools: github-markup bin (GitHub::Markup.render via the wikicloth gem) run on the file in a Ruby script; output compared with the expected HTML after the normalisation of test/markup_test.rb
|
| 28 |
Companions (not included): test/markups/README.mediawiki.html; test/markup_test.rb; LICENSE
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** github-markup bin (GitHub::Markup.render via the wikicloth gem) run on the file in a Ruby script; output compared with the expected HTML after the normalisation of test/markup_test.rb
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `test/markups/README.mediawiki`: Github-markup test: README in MediaWiki markup rendered to HTML.
|
| 20 |
Format: MediaWiki markup input and one expected HTML file (README.mediawiki.html)
|
| 21 |
Origin: sample README in MediaWiki markup and its expected HTML written by the github/markup maintainers; test/markup_test.rb is the judge
|
|
|
|
|
|
|
| 22 |
Check: give the agent README.mediawiki and ask for the HTML github-markup renders; parse both with Nokogiri (noblanks), normalise every text node (strip, collapse runs of whitespace, smart quotes to straight quotes, ellipsis to three dots) and diff the trees; an added id attribute is ignored, any other node difference fails
|
| 23 |
Tools: github-markup bin (GitHub::Markup.render via the wikicloth gem) run on the file in a Ruby script; output compared with the expected HTML after the normalisation of test/markup_test.rb
|
| 24 |
Companions (not included): test/markups/README.mediawiki.html; test/markup_test.rb; LICENSE
|
campaign_files/2026-10-md-media-and-documents/gnome-pango-tests-layouts/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: Expected serialized layout (JSON "output" object) compared byte for byte. 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:** build pango at the pinned commit and run tests/test-layout (meson test test-layout), headless: deserialize, lay out, serialize and diff
|
| 14 |
|
| 15 |
**Licence (SPDX):** LGPL-2.0-or-later AND OFL-1.1
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `tests/layouts/valid-1.layout`: Pango layout test valid-1: an ellipsized, underlined English sentence laid out in Cantarell 11 at a fixed width, with the expected line breaks, runs and glyph positions.
|
| 22 |
Format: Pango serialized layout (.layout, JSON) with input and expected output
|
| 23 |
Origin: regression test of the Pango maintainers; the "output" object in the same file is the accepted layout (lines, runs, glyphs, extents) that test-layout.c must reproduce
|
| 24 |
-
Reference result: expected serialized layout (JSON "output" object) compared byte for byte
|
| 25 |
-
Reference source: the "output" object of tests/layouts/valid-1.layout, saved by the maintainers from accepted runs
|
| 26 |
Check: load the .layout with pango_layout_deserialize using the test fonts, serialize it again with its output and diff the bytes against the original file; any difference fails; hide the "output" object when posing the task
|
| 27 |
Tools: build pango at the pinned commit and run tests/test-layout (meson test test-layout), headless: deserialize, lay out, serialize and diff
|
| 28 |
Companions (not included): tests/test-layout.c; tests/fonts/fonts.conf; tests/fonts/README; tests/fonts/Cantarell-VF.otf; COPYING
|
|
|
|
| 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:** build pango at the pinned commit and run tests/test-layout (meson test test-layout), headless: deserialize, lay out, serialize and diff
|
| 12 |
|
| 13 |
**Licence (SPDX):** LGPL-2.0-or-later AND OFL-1.1
|
|
|
|
| 19 |
- `tests/layouts/valid-1.layout`: Pango layout test valid-1: an ellipsized, underlined English sentence laid out in Cantarell 11 at a fixed width, with the expected line breaks, runs and glyph positions.
|
| 20 |
Format: Pango serialized layout (.layout, JSON) with input and expected output
|
| 21 |
Origin: regression test of the Pango maintainers; the "output" object in the same file is the accepted layout (lines, runs, glyphs, extents) that test-layout.c must reproduce
|
|
|
|
|
|
|
| 22 |
Check: load the .layout with pango_layout_deserialize using the test fonts, serialize it again with its output and diff the bytes against the original file; any difference fails; hide the "output" object when posing the task
|
| 23 |
Tools: build pango at the pinned commit and run tests/test-layout (meson test test-layout), headless: deserialize, lay out, serialize and diff
|
| 24 |
Companions (not included): tests/test-layout.c; tests/fonts/fonts.conf; tests/fonts/README; tests/fonts/Cantarell-VF.otf; COPYING
|
campaign_files/2026-10-md-media-and-documents/gnu-groff-src-roff-groff-tests/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether each file needs other upstream files is not stated. 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 pattern (extended regular expression on the UTF-8 typeset text); expected intermediate output lines (three grep patterns). 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:** groff -Tutf8 on the roff input (command line typesetter, headless), output checked with grep -E; groff -Tps -Z on the roff input (command line typesetter emitting device-independent intermediate output, headless), output checked with sed and grep
|
| 14 |
|
| 15 |
**Licence (SPDX):** GPL-3.0-or-later
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `src/roff/groff/tests/recognize-end-of-sentence.sh`: Groff test recognize-end-of-sentence: closing punctuation after a period stays transparent and the sentence gets two spaces.
|
| 22 |
Format: POSIX shell test script with embedded roff input and expected-output pattern
|
| 23 |
Origin: regression test of the groff maintainers; the expected output is written into the script as a pattern
|
| 24 |
-
Reference result: expected output pattern (extended regular expression on the UTF-8 typeset text)
|
| 25 |
-
Reference source: src/roff/groff/tests/recognize-end-of-sentence.sh line 29: the typeset line must match 'Eat\.[^ ]+ Drink\.' (two spaces after the closing punctuation)
|
| 26 |
Check: typeset the here-document with groff -Tutf8 and test the output with the script's grep -qE pattern; the script exits 0 on a pass; hide the pattern when posing the task (ask for the typeset line)
|
| 27 |
Tools: groff -Tutf8 on the roff input (command line typesetter, headless), output checked with grep -E
|
| 28 |
Companions (not included): COPYING
|
|
@@ -30,8 +26,6 @@ Files:
|
|
| 30 |
- `src/roff/groff/tests/draw-circle.sh`: Groff test draw-circle: \D'c 1' between two glyphs becomes the intermediate-output command D c 10000 on the ps device.
|
| 31 |
Format: POSIX shell test script with embedded roff input and expected-output pattern
|
| 32 |
Origin: regression test of the groff maintainers; the expected output is written into the script as a pattern
|
| 33 |
-
Reference result: expected intermediate output lines (three grep patterns)
|
| 34 |
-
Reference source: src/roff/groff/tests/draw-circle.sh lines 23 to 25: t *A, D *c *10000, t *B
|
| 35 |
Check: run groff -Tps -Z on the input, extract the three lines as the script does and test each with its pattern; the script exits 0 on a pass; hide the expected lines when posing the task
|
| 36 |
Tools: groff -Tps -Z on the roff input (command line typesetter emitting device-independent intermediate output, headless), output checked with sed and grep
|
| 37 |
Companions (not included): COPYING
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether each file needs other upstream files is not stated. 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:** groff -Tutf8 on the roff input (command line typesetter, headless), output checked with grep -E; groff -Tps -Z on the roff input (command line typesetter emitting device-independent intermediate output, headless), output checked with sed and grep
|
| 12 |
|
| 13 |
**Licence (SPDX):** GPL-3.0-or-later
|
|
|
|
| 19 |
- `src/roff/groff/tests/recognize-end-of-sentence.sh`: Groff test recognize-end-of-sentence: closing punctuation after a period stays transparent and the sentence gets two spaces.
|
| 20 |
Format: POSIX shell test script with embedded roff input and expected-output pattern
|
| 21 |
Origin: regression test of the groff maintainers; the expected output is written into the script as a pattern
|
|
|
|
|
|
|
| 22 |
Check: typeset the here-document with groff -Tutf8 and test the output with the script's grep -qE pattern; the script exits 0 on a pass; hide the pattern when posing the task (ask for the typeset line)
|
| 23 |
Tools: groff -Tutf8 on the roff input (command line typesetter, headless), output checked with grep -E
|
| 24 |
Companions (not included): COPYING
|
|
|
|
| 26 |
- `src/roff/groff/tests/draw-circle.sh`: Groff test draw-circle: \D'c 1' between two glyphs becomes the intermediate-output command D c 10000 on the ps device.
|
| 27 |
Format: POSIX shell test script with embedded roff input and expected-output pattern
|
| 28 |
Origin: regression test of the groff maintainers; the expected output is written into the script as a pattern
|
|
|
|
|
|
|
| 29 |
Check: run groff -Tps -Z on the input, extract the three lines as the script does and test each with its pattern; the script exits 0 on a pass; hide the expected lines when posing the task
|
| 30 |
Tools: groff -Tps -Z on the roff input (command line typesetter emitting device-independent intermediate output, headless), output checked with sed and grep
|
| 31 |
Companions (not included): COPYING
|
campaign_files/2026-10-md-media-and-documents/go-org-testdata-tables/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected HTML of the whole Org document. 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:** go-org render tables.org html (the go-org command line tool); pandoc -f org -t html and emacs --batch with org-html-export-to-html are comparable
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `org/testdata/tables.org`: Go-org test "tables": Org mode tables converted to HTML.
|
| 22 |
Format: Org mode file tables.org (1369 bytes) with the expected HTML tables.html (3269 bytes)
|
| 23 |
Origin: test data written by the go-org author for the Org mode table syntax (header rows, separators, alignment cookies, column groups)
|
| 24 |
-
Reference result: expected HTML of the whole Org document
|
| 25 |
-
Reference source: org/testdata/tables.html
|
| 26 |
Check: give the agent tables.org; hide tables.html; pass when the HTML output equals tables.html exactly (org_writer_test.go testWriter: actual != expected fails)
|
| 27 |
Tools: go-org render tables.org html (the go-org command line tool); pandoc -f org -t html and emacs --batch with org-html-export-to-html are comparable
|
| 28 |
Companions (not included): org/testdata/tables.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. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** go-org render tables.org html (the go-org command line tool); pandoc -f org -t html and emacs --batch with org-html-export-to-html are comparable
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `org/testdata/tables.org`: Go-org test "tables": Org mode tables converted to HTML.
|
| 20 |
Format: Org mode file tables.org (1369 bytes) with the expected HTML tables.html (3269 bytes)
|
| 21 |
Origin: test data written by the go-org author for the Org mode table syntax (header rows, separators, alignment cookies, column groups)
|
|
|
|
|
|
|
| 22 |
Check: give the agent tables.org; hide tables.html; pass when the HTML output equals tables.html exactly (org_writer_test.go testWriter: actual != expected fails)
|
| 23 |
Tools: go-org render tables.org html (the go-org command line tool); pandoc -f org -t html and emacs --batch with org-html-export-to-html are comparable
|
| 24 |
Companions (not included): org/testdata/tables.html
|
campaign_files/2026-10-md-media-and-documents/golang-image-testdata/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. 12 of 12 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 decode: the same picture saved as PNG (96 by 73, 16-colour palette); reference decode: the Y, Cb and Cr planes of the decoded picture (400 by 301) laid out in one gray PNG in IMC4 arrangement; reference decode: the same picture saved as PNG (96 by 73, 256-colour palette); reference decode: the same picture saved as PNG (153 by 55 black and white); reference decode: the 153 by 55 black and white picture saved as PNG; reference decode: the same picture saved as PNG (75 by 100 with alpha); reference decode: the same picture saved as PNG (150 by 100 colour); reference decode: the same picture saved as PNG (16 by 12, 32-bit BGRA with a BITMAPV5HEADER); reference decode: the same picture saved as PNG (386 by 395 with alpha); reference decode: the Y, Cb and Cr planes of the decoded picture (600 by 400) laid out in one gray PNG in IMC4 arrangement; reference decode: the same picture saved as PNG (75 by 100); reference decode: the same picture saved as PNG (75 by 100, two colours). 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:** Tools are named in the check written per file in the notes.
|
| 14 |
|
| 15 |
**Licence (SPDX):** BSD-3-Clause
|
|
@@ -21,96 +19,72 @@ Files:
|
|
| 21 |
- `testdata/bmp_4bpp.bmp`: golang.org/x/image BMP test bmp_4bpp.bmp with its PNG reference.
|
| 22 |
Format: BMP (4 bits per pixel, palette, 3624 bytes) plus the reference PNG (96 by 73, 1134 bytes)
|
| 23 |
Origin: BMP decoder test file of golang.org/x/image with its PNG reference; bmp/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 42: "func TestDecode(t *testing.T) {" lists it by name and loads name+".png" and name+".bmp"
|
| 24 |
-
Reference result: reference decode: the same picture saved as PNG (96 by 73, 16-colour palette)
|
| 25 |
-
Reference source: testdata/bmp_4bpp.png: the reference image TestDecode compares the decoded BMP against (bmp/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 51: ""bmp_4bpp",")
|
| 26 |
Check: hide testdata/bmp_4bpp.png; the agent decodes testdata/bmp_4bpp.bmp and writes a PNG; pass if size equals the reference and every pixel has the same 16-bit RGBA value as the reference (Go color.RGBA() of both images, as the upstream compare does). The round checked with ffmpeg 7.1 that decoding the BMP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 27 |
Companions (not included): testdata/bmp_4bpp.png; bmp/reader_test.go; LICENSE
|
| 28 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 29 |
- `testdata/yellow_rose.lossy.webp`: golang.org/x/image lossy WebP test yellow_rose with its YCbCr plane reference.
|
| 30 |
Format: WebP (VP8 lossy) plus the reference gray PNG of its planes (400 by 452)
|
| 31 |
Origin: lossy WebP decoder test file of golang.org/x/image with its plane reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 149: "func TestDecodeVP8(t *testing.T) {"
|
| 32 |
-
Reference result: reference decode: the Y, Cb and Cr planes of the decoded picture (400 by 301) laid out in one gray PNG in IMC4 arrangement
|
| 33 |
-
Reference source: testdata/yellow_rose.lossy.webp.ycbcr.png: the reference planes testDecodeLossy compares the decoded VP8 image against (webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 37: "pngFilename := webpFilename + ".ycbcr.png""; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 156: ""yellow_rose",")
|
| 34 |
Check: hide testdata/yellow_rose.lossy.webp.ycbcr.png; the agent decodes testdata/yellow_rose.lossy.webp (lossy VP8, 4:2:0) to its raw Y, Cb and Cr planes, without colour conversion, and writes them as one gray PNG arranged as the test describes: the Y plane on top (width w, height h), below it the Cb plane on the left and the Cr plane starting at half the width (webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 89: "// (or 2*h+h2 high, if with Alpha) gray image arranged in IMC4 format:"); pass if every row of every plane equals the reference bytes. The round checked with ffmpeg 7.1 that the yuv420p planes of the decoded WebP equal the reference planes exactly (max difference 0)
|
| 35 |
Companions (not included): testdata/yellow_rose.lossy.webp.ycbcr.png; webp/decode_test.go; LICENSE
|
| 36 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 37 |
- `testdata/bmp_8bpp.bmp`: golang.org/x/image BMP test bmp_8bpp.bmp with its PNG reference.
|
| 38 |
Format: BMP (8 bits per pixel, palette, 7128 bytes) plus the reference PNG (96 by 73, 1134 bytes)
|
| 39 |
Origin: BMP decoder test file of golang.org/x/image with its PNG reference; bmp/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 42: "func TestDecode(t *testing.T) {" lists it by name and loads name+".png" and name+".bmp"
|
| 40 |
-
Reference result: reference decode: the same picture saved as PNG (96 by 73, 256-colour palette)
|
| 41 |
-
Reference source: testdata/bmp_8bpp.png: the reference image TestDecode compares the decoded BMP against (bmp/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 52: ""bmp_8bpp",")
|
| 42 |
Check: hide testdata/bmp_8bpp.png; the agent decodes testdata/bmp_8bpp.bmp and writes a PNG; pass if size equals the reference and every pixel has the same 16-bit RGBA value as the reference (Go color.RGBA() of both images, as the upstream compare does). The round checked with ffmpeg 7.1 that decoding the BMP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 43 |
Companions (not included): testdata/bmp_8bpp.png; bmp/reader_test.go; LICENSE
|
| 44 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 45 |
- `testdata/bw-gopher_ccittGroup4.tiff`: golang.org/x/image TIFF test bw-gopher_ccittGroup4.tiff with its PNG reference.
|
| 46 |
Format: TIFF (bilevel, CCITT Group 4 compression, 371 bytes) plus the reference PNG (153 by 55, 546 bytes)
|
| 47 |
Origin: TIFF decoder test file of golang.org/x/image with its PNG reference; TestDecodeCCITT builds the TIFF name from the PNG name (tiff/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 228: "img2, err := load(fn + "_ccittGroup4.tiff")")
|
| 48 |
-
Reference result: reference decode: the same picture saved as PNG (153 by 55 black and white)
|
| 49 |
-
Reference source: testdata/bw-gopher.png: the reference image TestDecodeCCITT compares the decoded TIFF against (tiff/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 212: "func TestDecodeCCITT(t *testing.T) {")
|
| 50 |
Check: hide testdata/bw-gopher.png; the agent decodes testdata/bw-gopher_ccittGroup4.tiff and writes a PNG; pass if size equals the reference and every pixel has the same 16-bit RGBA value as the reference (Go color.RGBA(), as the upstream compare does). The round checked with ffmpeg 7.1 that decoding the TIFF gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 51 |
Companions (not included): testdata/bw-gopher.png; tiff/reader_test.go; LICENSE
|
| 52 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 53 |
- `ccitt/testdata/bw-gopher.ccitt_group3`: golang.org/x/image raw CCITT Group 3 stream bw-gopher.ccitt_group3 with its PNG reference.
|
| 54 |
Format: raw CCITT T.4 (Group 3) bit stream without a container, plus the reference PNG (153 by 55)
|
| 55 |
Origin: CCITT decoder test stream of golang.org/x/image (package ccitt) with its PNG reference; ccitt/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 423: "func TestDecodeIntoGray(t *testing.T) {"
|
| 56 |
-
Reference result: reference decode: the 153 by 55 black and white picture saved as PNG
|
| 57 |
-
Reference source: ccitt/testdata/bw-gopher.png: the reference image testDecodeIntoGray compares the decoded stream against (ccitt/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 456: "want, err := decodePNG("testdata/bw-gopher.png")")
|
| 58 |
Check: hide ccitt/testdata/bw-gopher.png; give the agent ccitt/testdata/bw-gopher.ccitt_group3 and the decoding parameters the test passes (ccitt/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 429: "{"testdata/bw-gopher.ccitt_group3", Group3, 153, 55},"; ccitt/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 437: "testDecodeIntoGray(t, tt.fileName, MSB, tt.sf, tt.w, tt.h, nil)"): Group 3 (T.4, one-dimensional), most significant bit first, width 153, height 55, 0 bits mean white; the agent writes the decoded picture as an 8-bit gray PNG; pass if every pixel equals the reference. The round checked by wrapping the stream in a hand-built TIFF header (compression 3, WhiteIsZero) and decoding with ffmpeg 7.1: max difference 0 against the reference
|
| 59 |
Companions (not included): ccitt/testdata/bw-gopher.png; ccitt/reader_test.go; LICENSE
|
| 60 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 61 |
- `testdata/gopher-doc.with-alpha.lossless.webp`: golang.org/x/image lossless WebP test gopher-doc.with-alpha with its PNG reference.
|
| 62 |
Format: WebP (VP8L lossless with alpha, 4296 bytes) plus the reference PNG (75 by 100 RGBA, 6083 bytes)
|
| 63 |
Origin: lossless WebP decoder test file of golang.org/x/image with its PNG reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 174: "func TestDecodeVP8L(t *testing.T) {"
|
| 64 |
-
Reference result: reference decode: the same picture saved as PNG (75 by 100 with alpha)
|
| 65 |
-
Reference source: testdata/gopher-doc.with-alpha.png: the reference image TestDecodeVP8L compares the decoded lossless WebP against (webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 187: "{name: "gopher-doc.with-alpha"},")
|
| 66 |
Check: hide testdata/gopher-doc.with-alpha.png; the agent decodes testdata/gopher-doc.with-alpha.lossless.webp (lossless VP8L) and writes a PNG; pass if bounds equal and every non-premultiplied RGBA byte equals the reference converted to NRGBA (as the upstream test does). The round checked with ffmpeg 7.1 that decoding the WebP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 67 |
Companions (not included): testdata/gopher-doc.with-alpha.png; webp/decode_test.go; LICENSE
|
| 68 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 69 |
- `testdata/blue-purple-pink.lzwcompressed.tiff`: golang.org/x/image TIFF test blue-purple-pink.lzwcompressed.tiff with its PNG reference.
|
| 70 |
Format: TIFF (RGB, LZW compression, 38994 bytes) plus the reference PNG (150 by 100, 25003 bytes)
|
| 71 |
Origin: TIFF decoder test file of golang.org/x/image with its PNG reference; tiff/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 193: "img1, err := load("blue-purple-pink.lzwcompressed.tiff")"
|
| 72 |
-
Reference result: reference decode: the same picture saved as PNG (150 by 100 colour)
|
| 73 |
-
Reference source: testdata/blue-purple-pink.png: the reference image TestDecodeLZW compares the decoded TIFF against (tiff/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 188: "func TestDecodeLZW(t *testing.T) {")
|
| 74 |
Check: hide testdata/blue-purple-pink.png; the agent decodes testdata/blue-purple-pink.lzwcompressed.tiff and writes a PNG; pass if size equals the reference and every pixel has the same 16-bit RGBA value as the reference (Go color.RGBA(), as the upstream compare does). The round checked with ffmpeg 7.1 that decoding the TIFF gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 75 |
Companions (not included): testdata/blue-purple-pink.png; tiff/reader_test.go; LICENSE
|
| 76 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 77 |
- `testdata/yellow_rose-small-v5.bmp`: golang.org/x/image BMP test yellow_rose-small-v5.bmp with its PNG reference.
|
| 78 |
Format: BMP (BITMAPV5HEADER, 32-bit) plus the reference PNG (16 by 12)
|
| 79 |
Origin: BMP decoder test file of golang.org/x/image with its PNG reference; bmp/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 42: "func TestDecode(t *testing.T) {" lists it by name and loads name+".png" and name+".bmp"
|
| 80 |
-
Reference result: reference decode: the same picture saved as PNG (16 by 12, 32-bit BGRA with a BITMAPV5HEADER)
|
| 81 |
-
Reference source: testdata/yellow_rose-small-v5.png: the reference image TestDecode compares the decoded BMP against (bmp/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 49: ""yellow_rose-small-v5",")
|
| 82 |
Check: hide testdata/yellow_rose-small-v5.png; the agent decodes testdata/yellow_rose-small-v5.bmp and writes a PNG; pass if size equals the reference and every pixel has the same 16-bit RGBA value as the reference (Go color.RGBA() of both images, as the upstream compare does). The round checked with ffmpeg 7.1 that decoding the BMP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 83 |
Companions (not included): testdata/yellow_rose-small-v5.png; bmp/reader_test.go; LICENSE
|
| 84 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 85 |
- `testdata/tux.lossless.webp`: golang.org/x/image lossless WebP test tux with its PNG reference.
|
| 86 |
Format: WebP (VP8L lossless, 29920 bytes) plus the reference PNG (386 by 395 RGBA, 41427 bytes)
|
| 87 |
Origin: lossless WebP decoder test file of golang.org/x/image with its PNG reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 174: "func TestDecodeVP8L(t *testing.T) {"
|
| 88 |
-
Reference result: reference decode: the same picture saved as PNG (386 by 395 with alpha)
|
| 89 |
-
Reference source: testdata/tux.png: the reference image TestDecodeVP8L compares the decoded lossless WebP against (webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 188: "{name: "tux"},")
|
| 90 |
Check: hide testdata/tux.png; the agent decodes testdata/tux.lossless.webp (lossless VP8L) and writes a PNG; pass if bounds equal and every non-premultiplied RGBA byte equals the reference converted to NRGBA (as the upstream test does). The round checked with ffmpeg 7.1 that decoding the WebP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 91 |
Companions (not included): testdata/tux.png; webp/decode_test.go; LICENSE
|
| 92 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 93 |
- `testdata/blue-purple-pink-large.normal-filter.lossy.webp`: golang.org/x/image lossy WebP test blue-purple-pink-large.normal-filter (normal loop filter) with its YCbCr plane reference.
|
| 94 |
Format: WebP (VP8 lossy, normal loop filter, 22680 bytes) plus the reference gray PNG of its planes (600 by 600, 142114 bytes)
|
| 95 |
Origin: lossy WebP decoder test file of golang.org/x/image with its plane reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 149: "func TestDecodeVP8(t *testing.T) {"
|
| 96 |
-
Reference result: reference decode: the Y, Cb and Cr planes of the decoded picture (600 by 400) laid out in one gray PNG in IMC4 arrangement
|
| 97 |
-
Reference source: testdata/blue-purple-pink-large.normal-filter.lossy.webp.ycbcr.png: the reference planes testDecodeLossy compares the decoded VP8 image against (webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 37: "pngFilename := webpFilename + ".ycbcr.png""; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 154: ""blue-purple-pink-large.normal-filter",")
|
| 98 |
Check: hide testdata/blue-purple-pink-large.normal-filter.lossy.webp.ycbcr.png; the agent decodes testdata/blue-purple-pink-large.normal-filter.lossy.webp (lossy VP8, 4:2:0) to its raw Y, Cb and Cr planes, without colour conversion, and writes them as one gray PNG arranged as the test describes: the Y plane on top (width w, height h), below it the Cb plane on the left and the Cr plane starting at half the width (webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 89: "// (or 2*h+h2 high, if with Alpha) gray image arranged in IMC4 format:"); pass if every row of every plane equals the reference bytes. The round checked with ffmpeg 7.1 that the yuv420p planes of the decoded WebP equal the reference planes exactly (max difference 0)
|
| 99 |
Companions (not included): testdata/blue-purple-pink-large.normal-filter.lossy.webp.ycbcr.png; webp/decode_test.go; LICENSE
|
| 100 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 101 |
- `testdata/gopher-doc.skip-hgroup.lossless.webp`: golang.org/x/image lossless WebP test gopher-doc.skip-hgroup (unreferenced Huffman groups) with its PNG reference.
|
| 102 |
Format: WebP (VP8L lossless with unreferenced Huffman tree groups, 3786 bytes) plus the reference PNG (75 by 100, 6839 bytes)
|
| 103 |
Origin: lossless WebP decoder test file of golang.org/x/image with its PNG reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 174: "func TestDecodeVP8L(t *testing.T) {"; the test case comment says "VP8L image with unreferenced Huffman tree groups." and names f0 gopher-doc.skip-hgroup.lossless.webp, f1 gopher-doc.8bpp.png
|
| 104 |
-
Reference result: reference decode: the same picture saved as PNG (75 by 100)
|
| 105 |
-
Reference source: testdata/gopher-doc.8bpp.png: the reference image TestDecodeVP8L compares the decoded lossless WebP against (webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 193: "f0: "gopher-doc.skip-hgroup.lossless.webp",")
|
| 106 |
Check: hide testdata/gopher-doc.8bpp.png; the agent decodes testdata/gopher-doc.skip-hgroup.lossless.webp (lossless VP8L) and writes a PNG; pass if bounds equal and every non-premultiplied RGBA byte equals the reference converted to NRGBA (as the upstream test does). The round checked with ffmpeg 7.1 that decoding the WebP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 107 |
Companions (not included): testdata/gopher-doc.8bpp.png; webp/decode_test.go; LICENSE
|
| 108 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 109 |
- `testdata/gopher-doc.1bpp.lossless.webp`: golang.org/x/image lossless WebP test gopher-doc.1bpp (colour-indexing transform with 1-bit pixel bundling) with its PNG reference.
|
| 110 |
Format: WebP (VP8L lossless, 2-colour palette, 442 bytes) plus the reference PNG (75 by 100, 1026 bytes)
|
| 111 |
Origin: lossless WebP decoder test file of golang.org/x/image with its PNG reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 174: "func TestDecodeVP8L(t *testing.T) {"
|
| 112 |
-
Reference result: reference decode: the same picture saved as PNG (75 by 100, two colours)
|
| 113 |
-
Reference source: testdata/gopher-doc.1bpp.png: the reference image TestDecodeVP8L compares the decoded lossless WebP against (webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 183: "{name: "gopher-doc.1bpp"},")
|
| 114 |
Check: hide testdata/gopher-doc.1bpp.png; the agent decodes testdata/gopher-doc.1bpp.lossless.webp (lossless VP8L) and writes a PNG; pass if bounds equal and every non-premultiplied RGBA byte equals the reference converted to NRGBA (as the upstream test does). The round checked with ffmpeg 7.1 that decoding the WebP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 115 |
Companions (not included): testdata/gopher-doc.1bpp.png; webp/decode_test.go; LICENSE
|
| 116 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 12 of 12 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:** Tools are named in the check written per file in the notes.
|
| 12 |
|
| 13 |
**Licence (SPDX):** BSD-3-Clause
|
|
|
|
| 19 |
- `testdata/bmp_4bpp.bmp`: golang.org/x/image BMP test bmp_4bpp.bmp with its PNG reference.
|
| 20 |
Format: BMP (4 bits per pixel, palette, 3624 bytes) plus the reference PNG (96 by 73, 1134 bytes)
|
| 21 |
Origin: BMP decoder test file of golang.org/x/image with its PNG reference; bmp/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 42: "func TestDecode(t *testing.T) {" lists it by name and loads name+".png" and name+".bmp"
|
|
|
|
|
|
|
| 22 |
Check: hide testdata/bmp_4bpp.png; the agent decodes testdata/bmp_4bpp.bmp and writes a PNG; pass if size equals the reference and every pixel has the same 16-bit RGBA value as the reference (Go color.RGBA() of both images, as the upstream compare does). The round checked with ffmpeg 7.1 that decoding the BMP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 23 |
Companions (not included): testdata/bmp_4bpp.png; bmp/reader_test.go; LICENSE
|
| 24 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 25 |
- `testdata/yellow_rose.lossy.webp`: golang.org/x/image lossy WebP test yellow_rose with its YCbCr plane reference.
|
| 26 |
Format: WebP (VP8 lossy) plus the reference gray PNG of its planes (400 by 452)
|
| 27 |
Origin: lossy WebP decoder test file of golang.org/x/image with its plane reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 149: "func TestDecodeVP8(t *testing.T) {"
|
|
|
|
|
|
|
| 28 |
Check: hide testdata/yellow_rose.lossy.webp.ycbcr.png; the agent decodes testdata/yellow_rose.lossy.webp (lossy VP8, 4:2:0) to its raw Y, Cb and Cr planes, without colour conversion, and writes them as one gray PNG arranged as the test describes: the Y plane on top (width w, height h), below it the Cb plane on the left and the Cr plane starting at half the width (webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 89: "// (or 2*h+h2 high, if with Alpha) gray image arranged in IMC4 format:"); pass if every row of every plane equals the reference bytes. The round checked with ffmpeg 7.1 that the yuv420p planes of the decoded WebP equal the reference planes exactly (max difference 0)
|
| 29 |
Companions (not included): testdata/yellow_rose.lossy.webp.ycbcr.png; webp/decode_test.go; LICENSE
|
| 30 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 31 |
- `testdata/bmp_8bpp.bmp`: golang.org/x/image BMP test bmp_8bpp.bmp with its PNG reference.
|
| 32 |
Format: BMP (8 bits per pixel, palette, 7128 bytes) plus the reference PNG (96 by 73, 1134 bytes)
|
| 33 |
Origin: BMP decoder test file of golang.org/x/image with its PNG reference; bmp/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 42: "func TestDecode(t *testing.T) {" lists it by name and loads name+".png" and name+".bmp"
|
|
|
|
|
|
|
| 34 |
Check: hide testdata/bmp_8bpp.png; the agent decodes testdata/bmp_8bpp.bmp and writes a PNG; pass if size equals the reference and every pixel has the same 16-bit RGBA value as the reference (Go color.RGBA() of both images, as the upstream compare does). The round checked with ffmpeg 7.1 that decoding the BMP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 35 |
Companions (not included): testdata/bmp_8bpp.png; bmp/reader_test.go; LICENSE
|
| 36 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 37 |
- `testdata/bw-gopher_ccittGroup4.tiff`: golang.org/x/image TIFF test bw-gopher_ccittGroup4.tiff with its PNG reference.
|
| 38 |
Format: TIFF (bilevel, CCITT Group 4 compression, 371 bytes) plus the reference PNG (153 by 55, 546 bytes)
|
| 39 |
Origin: TIFF decoder test file of golang.org/x/image with its PNG reference; TestDecodeCCITT builds the TIFF name from the PNG name (tiff/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 228: "img2, err := load(fn + "_ccittGroup4.tiff")")
|
|
|
|
|
|
|
| 40 |
Check: hide testdata/bw-gopher.png; the agent decodes testdata/bw-gopher_ccittGroup4.tiff and writes a PNG; pass if size equals the reference and every pixel has the same 16-bit RGBA value as the reference (Go color.RGBA(), as the upstream compare does). The round checked with ffmpeg 7.1 that decoding the TIFF gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 41 |
Companions (not included): testdata/bw-gopher.png; tiff/reader_test.go; LICENSE
|
| 42 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 43 |
- `ccitt/testdata/bw-gopher.ccitt_group3`: golang.org/x/image raw CCITT Group 3 stream bw-gopher.ccitt_group3 with its PNG reference.
|
| 44 |
Format: raw CCITT T.4 (Group 3) bit stream without a container, plus the reference PNG (153 by 55)
|
| 45 |
Origin: CCITT decoder test stream of golang.org/x/image (package ccitt) with its PNG reference; ccitt/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 423: "func TestDecodeIntoGray(t *testing.T) {"
|
|
|
|
|
|
|
| 46 |
Check: hide ccitt/testdata/bw-gopher.png; give the agent ccitt/testdata/bw-gopher.ccitt_group3 and the decoding parameters the test passes (ccitt/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 429: "{"testdata/bw-gopher.ccitt_group3", Group3, 153, 55},"; ccitt/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 437: "testDecodeIntoGray(t, tt.fileName, MSB, tt.sf, tt.w, tt.h, nil)"): Group 3 (T.4, one-dimensional), most significant bit first, width 153, height 55, 0 bits mean white; the agent writes the decoded picture as an 8-bit gray PNG; pass if every pixel equals the reference. The round checked by wrapping the stream in a hand-built TIFF header (compression 3, WhiteIsZero) and decoding with ffmpeg 7.1: max difference 0 against the reference
|
| 47 |
Companions (not included): ccitt/testdata/bw-gopher.png; ccitt/reader_test.go; LICENSE
|
| 48 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 49 |
- `testdata/gopher-doc.with-alpha.lossless.webp`: golang.org/x/image lossless WebP test gopher-doc.with-alpha with its PNG reference.
|
| 50 |
Format: WebP (VP8L lossless with alpha, 4296 bytes) plus the reference PNG (75 by 100 RGBA, 6083 bytes)
|
| 51 |
Origin: lossless WebP decoder test file of golang.org/x/image with its PNG reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 174: "func TestDecodeVP8L(t *testing.T) {"
|
|
|
|
|
|
|
| 52 |
Check: hide testdata/gopher-doc.with-alpha.png; the agent decodes testdata/gopher-doc.with-alpha.lossless.webp (lossless VP8L) and writes a PNG; pass if bounds equal and every non-premultiplied RGBA byte equals the reference converted to NRGBA (as the upstream test does). The round checked with ffmpeg 7.1 that decoding the WebP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 53 |
Companions (not included): testdata/gopher-doc.with-alpha.png; webp/decode_test.go; LICENSE
|
| 54 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 55 |
- `testdata/blue-purple-pink.lzwcompressed.tiff`: golang.org/x/image TIFF test blue-purple-pink.lzwcompressed.tiff with its PNG reference.
|
| 56 |
Format: TIFF (RGB, LZW compression, 38994 bytes) plus the reference PNG (150 by 100, 25003 bytes)
|
| 57 |
Origin: TIFF decoder test file of golang.org/x/image with its PNG reference; tiff/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 193: "img1, err := load("blue-purple-pink.lzwcompressed.tiff")"
|
|
|
|
|
|
|
| 58 |
Check: hide testdata/blue-purple-pink.png; the agent decodes testdata/blue-purple-pink.lzwcompressed.tiff and writes a PNG; pass if size equals the reference and every pixel has the same 16-bit RGBA value as the reference (Go color.RGBA(), as the upstream compare does). The round checked with ffmpeg 7.1 that decoding the TIFF gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 59 |
Companions (not included): testdata/blue-purple-pink.png; tiff/reader_test.go; LICENSE
|
| 60 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 61 |
- `testdata/yellow_rose-small-v5.bmp`: golang.org/x/image BMP test yellow_rose-small-v5.bmp with its PNG reference.
|
| 62 |
Format: BMP (BITMAPV5HEADER, 32-bit) plus the reference PNG (16 by 12)
|
| 63 |
Origin: BMP decoder test file of golang.org/x/image with its PNG reference; bmp/reader_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 42: "func TestDecode(t *testing.T) {" lists it by name and loads name+".png" and name+".bmp"
|
|
|
|
|
|
|
| 64 |
Check: hide testdata/yellow_rose-small-v5.png; the agent decodes testdata/yellow_rose-small-v5.bmp and writes a PNG; pass if size equals the reference and every pixel has the same 16-bit RGBA value as the reference (Go color.RGBA() of both images, as the upstream compare does). The round checked with ffmpeg 7.1 that decoding the BMP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 65 |
Companions (not included): testdata/yellow_rose-small-v5.png; bmp/reader_test.go; LICENSE
|
| 66 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 67 |
- `testdata/tux.lossless.webp`: golang.org/x/image lossless WebP test tux with its PNG reference.
|
| 68 |
Format: WebP (VP8L lossless, 29920 bytes) plus the reference PNG (386 by 395 RGBA, 41427 bytes)
|
| 69 |
Origin: lossless WebP decoder test file of golang.org/x/image with its PNG reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 174: "func TestDecodeVP8L(t *testing.T) {"
|
|
|
|
|
|
|
| 70 |
Check: hide testdata/tux.png; the agent decodes testdata/tux.lossless.webp (lossless VP8L) and writes a PNG; pass if bounds equal and every non-premultiplied RGBA byte equals the reference converted to NRGBA (as the upstream test does). The round checked with ffmpeg 7.1 that decoding the WebP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 71 |
Companions (not included): testdata/tux.png; webp/decode_test.go; LICENSE
|
| 72 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 73 |
- `testdata/blue-purple-pink-large.normal-filter.lossy.webp`: golang.org/x/image lossy WebP test blue-purple-pink-large.normal-filter (normal loop filter) with its YCbCr plane reference.
|
| 74 |
Format: WebP (VP8 lossy, normal loop filter, 22680 bytes) plus the reference gray PNG of its planes (600 by 600, 142114 bytes)
|
| 75 |
Origin: lossy WebP decoder test file of golang.org/x/image with its plane reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 149: "func TestDecodeVP8(t *testing.T) {"
|
|
|
|
|
|
|
| 76 |
Check: hide testdata/blue-purple-pink-large.normal-filter.lossy.webp.ycbcr.png; the agent decodes testdata/blue-purple-pink-large.normal-filter.lossy.webp (lossy VP8, 4:2:0) to its raw Y, Cb and Cr planes, without colour conversion, and writes them as one gray PNG arranged as the test describes: the Y plane on top (width w, height h), below it the Cb plane on the left and the Cr plane starting at half the width (webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 89: "// (or 2*h+h2 high, if with Alpha) gray image arranged in IMC4 format:"); pass if every row of every plane equals the reference bytes. The round checked with ffmpeg 7.1 that the yuv420p planes of the decoded WebP equal the reference planes exactly (max difference 0)
|
| 77 |
Companions (not included): testdata/blue-purple-pink-large.normal-filter.lossy.webp.ycbcr.png; webp/decode_test.go; LICENSE
|
| 78 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 79 |
- `testdata/gopher-doc.skip-hgroup.lossless.webp`: golang.org/x/image lossless WebP test gopher-doc.skip-hgroup (unreferenced Huffman groups) with its PNG reference.
|
| 80 |
Format: WebP (VP8L lossless with unreferenced Huffman tree groups, 3786 bytes) plus the reference PNG (75 by 100, 6839 bytes)
|
| 81 |
Origin: lossless WebP decoder test file of golang.org/x/image with its PNG reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 174: "func TestDecodeVP8L(t *testing.T) {"; the test case comment says "VP8L image with unreferenced Huffman tree groups." and names f0 gopher-doc.skip-hgroup.lossless.webp, f1 gopher-doc.8bpp.png
|
|
|
|
|
|
|
| 82 |
Check: hide testdata/gopher-doc.8bpp.png; the agent decodes testdata/gopher-doc.skip-hgroup.lossless.webp (lossless VP8L) and writes a PNG; pass if bounds equal and every non-premultiplied RGBA byte equals the reference converted to NRGBA (as the upstream test does). The round checked with ffmpeg 7.1 that decoding the WebP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 83 |
Companions (not included): testdata/gopher-doc.8bpp.png; webp/decode_test.go; LICENSE
|
| 84 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
| 85 |
- `testdata/gopher-doc.1bpp.lossless.webp`: golang.org/x/image lossless WebP test gopher-doc.1bpp (colour-indexing transform with 1-bit pixel bundling) with its PNG reference.
|
| 86 |
Format: WebP (VP8L lossless, 2-colour palette, 442 bytes) plus the reference PNG (75 by 100, 1026 bytes)
|
| 87 |
Origin: lossless WebP decoder test file of golang.org/x/image with its PNG reference; webp/decode_test.go (golang/image @c437a9130dcb43e6df402a034160826e29fd29b8) line 174: "func TestDecodeVP8L(t *testing.T) {"
|
|
|
|
|
|
|
| 88 |
Check: hide testdata/gopher-doc.1bpp.png; the agent decodes testdata/gopher-doc.1bpp.lossless.webp (lossless VP8L) and writes a PNG; pass if bounds equal and every non-premultiplied RGBA byte equals the reference converted to NRGBA (as the upstream test does). The round checked with ffmpeg 7.1 that decoding the WebP gives exactly the reference pixels as RGBA (max difference 0, 0 differing bytes)
|
| 89 |
Companions (not included): testdata/gopher-doc.1bpp.png; webp/decode_test.go; LICENSE
|
| 90 |
Dependencies: any decoder for the format (Go x/image, ffmpeg, libwebp, libtiff, Pillow).
|
campaign_files/2026-10-md-media-and-documents/goldmark-extension-testdata-footnote/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: Expected HTML with footnote section for each case. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** a small Go program calling goldmark.New(goldmark.WithExtensions(extension.Footnote)).Convert; pandoc -f markdown -t html renders the same footnote syntax
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `extension/testdata/footnote.txt`: Goldmark footnote extension test cases: Markdown footnotes converted to HTML.
|
| 22 |
Format: goldmark test case file (2992 bytes): 10 numbered cases, Markdown between "//- - - - - - - - -//" lines and expected HTML before "//= = = = = = = = = = = = = = = = = = = = = = = =//"
|
| 23 |
Origin: test data written by the goldmark author for the footnote extension (PHP Markdown Extra style footnotes)
|
| 24 |
-
Reference result: expected HTML with footnote section for each case
|
| 25 |
-
Reference source: the expected block of each numbered case
|
| 26 |
Check: split by the delimiter lines as testutil.DoTestCaseFile does; show only the Markdown; convert with the footnote parser and renderer (extension/footnote_test.go lines 14 to 24); pass when the output equals the expected block after trimming leading and trailing white space
|
| 27 |
Tools: a small Go program calling goldmark.New(goldmark.WithExtensions(extension.Footnote)).Convert; pandoc -f markdown -t html renders the same footnote syntax
|
| 28 |
Dependencies: goldmark; Go toolchain
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** The file is self-contained. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a small Go program calling goldmark.New(goldmark.WithExtensions(extension.Footnote)).Convert; pandoc -f markdown -t html renders the same footnote syntax
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `extension/testdata/footnote.txt`: Goldmark footnote extension test cases: Markdown footnotes converted to HTML.
|
| 20 |
Format: goldmark test case file (2992 bytes): 10 numbered cases, Markdown between "//- - - - - - - - -//" lines and expected HTML before "//= = = = = = = = = = = = = = = = = = = = = = = =//"
|
| 21 |
Origin: test data written by the goldmark author for the footnote extension (PHP Markdown Extra style footnotes)
|
|
|
|
|
|
|
| 22 |
Check: split by the delimiter lines as testutil.DoTestCaseFile does; show only the Markdown; convert with the footnote parser and renderer (extension/footnote_test.go lines 14 to 24); pass when the output equals the expected block after trimming leading and trailing white space
|
| 23 |
Tools: a small Go program calling goldmark.New(goldmark.WithExtensions(extension.Footnote)).Convert; pandoc -f markdown -t html renders the same footnote syntax
|
| 24 |
Dependencies: goldmark; Go toolchain
|
campaign_files/2026-10-md-media-and-documents/gusbrs-zref-check-testfiles/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: Expected normalised TeX log (.tlg) with the check warnings. 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:** l3build check zc-check-above01 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 14 |
|
| 15 |
**Licence (SPDX):** LPPL-1.3c
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `testfiles/zc-check-above01.lvt`: Zref-check l3build test above01: float placement checks (\zcheck[above]) pass or warn depending on where figures land.
|
| 22 |
Format: LaTeX test file (.lvt) plus expected log (.tlg)
|
| 23 |
Origin: regression test of the package author; the .tlg is the accepted normalised log with the expected warnings
|
| 24 |
-
Reference result: expected normalised TeX log (.tlg) with the check warnings
|
| 25 |
-
Reference source: testfiles/zc-check-above01.tlg, saved by the author from checked runs (one file for all engines)
|
| 26 |
Check: run the .lvt with l3build on each engine and compare the normalised .log with the .tlg line by line; hide the .tlg when posing the task
|
| 27 |
Tools: l3build check zc-check-above01 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 28 |
Companions (not included): build.lua; 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:** l3build check zc-check-above01 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 12 |
|
| 13 |
**Licence (SPDX):** LPPL-1.3c
|
|
|
|
| 19 |
- `testfiles/zc-check-above01.lvt`: Zref-check l3build test above01: float placement checks (\zcheck[above]) pass or warn depending on where figures land.
|
| 20 |
Format: LaTeX test file (.lvt) plus expected log (.tlg)
|
| 21 |
Origin: regression test of the package author; the .tlg is the accepted normalised log with the expected warnings
|
|
|
|
|
|
|
| 22 |
Check: run the .lvt with l3build on each engine and compare the normalised .log with the .tlg line by line; hide the .tlg when posing the task
|
| 23 |
Tools: l3build check zc-check-above01 (headless LaTeX run, log normalised and diffed against the .tlg)
|
| 24 |
Companions (not included): build.lua; LICENSE
|
campaign_files/2026-10-ml-serving-configs-2/github-amazon-science-petshop-root-cause-analysis/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether each unit needs other upstream files is not stated. 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: labelled_root_cause. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Hide root_cause and metadata of target.json (keep target). Task: from metrics.csv and graph.csv the agent names the root cause node of the anomaly on the target node; pass on an exact string match with root_cause.node. A second task names the injected fault kind (delay or error rate) from the injection command; exact match.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC-BY-4.0
|
|
@@ -21,24 +19,18 @@ Units:
|
|
| 21 |
- `dataset/high_traffic/train/issue_1/` (2 files): PetShop high traffic, train issue 1: service metrics of a microservice pet shop around a latency anomaly with the injected root cause labelled.
|
| 22 |
Format: metrics.csv: CSV with a multi-row header (microservice, metric, aggregation) and one column per service metric, time stamps as rows; target.json: JSON with the anomalous target node, metric, aggregation and time stamp, the root cause node and the fault injection command; graph.csv: adjacency matrix of the service call graph
|
| 23 |
Origin: metrics recorded on a real deployment of the AWS pet adoption demo application with injected faults, published as a benchmark.
|
| 24 |
-
Reference result: labelled_root_cause
|
| 25 |
-
Reference source: target.json, root_cause.node = "PetSearch_AWS::ECS::Fargate" for the anomaly on PetSite latency; the fault injection command in metadata.reproducibility is "aws ssm put-parameter --name '/petstore/searchdelay' --value '500' --overwrite"
|
| 26 |
Check: Hide root_cause and metadata of target.json (keep target). Task: from metrics.csv and graph.csv the agent names the root cause node of the anomaly on the target node; pass on an exact string match with root_cause.node. A second task names the injected fault kind (delay or error rate) from the injection command; exact match
|
| 27 |
Companions (not included): dataset/high_traffic/graph.csv
|
| 28 |
Dependencies: none to read the data (CSV and JSON); the repository code is not used and not run.
|
| 29 |
- `dataset/low_traffic/train/issue_6/` (2 files): PetShop low traffic, train issue 6: service metrics around an availability anomaly with the injected root cause labelled.
|
| 30 |
Format: metrics.csv: CSV with a multi-row header (microservice, metric, aggregation) and one column per service metric, time stamps as rows; target.json: JSON with the anomalous target node, metric, aggregation and time stamp, the root cause node and the fault injection command; graph.csv: adjacency matrix of the service call graph
|
| 31 |
Origin: metrics recorded on a real deployment of the AWS pet adoption demo application with injected faults, published as a benchmark.
|
| 32 |
-
Reference result: labelled_root_cause
|
| 33 |
-
Reference source: target.json, root_cause.node = "PetSearch_AWS::ECS::Fargate" for the anomaly on PetSite availability; the fault injection command in metadata.reproducibility is "aws ssm put-parameter --name '/petstore/searcherrorpercent' --value '2' --overwrite"
|
| 34 |
Check: Hide root_cause and metadata of target.json (keep target). Task: from metrics.csv and graph.csv the agent names the root cause node of the anomaly on the target node; pass on an exact string match with root_cause.node. A second task names the injected fault kind (delay or error rate) from the injection command; exact match
|
| 35 |
Companions (not included): dataset/low_traffic/graph.csv
|
| 36 |
Dependencies: none to read the data (CSV and JSON); the repository code is not used and not run.
|
| 37 |
- `dataset/temporal_traffic1/train/issue_1/` (2 files): PetShop temporal traffic 1, train issue 1: service metrics under daily traffic patterns around an availability anomaly with the injected root cause labelled.
|
| 38 |
Format: metrics.csv: CSV with a multi-row header (microservice, metric, aggregation) and one column per service metric, time stamps as rows; target.json: JSON with the anomalous target node, metric, aggregation and time stamp, the root cause node and the fault injection command; graph.csv: adjacency matrix of the service call graph
|
| 39 |
Origin: metrics recorded on a real deployment of the AWS pet adoption demo application with injected faults, published as a benchmark.
|
| 40 |
-
Reference result: labelled_root_cause
|
| 41 |
-
Reference source: target.json, root_cause.node = "PetSearch_AWS::ECS::Fargate" for the anomaly on PetSite availability; the fault injection command in metadata.reproducibility is "aws ssm put-parameter --name '/petstore/searcherrorpercent' --value '3' --overwrite"
|
| 42 |
Check: Hide root_cause and metadata of target.json (keep target). Task: from metrics.csv and graph.csv the agent names the root cause node of the anomaly on the target node; pass on an exact string match with root_cause.node. A second task names the injected fault kind (delay or error rate) from the injection command; exact match
|
| 43 |
Companions (not included): dataset/temporal_traffic1/graph.csv
|
| 44 |
Dependencies: none to read the data (CSV and JSON); the repository code is not used and not run.
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether each unit needs other upstream files is not stated. 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:** Check: Hide root_cause and metadata of target.json (keep target). Task: from metrics.csv and graph.csv the agent names the root cause node of the anomaly on the target node; pass on an exact string match with root_cause.node. A second task names the injected fault kind (delay or error rate) from the injection command; exact match.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC-BY-4.0
|
|
|
|
| 19 |
- `dataset/high_traffic/train/issue_1/` (2 files): PetShop high traffic, train issue 1: service metrics of a microservice pet shop around a latency anomaly with the injected root cause labelled.
|
| 20 |
Format: metrics.csv: CSV with a multi-row header (microservice, metric, aggregation) and one column per service metric, time stamps as rows; target.json: JSON with the anomalous target node, metric, aggregation and time stamp, the root cause node and the fault injection command; graph.csv: adjacency matrix of the service call graph
|
| 21 |
Origin: metrics recorded on a real deployment of the AWS pet adoption demo application with injected faults, published as a benchmark.
|
|
|
|
|
|
|
| 22 |
Check: Hide root_cause and metadata of target.json (keep target). Task: from metrics.csv and graph.csv the agent names the root cause node of the anomaly on the target node; pass on an exact string match with root_cause.node. A second task names the injected fault kind (delay or error rate) from the injection command; exact match
|
| 23 |
Companions (not included): dataset/high_traffic/graph.csv
|
| 24 |
Dependencies: none to read the data (CSV and JSON); the repository code is not used and not run.
|
| 25 |
- `dataset/low_traffic/train/issue_6/` (2 files): PetShop low traffic, train issue 6: service metrics around an availability anomaly with the injected root cause labelled.
|
| 26 |
Format: metrics.csv: CSV with a multi-row header (microservice, metric, aggregation) and one column per service metric, time stamps as rows; target.json: JSON with the anomalous target node, metric, aggregation and time stamp, the root cause node and the fault injection command; graph.csv: adjacency matrix of the service call graph
|
| 27 |
Origin: metrics recorded on a real deployment of the AWS pet adoption demo application with injected faults, published as a benchmark.
|
|
|
|
|
|
|
| 28 |
Check: Hide root_cause and metadata of target.json (keep target). Task: from metrics.csv and graph.csv the agent names the root cause node of the anomaly on the target node; pass on an exact string match with root_cause.node. A second task names the injected fault kind (delay or error rate) from the injection command; exact match
|
| 29 |
Companions (not included): dataset/low_traffic/graph.csv
|
| 30 |
Dependencies: none to read the data (CSV and JSON); the repository code is not used and not run.
|
| 31 |
- `dataset/temporal_traffic1/train/issue_1/` (2 files): PetShop temporal traffic 1, train issue 1: service metrics under daily traffic patterns around an availability anomaly with the injected root cause labelled.
|
| 32 |
Format: metrics.csv: CSV with a multi-row header (microservice, metric, aggregation) and one column per service metric, time stamps as rows; target.json: JSON with the anomalous target node, metric, aggregation and time stamp, the root cause node and the fault injection command; graph.csv: adjacency matrix of the service call graph
|
| 33 |
Origin: metrics recorded on a real deployment of the AWS pet adoption demo application with injected faults, published as a benchmark.
|
|
|
|
|
|
|
| 34 |
Check: Hide root_cause and metadata of target.json (keep target). Task: from metrics.csv and graph.csv the agent names the root cause node of the anomaly on the target node; pass on an exact string match with root_cause.node. A second task names the injected fault kind (delay or error rate) from the injection command; exact match
|
| 35 |
Companions (not included): dataset/temporal_traffic1/graph.csv
|
| 36 |
Dependencies: none to read the data (CSV and JSON); the repository code is not used and not run.
|
campaign_files/2026-10-ml-serving-configs-2/github-intelligentdds-nezha/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_root_cause. Where the reference result comes from and how a solution is checked is written per unit in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Hide the fault list. For each of the 24 injections the agent gets the injection time and the metric files and names the faulty pod and the fault type; scored per injection by exact match on inject_pod and on inject_type (from the set cpu_contention, cpu_consumed, network_delay, return, exception), reported as counts.
|
| 14 |
|
| 15 |
**Licence (SPDX):** MIT
|
|
@@ -21,8 +19,6 @@ Units:
|
|
| 21 |
- `rca_data/2022-08-22/metric/` (14 files): Nezha OnlineBoutique fault day 2022-08-22: per-pod metrics of 10 microservices plus call-graph and latency files, with the service-level list of 24 injected faults (pod, fault type, time).
|
| 22 |
Format: metric/*_metric.csv: CSV per pod with a timestamp and container metrics (CPU, memory, network, latency); dependency.csv, source_50.csv, destination_50.csv, front_service.csv: call relations and front-end latency; fault_list.json: JSON keyed by hour, each entry inject_time, inject_timestamp, inject_pod, inject_type
|
| 23 |
Origin: real metrics recorded by the authors on OnlineBoutique deployed on Kubernetes with chaos injection, published as-is in the repository
|
| 24 |
-
Reference result: labelled_root_cause
|
| 25 |
-
Reference source: rca_data/2022-08-22/2022-08-22-fault_list.json, described in README.md line 120 as the service level label of root causes in OnlineBoutique
|
| 26 |
Check: Hide the fault list. For each of the 24 injections the agent gets the injection time and the metric files and names the faulty pod and the fault type; scored per injection by exact match on inject_pod and on inject_type (from the set cpu_contention, cpu_consumed, network_delay, return, exception), reported as counts
|
| 27 |
Companions (not included): rca_data/2022-08-22/2022-08-22-fault_list.json
|
| 28 |
Dependencies: none to read the data (CSV and JSON).
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the unit needs other upstream files is not stated. 1 of 1 units name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per unit in the notes. Dependencies named upstream are listed per unit in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Hide the fault list. For each of the 24 injections the agent gets the injection time and the metric files and names the faulty pod and the fault type; scored per injection by exact match on inject_pod and on inject_type (from the set cpu_contention, cpu_consumed, network_delay, return, exception), reported as counts.
|
| 12 |
|
| 13 |
**Licence (SPDX):** MIT
|
|
|
|
| 19 |
- `rca_data/2022-08-22/metric/` (14 files): Nezha OnlineBoutique fault day 2022-08-22: per-pod metrics of 10 microservices plus call-graph and latency files, with the service-level list of 24 injected faults (pod, fault type, time).
|
| 20 |
Format: metric/*_metric.csv: CSV per pod with a timestamp and container metrics (CPU, memory, network, latency); dependency.csv, source_50.csv, destination_50.csv, front_service.csv: call relations and front-end latency; fault_list.json: JSON keyed by hour, each entry inject_time, inject_timestamp, inject_pod, inject_type
|
| 21 |
Origin: real metrics recorded by the authors on OnlineBoutique deployed on Kubernetes with chaos injection, published as-is in the repository
|
|
|
|
|
|
|
| 22 |
Check: Hide the fault list. For each of the 24 injections the agent gets the injection time and the metric files and names the faulty pod and the fault type; scored per injection by exact match on inject_pod and on inject_type (from the set cpu_contention, cpu_consumed, network_delay, return, exception), reported as counts
|
| 23 |
Companions (not included): rca_data/2022-08-22/2022-08-22-fault_list.json
|
| 24 |
Dependencies: none to read the data (CSV and JSON).
|
campaign_files/2026-10-ml-serving-configs-2/github-markusthill-mgab/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_anomaly_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: Drop the columns is_anomaly and is_ignored before handing the series to the agent. Task: list the time indices where anomalies sit. A reported index counts as a hit when it falls inside a labelled anomaly window (is_anomaly = 1), each window counted once; reports inside the first 256 steps (is_ignored = 1) are not counted as false; scored as hits, misses and false reports out of the 10 windows.
|
| 14 |
|
| 15 |
**Licence (SPDX):** CC0-1.0
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `ml293-01/1.csv`: Mackey-Glass Anomaly Benchmark (MGAB) series 1: 100,000 chaotic Mackey-Glass values with 10 hard-to-see inserted anomalies, each labelled with a 400-point window.
|
| 22 |
Format: CSV, 100,000 rows, 4 columns: time index, value, is_anomaly (0/1, 400-point window per anomaly), is_ignored (1 for the first 256 steps)
|
| 23 |
Origin: synthetic series published as-is by the benchmark author (Mackey-Glass delay differential equation with segments cut out and stitched, README.md lines 43 to 61).
|
| 24 |
-
Reference result: labelled_anomaly_windows
|
| 25 |
-
Reference source: columns is_anomaly and is_ignored of 1.csv, written by the benchmark author (README.md lines 28 to 32)
|
| 26 |
Check: Drop the columns is_anomaly and is_ignored before handing the series to the agent. Task: list the time indices where anomalies sit. A reported index counts as a hit when it falls inside a labelled anomaly window (is_anomaly = 1), each window counted once; reports inside the first 256 steps (is_ignored = 1) are not counted as false; scored as hits, misses and false reports out of the 10 windows
|
| 27 |
Dependencies: none to read the data (plain CSV).
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Drop the columns is_anomaly and is_ignored before handing the series to the agent. Task: list the time indices where anomalies sit. A reported index counts as a hit when it falls inside a labelled anomaly window (is_anomaly = 1), each window counted once; reports inside the first 256 steps (is_ignored = 1) are not counted as false; scored as hits, misses and false reports out of the 10 windows.
|
| 12 |
|
| 13 |
**Licence (SPDX):** CC0-1.0
|
|
|
|
| 19 |
- `ml293-01/1.csv`: Mackey-Glass Anomaly Benchmark (MGAB) series 1: 100,000 chaotic Mackey-Glass values with 10 hard-to-see inserted anomalies, each labelled with a 400-point window.
|
| 20 |
Format: CSV, 100,000 rows, 4 columns: time index, value, is_anomaly (0/1, 400-point window per anomaly), is_ignored (1 for the first 256 steps)
|
| 21 |
Origin: synthetic series published as-is by the benchmark author (Mackey-Glass delay differential equation with segments cut out and stitched, README.md lines 43 to 61).
|
|
|
|
|
|
|
| 22 |
Check: Drop the columns is_anomaly and is_ignored before handing the series to the agent. Task: list the time indices where anomalies sit. A reported index counts as a hit when it falls inside a labelled anomaly window (is_anomaly = 1), each window counted once; reports inside the first 256 steps (is_ignored = 1) are not counted as false; scored as hits, misses and false reports out of the 10 windows
|
| 23 |
Dependencies: none to read the data (plain CSV).
|
campaign_files/2026-10-ml-serving-configs-2/github-thufdd-thu-concept-drift-datasets/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: labelled_drift_points. Where the reference result comes from and how a solution is checked is written per file in the notes.
|
| 12 |
-
|
| 13 |
**Tools to open and check:** Check: Hand the agent the CSV. Task: list the indices where the concept drifts. Judge each of the 4 true drift points (20000, 40000, 60000, 80000) as found when the agent reports the matching index exactly, or score detection delay as the distance from each true point to the first report after it.
|
| 14 |
|
| 15 |
**Licence (SPDX):** NOASSERTION
|
|
@@ -21,8 +19,6 @@ Files:
|
|
| 21 |
- `ml341-03/linear_sudden_rotation_noise_and_redunce.csv`: THU concept drift stream linear_sudden_rotation_noise_and_redunce.csv: 100,000 labelled points of a two-class linear stream with sudden rotation drifts, noise and redundant features.
|
| 22 |
Format: CSV, 100,000 rows of feature columns and a class label column
|
| 23 |
Origin: synthetic stream published as-is by the dataset authors.
|
| 24 |
-
Reference result: labelled_drift_points
|
| 25 |
-
Reference source: the drift positions fixed by the generator code: DataStreamGenerator.py line 398 `if i % (0.2 * self.sample_count) == 0 and i > 0:` with the default sample_count 100000 (line 18), so the concept changes at indices 20000, 40000, 60000 and 80000; checked here on the file: the class boundary changes at those indices
|
| 26 |
Check: Hand the agent the CSV. Task: list the indices where the concept drifts. Judge each of the 4 true drift points (20000, 40000, 60000, 80000) as found when the agent reports the matching index exactly, or score detection delay as the distance from each true point to the first report after it
|
| 27 |
Companions (not included): DataStreamGenerator.py
|
| 28 |
Dependencies: none to read the data (plain CSV).
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated. 1 of 1 files name companion files (other upstream files read alongside); companions are not included in this delivery and are listed per file in the notes. Dependencies named upstream are listed per file in the notes.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** Check: Hand the agent the CSV. Task: list the indices where the concept drifts. Judge each of the 4 true drift points (20000, 40000, 60000, 80000) as found when the agent reports the matching index exactly, or score detection delay as the distance from each true point to the first report after it.
|
| 12 |
|
| 13 |
**Licence (SPDX):** NOASSERTION
|
|
|
|
| 19 |
- `ml341-03/linear_sudden_rotation_noise_and_redunce.csv`: THU concept drift stream linear_sudden_rotation_noise_and_redunce.csv: 100,000 labelled points of a two-class linear stream with sudden rotation drifts, noise and redundant features.
|
| 20 |
Format: CSV, 100,000 rows of feature columns and a class label column
|
| 21 |
Origin: synthetic stream published as-is by the dataset authors.
|
|
|
|
|
|
|
| 22 |
Check: Hand the agent the CSV. Task: list the indices where the concept drifts. Judge each of the 4 true drift points (20000, 40000, 60000, 80000) as found when the agent reports the matching index exactly, or score detection delay as the distance from each true point to the first report after it
|
| 23 |
Companions (not included): DataStreamGenerator.py
|
| 24 |
Dependencies: none to read the data (plain CSV).
|
campaign_files/2026-10-ml-serving-configs-2/glibc-auto-libm-test-out/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. 8 of 8 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_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:** Tools are named in the check written per file in the notes.
|
| 14 |
|
| 15 |
**Licence (SPDX):** LGPL-2.1-or-later
|
|
@@ -21,64 +19,48 @@ Files:
|
|
| 21 |
- `math/auto-libm-test-out-erf`: Glibc libm test vectors for erf: 3408 expected-result lines (80 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 22 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 23 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
| 24 |
-
Reference result: expected_output_values
|
| 25 |
-
Reference source: the outputs and flags on each = line of math/auto-libm-test-out-erf, computed by math/gen-auto-libm-tests.c with mpfr_erf (correct rounding in each of the 4 rounding modes; table entry at gen-auto-libm-tests.c line 576)
|
| 26 |
Check: For each = line, set the rounding mode, call the implementation of erf under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 27 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 28 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 29 |
- `math/auto-libm-test-out-tgamma`: Glibc libm test vectors for tgamma: 27176 expected-result lines (499 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 30 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 31 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
| 32 |
-
Reference result: expected_output_values
|
| 33 |
-
Reference source: the outputs and flags on each = line of math/auto-libm-test-out-tgamma, computed by math/gen-auto-libm-tests.c with mpfr_gamma (correct rounding in each of the 4 rounding modes; table entry at gen-auto-libm-tests.c line 616)
|
| 34 |
Check: For each = line, set the rounding mode, call the implementation of tgamma under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 35 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 36 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 37 |
- `math/auto-libm-test-out-hypot`: Glibc libm test vectors for hypot: 14736 expected-result lines (56 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 38 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 39 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
| 40 |
-
Reference result: expected_output_values
|
| 41 |
-
Reference source: the outputs and flags on each = line of math/auto-libm-test-out-hypot, computed by math/gen-auto-libm-tests.c with mpfr_hypot (correct rounding in each of the 4 rounding modes; table entry at gen-auto-libm-tests.c line 586)
|
| 42 |
Check: For each = line, set the rounding mode, call the implementation of hypot under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 43 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 44 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 45 |
- `math/auto-libm-test-out-pow`: Glibc libm test vectors for pow: 43756 expected-result lines (536 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 46 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 47 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
| 48 |
-
Reference result: expected_output_values
|
| 49 |
-
Reference source: the outputs and flags on each = line of math/auto-libm-test-out-pow, computed by math/gen-auto-libm-tests.c with mpfr_pow (correct rounding in each of the 4 rounding modes; table entry at gen-auto-libm-tests.c line 599)
|
| 50 |
Check: For each = line, set the rounding mode, call the implementation of pow under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 51 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 52 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 53 |
- `math/auto-libm-test-out-fma`: Glibc libm test vectors for fma: 15384 expected-result lines (263 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 54 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 55 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
| 56 |
-
Reference result: expected_output_values
|
| 57 |
-
Reference source: the outputs and flags on each = line of math/auto-libm-test-out-fma, computed by math/gen-auto-libm-tests.c with mpfr_fma (correct rounding in each of the 4 rounding modes; table entry at gen-auto-libm-tests.c line 584)
|
| 58 |
Check: For each = line, set the rounding mode, call the implementation of fma under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130); the function is exactly determined, so results and exceptions must be exact (gen-auto-libm-tests.c lines 483-484 and the true flag at line 584)
|
| 59 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 60 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 61 |
- `math/auto-libm-test-out-rsqrt`: Glibc libm test vectors for rsqrt: 3936 expected-result lines (79 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 62 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 63 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
| 64 |
-
Reference result: expected_output_values
|
| 65 |
-
Reference source: the outputs and flags on each = line of math/auto-libm-test-out-rsqrt, computed by math/gen-auto-libm-tests.c with mpfr_rec_sqrt (correct rounding in each of the 4 rounding modes; table entry at gen-auto-libm-tests.c line 605)
|
| 66 |
Check: For each = line, set the rounding mode, call the implementation of rsqrt under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130); the function is exactly determined, so results and exceptions must be exact (gen-auto-libm-tests.c lines 483-484 and the true flag at line 605)
|
| 67 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 68 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 69 |
- `math/auto-libm-test-out-exp2`: Glibc libm test vectors for exp2: 4160 expected-result lines (102 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 70 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 71 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
| 72 |
-
Reference result: expected_output_values
|
| 73 |
-
Reference source: the outputs and flags on each = line of math/auto-libm-test-out-exp2, computed by math/gen-auto-libm-tests.c with mpfr_exp2 (correct rounding in each of the 4 rounding modes; table entry at gen-auto-libm-tests.c line 581)
|
| 74 |
Check: For each = line, set the rounding mode, call the implementation of exp2 under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 75 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 76 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 77 |
- `math/auto-libm-test-out-log2`: Glibc libm test vectors for log2: 2064 expected-result lines (34 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 78 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 79 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
| 80 |
-
Reference result: expected_output_values
|
| 81 |
-
Reference source: the outputs and flags on each = line of math/auto-libm-test-out-log2, computed by math/gen-auto-libm-tests.c with mpfr_log2 (correct rounding in each of the 4 rounding modes; table entry at gen-auto-libm-tests.c line 596)
|
| 82 |
Check: For each = line, set the rounding mode, call the implementation of log2 under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 83 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 84 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Not self-contained: each file is used together with other files from the same upstream. 8 of 8 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:** Tools are named in the check written per file in the notes.
|
| 12 |
|
| 13 |
**Licence (SPDX):** LGPL-2.1-or-later
|
|
|
|
| 19 |
- `math/auto-libm-test-out-erf`: Glibc libm test vectors for erf: 3408 expected-result lines (80 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 20 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 21 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
|
|
|
|
|
|
| 22 |
Check: For each = line, set the rounding mode, call the implementation of erf under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 23 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 24 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 25 |
- `math/auto-libm-test-out-tgamma`: Glibc libm test vectors for tgamma: 27176 expected-result lines (499 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 26 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 27 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
|
|
|
|
|
|
| 28 |
Check: For each = line, set the rounding mode, call the implementation of tgamma under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 29 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 30 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 31 |
- `math/auto-libm-test-out-hypot`: Glibc libm test vectors for hypot: 14736 expected-result lines (56 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 32 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 33 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
|
|
|
|
|
|
| 34 |
Check: For each = line, set the rounding mode, call the implementation of hypot under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 35 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 36 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 37 |
- `math/auto-libm-test-out-pow`: Glibc libm test vectors for pow: 43756 expected-result lines (536 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 38 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 39 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
|
|
|
|
|
|
| 40 |
Check: For each = line, set the rounding mode, call the implementation of pow under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 41 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 42 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 43 |
- `math/auto-libm-test-out-fma`: Glibc libm test vectors for fma: 15384 expected-result lines (263 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 44 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 45 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
|
|
|
|
|
|
| 46 |
Check: For each = line, set the rounding mode, call the implementation of fma under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130); the function is exactly determined, so results and exceptions must be exact (gen-auto-libm-tests.c lines 483-484 and the true flag at line 584)
|
| 47 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 48 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 49 |
- `math/auto-libm-test-out-rsqrt`: Glibc libm test vectors for rsqrt: 3936 expected-result lines (79 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 50 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 51 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
|
|
|
|
|
|
| 52 |
Check: For each = line, set the rounding mode, call the implementation of rsqrt under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130); the function is exactly determined, so results and exceptions must be exact (gen-auto-libm-tests.c lines 483-484 and the true flag at line 605)
|
| 53 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 54 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 55 |
- `math/auto-libm-test-out-exp2`: Glibc libm test vectors for exp2: 4160 expected-result lines (102 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 56 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 57 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
|
|
|
|
|
|
| 58 |
Check: For each = line, set the rounding mode, call the implementation of exp2 under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 59 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 60 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
| 61 |
- `math/auto-libm-test-out-log2`: Glibc libm test vectors for log2: 2064 expected-result lines (34 test inputs expanded over 4 rounding modes and up to 6 floating point formats), correctly rounded by MPFR, with exception and errno flags.
|
| 62 |
Format: plain text: comment lines start with #, input lines repeat the auto-libm-test-in test, each output line has the form = function rounding-mode format inputs : outputs : flags, values as C hex floats (gen-auto-libm-tests.c lines 110-130)
|
| 63 |
Origin: test data of the GNU C Library math test suite, generated with MPFR
|
|
|
|
|
|
|
| 64 |
Check: For each = line, set the rounding mode, call the implementation of log2 under test in the named format on the hex inputs, and compare with the expected output; glibc's driver does not report differences up to the allowed ULP count as a regression (math/README.libm-test lines 45-47), checks the listed exceptions and errno values, skips lines flagged xfail and ignores the ones marked -ok (gen-auto-libm-tests.c lines 96-100 and 122-130)
|
| 65 |
Companions (not included): math/README.libm-test; math/gen-auto-libm-tests.c; README; COPYING.LESSERv2
|
| 66 |
Dependencies: MPFR and MPC. the libm implementation under test.
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-1411-4/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol14/xml/CFR-2025-title26-vol14-sec1-1411-4.xml`: US net investment income (26 CFR 1.1411-4, 2025 edition), with worked examples of net gain and allocable deductions.
|
| 22 |
Format: CFR section XML, 89,032 bytes; rules plus about 25 examples
|
| 23 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the Example paragraphs, for instance: "A's net gain for Year 1 is $17,000" and "D must nonetheless reduce Year 3's section 1411(c)(1)(B) properly allocable deductions by $1,000 ($5,000 x ($15,000/$75,000))"
|
| 26 |
Check: give the agent one example's facts and the section's rules; it reports the amount the example prints (net gain, net investment income, reduction of deductions); pass when it equals the printed whole-dollar figure; examples that only classify income without an amount are not used
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol14/xml/CFR-2025-title26-vol14-sec1-1411-4.xml`: US net investment income (26 CFR 1.1411-4, 2025 edition), with worked examples of net gain and allocable deductions.
|
| 20 |
Format: CFR section XML, 89,032 bytes; rules plus about 25 examples
|
| 21 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts and the section's rules; it reports the amount the example prints (net gain, net investment income, reduction of deductions); pass when it equals the printed whole-dollar figure; examples that only classify income without an amount are not used
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-170a-4/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol4/xml/CFR-2025-title26-vol4-sec1-170A-4.xml`: US reductions of charitable contributions of appreciated property (26 CFR 1.170A-4, 2025 edition), with 10 worked examples.
|
| 22 |
Format: CFR section XML, 38,730 bytes; rules plus 10 examples
|
| 23 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the Example paragraphs, for instance Example 3: "D's contribution is reduced by $35,000 (100 percent of the ordinary income of $20,000 and 50 percent of the long-term capital gain of $30,000)"
|
| 26 |
Check: give the agent one example's facts (fair market value, basis, holding period, donee, contribution base) and the section's rules; it reports the reduction, the deductible amount and any carryover the example prints; pass when every amount equals the printed whole-dollar figure; the facts are for the 1970s tax years the examples name, so the agent uses the percentages stated in the section
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol4/xml/CFR-2025-title26-vol4-sec1-170A-4.xml`: US reductions of charitable contributions of appreciated property (26 CFR 1.170A-4, 2025 edition), with 10 worked examples.
|
| 20 |
Format: CFR section XML, 38,730 bytes; rules plus 10 examples
|
| 21 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (fair market value, basis, holding period, donee, contribution base) and the section's rules; it reports the reduction, the deductible amount and any carryover the example prints; pass when every amount equals the printed whole-dollar figure; the facts are for the 1970s tax years the examples name, so the agent uses the percentages stated in the section
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-199a-1/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol4/xml/CFR-2025-title26-vol4-sec1-199A-1.xml`: US qualified business income deduction (26 CFR 1.199A-1, 2025 edition), with many worked examples.
|
| 22 |
Format: CFR section XML, 53,565 bytes; rules plus numbered examples in paragraphs (c) and (d)
|
| 23 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the Example paragraphs, for instance: "Twenty percent of the $4,000,000 of QBI is $800,000. Two and one-half percent of the $10,000,000 UBIA of qualified property is $250,000"
|
| 26 |
Check: give the agent one example's facts (QBI, W-2 wages, UBIA, taxable income, filing status) and the section's rules; it reports the section 199A deduction and the intermediate components the example prints; pass when every amount equals the printed whole-dollar figure
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol4/xml/CFR-2025-title26-vol4-sec1-199A-1.xml`: US qualified business income deduction (26 CFR 1.199A-1, 2025 edition), with many worked examples.
|
| 20 |
Format: CFR section XML, 53,565 bytes; rules plus numbered examples in paragraphs (c) and (d)
|
| 21 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (QBI, W-2 wages, UBIA, taxable income, filing status) and the section's rules; it reports the section 199A deduction and the intermediate components the example prints; pass when every amount equals the printed whole-dollar figure
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-280f-7/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol4/xml/CFR-2025-title26-vol4-sec1-280F-7.xml`: US lease inclusion amounts for listed property and leased cars (26 CFR 1.280F-7, 2025 edition), with the section's own percentage tables and worked examples.
|
| 22 |
Format: CFR section XML, 39,163 bytes; rules, percentage tables and worked examples
|
| 23 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the examples, for instance: "B's inclusion amount is $154 ... The amount determined under subdivision (i) is -$86 [$3,000 x 40% x (-7.2%)], and the amount determined under subdivision (ii) is $240"
|
| 26 |
Check: give the agent one example's facts (fair market value, lease dates, business-use percentages) and the section with its tables; it reports the inclusion amount and its parts; pass when each amount equals the printed whole-dollar figure
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol4/xml/CFR-2025-title26-vol4-sec1-280F-7.xml`: US lease inclusion amounts for listed property and leased cars (26 CFR 1.280F-7, 2025 edition), with the section's own percentage tables and worked examples.
|
| 20 |
Format: CFR section XML, 39,163 bytes; rules, percentage tables and worked examples
|
| 21 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (fair market value, lease dates, business-use percentages) and the section with its tables; it reports the inclusion amount and its parts; pass when each amount equals the printed whole-dollar figure
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-36b-3/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol1/xml/CFR-2025-title26-vol1-sec1-36B-3.xml`: US premium tax credit computation (26 CFR 1.36B-3, 2025 edition), with worked examples.
|
| 22 |
Format: CFR section XML, 56,482 bytes; rules plus numbered examples
|
| 23 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the Example paragraphs, for instance: "Q's premium assistance amount for a coverage month is $400 (the lesser of $400, Q's monthly enrollment premium, and $420 ...)"
|
| 26 |
Check: give the agent one example's facts (enrollment premium, benchmark premium, contribution amount, household) and the section's rules; it reports the premium assistance amount; pass when it equals the printed whole-dollar figure
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol1/xml/CFR-2025-title26-vol1-sec1-36B-3.xml`: US premium tax credit computation (26 CFR 1.36B-3, 2025 edition), with worked examples.
|
| 20 |
Format: CFR section XML, 56,482 bytes; rules plus numbered examples
|
| 21 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (enrollment premium, benchmark premium, contribution amount, household) and the section's rules; it reports the premium assistance amount; pass when it equals the printed whole-dollar figure
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-61-21/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol2/xml/CFR-2025-title26-vol2-sec1-61-21.xml`: US valuation of taxable fringe benefits (26 CFR 1.61-21, 2025 edition), with the annual lease value table and worked examples.
|
| 22 |
Format: CFR section XML, 171,346 bytes; rules, the Annual Lease Value Table and about 27 examples
|
| 23 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the Example paragraphs, for instance: "The maximum amount subject to inclusion in A's gross income for use of the automobile and chauffeur is therefore $24,250 ($12,000 + $3,000 + $9,250)"
|
| 26 |
Check: give the agent one example's facts (vehicle value, business use, mileage, flight details) and the section with its tables; it reports the amount includible in income the example prints; pass when it equals the printed figure exactly
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol2/xml/CFR-2025-title26-vol2-sec1-61-21.xml`: US valuation of taxable fringe benefits (26 CFR 1.61-21, 2025 edition), with the annual lease value table and worked examples.
|
| 20 |
Format: CFR section XML, 171,346 bytes; rules, the Annual Lease Value Table and about 27 examples
|
| 21 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (vehicle value, business use, mileage, flight details) and the section with its tables; it reports the amount includible in income the example prints; pass when it equals the printed figure exactly
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1-72-4/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol2/xml/CFR-2025-title26-vol2-sec1-72-4.xml`: US annuity exclusion ratio and excludable amounts (26 CFR 1.72-4, 2025 edition), with worked examples.
|
| 22 |
Format: CFR section XML, 29,561 bytes; rule text plus about 6 worked examples
|
| 23 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the examples, for instance: "the exclusion ratio to be used by A is $12,650 / 16,000; or 79.1 percent (79.06 rounded to the nearest tenth) ... $949.20 ($1,200 x 79.1 percent)"
|
| 26 |
Check: give the agent one example's facts (investment in the contract, expected return, payments received) and the section's rule; it reports the exclusion ratio and the excludable and includible amounts; pass when the ratio equals the printed percentage to one decimal and each amount equals the printed figure to the cent
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol2/xml/CFR-2025-title26-vol2-sec1-72-4.xml`: US annuity exclusion ratio and excludable amounts (26 CFR 1.72-4, 2025 edition), with worked examples.
|
| 20 |
Format: CFR section XML, 29,561 bytes; rule text plus about 6 worked examples
|
| 21 |
Origin: official text published by Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (investment in the contract, expected return, payments received) and the section's rule; it reports the exclusion ratio and the excludable and includible amounts; pass when the ratio equals the printed percentage to one decimal and each amount equals the printed figure to the cent
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1001-2/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1001-2.xml`: US discharge of liabilities on sale or transfer: amount realized including recourse and nonrecourse liabilities and partnership liability shares (26 CFR 1.1001-2, 2025 edition), with worked amounts.
|
| 22 |
Format: CFR section XML, 12,648 bytes; rule text plus 8 numbered examples
|
| 23 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the examples in paragraph (c), for instance: "A's amount realized is $9,200 ($1,600 + $7,600). Since A's adjusted basis in the asset is $6,900 ($10,000 − $3,100) A realizes a gain of $2,300 ($9,200 − $6,900)"
|
| 26 |
Check: give the agent one example's facts (cost, depreciation, liability outstanding and its kind, cash paid, share of partnership liabilities) and the section's rule; it reports the amount realized and the gain or loss realized (and any discharge income where the example states one); pass when each equals the printed figure exactly in whole dollars
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1001-2.xml`: US discharge of liabilities on sale or transfer: amount realized including recourse and nonrecourse liabilities and partnership liability shares (26 CFR 1.1001-2, 2025 edition), with worked amounts.
|
| 20 |
Format: CFR section XML, 12,648 bytes; rule text plus 8 numbered examples
|
| 21 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (cost, depreciation, liability outstanding and its kind, cash paid, share of partnership liabilities) and the section's rule; it reports the amount realized and the gain or loss realized (and any discharge income where the example states one); pass when each equals the printed figure exactly in whole dollars
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1011-2/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1011-2.xml`: US bargain sale to a charity: allocation of adjusted basis between the sale and the gift, and the reduced charitable deduction (26 CFR 1.1011-2, 2025 edition), with worked amounts.
|
| 22 |
Format: CFR section XML, 20,644 bytes; rule text plus 8 or more numbered examples
|
| 23 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source; the examples apply the 1970 deduction limits; a task must name the example's year
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the examples in paragraph (c), for instance: "the adjusted basis for determining gain on the bargain sale is $1,600 ($4,000 adjusted basis × $4,000 amount realized / $10,000 value of property). A has recognized long-term capital gain of $2,400"
|
| 26 |
Check: give the agent one example's facts (amount realized, adjusted basis, fair market value, contribution base, other gifts, the donee's kind) and the section's rule; it reports the basis allocated to the sale, the recognized gain and the charitable contribution amount where the example states one; pass when each equals the printed figure exactly in whole dollars
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1011-2.xml`: US bargain sale to a charity: allocation of adjusted basis between the sale and the gift, and the reduced charitable deduction (26 CFR 1.1011-2, 2025 edition), with worked amounts.
|
| 20 |
Format: CFR section XML, 20,644 bytes; rule text plus 8 or more numbered examples
|
| 21 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source; the examples apply the 1970 deduction limits; a task must name the example's year
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (amount realized, adjusted basis, fair market value, contribution base, other gifts, the donee's kind) and the section's rule; it reports the basis allocated to the sale, the recognized gain and the charitable contribution amount where the example states one; pass when each equals the printed figure exactly in whole dollars
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1245-1/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1245-1.xml`: US depreciation recapture on section 1245 property: gain treated as ordinary income from recomputed basis (26 CFR 1.1245-1, 2025 edition), with worked amounts.
|
| 22 |
Format: CFR section XML, 41,129 bytes; rule text plus numbered examples in several paragraphs
|
| 23 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the examples in paragraph (b), for instance: "the excess of recomputed basis over adjusted basis, or $1,300, is treated as ordinary income under section 1245(a)(1). The remaining $400 of the gain may be treated as gain from the sale or exchange of property described in section 1231"
|
| 26 |
Check: give the agent one example's facts (basis, depreciation taken, amount realized or fair market value, kind of disposition) and the section's rule; it reports the gain realized, the ordinary income under section 1245(a)(1) and any remaining gain; pass when each equals the printed figure exactly in whole dollars
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1245-1.xml`: US depreciation recapture on section 1245 property: gain treated as ordinary income from recomputed basis (26 CFR 1.1245-1, 2025 edition), with worked amounts.
|
| 20 |
Format: CFR section XML, 41,129 bytes; rule text plus numbered examples in several paragraphs
|
| 21 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (basis, depreciation taken, amount realized or fair market value, kind of disposition) and the section's rule; it reports the gain realized, the ordinary income under section 1245(a)(1) and any remaining gain; pass when each equals the printed figure exactly in whole dollars
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1250-1/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1250-1.xml`: US depreciation recapture on section 1250 real property: applicable percentages and gain split between section 1250(a)(1), 1250(a)(2) and section 1231 (26 CFR 1.1250-1, 2025 edition), with worked amounts.
|
| 22 |
Format: CFR section XML, 52,905 bytes; rule text plus numbered examples in several paragraphs
|
| 23 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source; the examples apply the 1964 to 1987 rules with their period split at 1970; a task must state the example's dates
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the examples in paragraphs (a) and (b), for instance: "the amount of gain recognized as ordinary income under section 1250(a)(1) is $19,000 (that is, 95 percent of $20,000) ... is $6,000 (that is, 15 percent of $40,000)"
|
| 26 |
Check: give the agent one example's facts (adjusted basis, amount realized, additional depreciation by period, applicable percentages as the example states them) and the section's rule; it reports the ordinary income under each subsection and the remaining section 1231 gain; pass when each equals the printed figure exactly in whole dollars
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1250-1.xml`: US depreciation recapture on section 1250 real property: applicable percentages and gain split between section 1250(a)(1), 1250(a)(2) and section 1231 (26 CFR 1.1250-1, 2025 edition), with worked amounts.
|
| 20 |
Format: CFR section XML, 52,905 bytes; rule text plus numbered examples in several paragraphs
|
| 21 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source; the examples apply the 1964 to 1987 rules with their period split at 1970; a task must state the example's dates
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (adjusted basis, amount realized, additional depreciation by period, applicable percentages as the example states them) and the section's rule; it reports the ordinary income under each subsection and the remaining section 1231 gain; pass when each equals the printed figure exactly in whole dollars
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1250-2/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1250-2.xml`: US additional depreciation on section 1250 property: actual depreciation over straight line, year by year, with deficits carried between periods (26 CFR 1.1250-2, 2025 edition), with worked tables.
|
| 22 |
Format: CFR section XML, 38,485 bytes; rule text plus 5 or more numbered examples, some with year-by-year tables
|
| 23 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source; the examples apply rules for property held across 1963 to 1988; a task must state the example's dates
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the examples in paragraphs (b) and (c), for instance the table ending "Sum for periods after Dec. 31, 1963 ... 4,723 ... 3,600 ... 1,123" and "the amount of gain recognized under section 1250(a)(2) is $3,600 (that is, 12 percent of $30,000)"
|
| 26 |
Check: give the agent one example's facts (cost, method, rate, useful life, salvage value, dates, or the stated additional depreciation by period) and the section's rule; it reports the year-by-year depreciation and the additional depreciation, or the recognized gain; pass when each equals the printed figure exactly in whole dollars
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1250-2.xml`: US additional depreciation on section 1250 property: actual depreciation over straight line, year by year, with deficits carried between periods (26 CFR 1.1250-2, 2025 edition), with worked tables.
|
| 20 |
Format: CFR section XML, 38,485 bytes; rule text plus 5 or more numbered examples, some with year-by-year tables
|
| 21 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source; the examples apply rules for property held across 1963 to 1988; a task must state the example's dates
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (cost, method, rate, useful life, salvage value, dates, or the stated additional depreciation by period) and the section's rule; it reports the year-by-year depreciation and the additional depreciation, or the recognized gain; pass when each equals the printed figure exactly in whole dollars
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1272-1/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1272-1.xml`: US original issue discount: constant yield accrual by accrual period, yield conversion between compounding periods, daily portions (26 CFR 1.1272-1, 2025 edition), with worked amounts to the cent.
|
| 22 |
Format: CFR section XML, 45,620 bytes; rule text plus numbered examples
|
| 23 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the examples in paragraph (j), for instance: "the OID allocable to the first semiannual accrual period is $27,022.56 ... The daily portion of OID for the first semiannual accrual period is $150.13 ($27,022.56/180)"
|
| 26 |
Check: give the agent one example's facts (issue price, payments and dates, chosen accrual periods) and the section's rule, stating the example conventions; it reports the yield, the OID for the named accrual periods and the daily portions; pass when each money amount equals the printed figure to the cent
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1272-1.xml`: US original issue discount: constant yield accrual by accrual period, yield conversion between compounding periods, daily portions (26 CFR 1.1272-1, 2025 edition), with worked amounts to the cent.
|
| 20 |
Format: CFR section XML, 45,620 bytes; rule text plus numbered examples
|
| 21 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (issue price, payments and dates, chosen accrual periods) and the section's rule, stating the example conventions; it reports the yield, the OID for the named accrual periods and the daily portions; pass when each money amount equals the printed figure to the cent
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1367-1/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1367-1.xml`: US S corporation shareholder stock basis: per-share increases and decreases, ordering rules before and after 1997 (26 CFR 1.1367-1, 2025 edition), with worked per-share bases.
|
| 22 |
Format: CFR section XML, 21,937 bytes; rule text plus 5 or more numbered examples
|
| 23 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the examples in paragraph (g), for instance: "A has a basis of $3 per share in his original block of 50 shares ($6 + $3−$5−$1) and a basis of $5 per share in the second block of 50 shares ($8 + $3−$5−$1)"
|
| 26 |
Check: give the agent one example's facts (blocks of shares and their basis, pass-through items by kind, distributions, the taxable year) and the section's rule; it reports the basis per share of each block at year end; pass when each equals the printed figure exactly
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1367-1.xml`: US S corporation shareholder stock basis: per-share increases and decreases, ordering rules before and after 1997 (26 CFR 1.1367-1, 2025 edition), with worked per-share bases.
|
| 20 |
Format: CFR section XML, 21,937 bytes; rule text plus 5 or more numbered examples
|
| 21 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (blocks of shares and their basis, pass-through items by kind, distributions, the taxable year) and the section's rule; it reports the basis per share of each block at year end; pass when each equals the printed figure exactly
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
campaign_files/2026-10-op-rule-calculations-2/govinfo-cfr-26-1377-1/README.md
CHANGED
|
@@ -8,8 +8,6 @@
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
| 11 |
-
**Answers:** No answer files are included. Reference result: official_worked_examples. 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:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 14 |
|
| 15 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
@@ -21,7 +19,5 @@ Files:
|
|
| 21 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1377-1.xml`: US S corporation pro rata share: per-share, per-day allocation of income on partial disposition, terminating election and trust conversion (26 CFR 1.1377-1, 2025 edition), with worked amounts.
|
| 22 |
Format: CFR section XML, 19,734 bytes; rule text plus 3 numbered examples
|
| 23 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
| 24 |
-
Reference result: official_worked_examples
|
| 25 |
-
Reference source: the examples in paragraph (c), for instance: "B's pro rata share of X's nonseparately computed income for 1997 is $280,000 (($1,000 × 200 days) + ($500 × 160 days))" and "$49,727 ($100,000 × 182 days/366 days)"
|
| 26 |
Check: give the agent one example's facts (dates, shares held, income of the year or of each part year) and the section's rule; it reports each shareholder's pro rata share; pass when each equals the printed figure in whole dollars
|
| 27 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
|
|
|
| 8 |
|
| 9 |
**Self-contained:** Whether the file needs other upstream files is not stated.
|
| 10 |
|
|
|
|
|
|
|
| 11 |
**Tools to open and check:** a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|
| 12 |
|
| 13 |
**Licence (SPDX):** LicenseRef-US-Government-Work
|
|
|
|
| 19 |
- `content/pkg/CFR-2025-title26-vol13/xml/CFR-2025-title26-vol13-sec1-1377-1.xml`: US S corporation pro rata share: per-share, per-day allocation of income on partial disposition, terminating election and trust conversion (26 CFR 1.1377-1, 2025 edition), with worked amounts.
|
| 20 |
Format: CFR section XML, 19,734 bytes; rule text plus 3 numbered examples
|
| 21 |
Origin: official text published by US Department of the Treasury, Internal Revenue Service (via GovInfo, Office of the Federal Register); the worked examples and their results are printed in the source
|
|
|
|
|
|
|
| 22 |
Check: give the agent one example's facts (dates, shares held, income of the year or of each part year) and the section's rule; it reports each shareholder's pro rata share; pass when each equals the printed figure in whole dollars
|
| 23 |
Tools: a Python script, or an .xlsx file written with openpyxl, that applies the rule step by step to the example's facts and prints the amount
|