S2 pilot handover¶
AMČR colleagues run the six ATRIUM services themselves in the S2 pilot, from December 2026 to January 2027. This page is where the handover starts: which images, which runbook for each, what to watch for, and whom to ask. It follows the handover rules of the acceptance runbook. What each service does with the documents, in plain words: For archives. What is measured and what is experimental: Status.
The six services¶
The versions below are the pilot set, one release per tool, final since 4 November
(#77). Each tool's command line and service
give the same results from the same input; what still differs, and why, is in one table in each tool's
docs/usage.md.
11 November is the target for choosing and approving the six -api images. AMČR approves each one
explicitly, by digest, and the digest is entered here once approved. Until then the column stays empty,
and latest or test are never the baseline. Acceptance on AMČR's cluster follows separately (below).
| Stage | Image | Release | Approved digest | Runbook | Issues |
|---|---|---|---|---|---|
| page categories | ghcr.io/ufal/atrium-page-classification-api |
1.12.3-beta |
— | service/README.md | tracker |
| OCR output and text files → lines | ghcr.io/ufal/atrium-ocr-postprocess-api |
1.15.3-beta |
— | service/README.md | tracker |
| born-digital files → the record | ghcr.io/ufal/atrium-digital-convert-api |
1.4.4-beta |
— | service/README.md | tracker |
| morphology, named entities, TEITOK | ghcr.io/ufal/atrium-nlp-enrich-api |
1.3.3-beta |
— | service/README.md | tracker |
| keywords | ghcr.io/ufal/atrium-keyword-extract-api |
1.6.4-beta |
— | service/README.md | tracker |
| English metadata | ghcr.io/ufal/atrium-translator-api |
1.7.5-beta |
— | service/README.md | tracker |
For operators: finding a digest.
- Each release lists the digest of every image it published in its
images.jsonasset. The image tag is the release without its leadingv. - Read a digest from that file, or with
docker buildx imagetools inspect <image>:<tag>. - Every end-to-end run records the digest and source of each image it ran (
e2e-manifest.json, an artifact of the run). A green run at these release tags shows which releases passed together. - The end-to-end lanes run the batch images for most stages. The digests to approve are still those of
the
-apiimages of the same releases.
Before you rely on a result¶
Each runbook has a Known limits section. These are the ones a pilot user meets first:
- ocr-postprocess scores language and quality line by line; its rules are tuned for Czech, so lines in other languages are scored less reliably.
- translator refuses a language pair its backend has no model for (422,
cause: unsupported_language_pair) rather than routing it through another language; by default it calls LINDAT, whose output terms are open under #78. - digital-convert reads born-digital files only: a PDF that carries an OCR text layer is refused, and pages whose text was extracted damaged are flagged for OCR. Its upload limit is 250 MB; a deployment can raise it for larger originals, but files up to 1.5 GB are not yet tested for memory, concurrency and timeouts.
- keyword-extract's vocabulary-controlled kind is experimental and not evaluated; its statistical kind needs no backend.
- page-classification classifies at most
MAX_PDF_PAGESpages of a PDF per request (default 50); set it to the longest report when it runs behind digital-convert's/describe. - nlp-enrich calls LINDAT's UDPipe and NameTag. Its
/jobsare kept in memory: a restart loses them, and the caller submits a lost job again (accepted for the S2 pilot).
Acceptance¶
AMČR's acceptance on its own cluster is planned for the second half of November, before the December pilot, coordinated with @rharasim. The procedure and its results table are in the Kubernetes acceptance runbook. The table has one row per service: the digest each pod ran and what each check printed, and for the translator a run on real AMČR metadata. The completed table is linked here when AMČR returns it.
Contacts¶
| Role | Who |
|---|---|
| the six tools, their releases and runbooks | @K4TEL |
| LINDAT services; ÚFAL repository settings | @stranak |
| AMČR pilot lead | @motyc |
| AMČR acceptance on the cluster | @rharasim |
Further AMČR contacts are added as AMČR names them. Questions go to the issue tracker of the service concerned, or to #77 for the handover as a whole.