yamaa As a clinical trial statistician or programmer, challenge anything in this benchmark: describe a problem in Comments, or propose a fix with the Edit button on any source file.
- Task: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
- Inputs: Do they trigger the failure for the reason the summary gives?
- Expected failure: Is this the right error, raised at the right point, and would it tell the programmer what to fix?
The other tabs beside Comments are background for assessment, not under review.
Summary
EditUnder reviewWhat this benchmark meansREADME.mdGoal: carry the site name (SITENM) onto a subject listing.
Input: collected demographics carrying SITENM.
Variables:
SITENMwould be the name of the site the subject enrolled at, taken from the collected value.
One stored site name holds a byte written in an older encoding, which is not valid UTF-8 text. Replacing the byte with a substitute character would store a name the study never recorded, and dropping it would store a different name again, so the run is rejected while the file is read and no artifact is accepted.
How to fix
Export the listing as UTF-8, so every collected character keeps the value it
was entered with. The second site name then stores its accented letter (o
with circumflex, U+00F4) as the two bytes C3 B4 instead of the single byte
F4 that the older encoding wrote.
Converting a file after the fact is safe only while the original encoding is known. A study that stores names in an unstated encoding cannot say which letters it collected.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- ingest
- condition
- invalid_text
- requirement
- REQ-0853
expected/error.yaml
phase: ingest
condition: invalid_text
spec_paths:
- input.DM.path
requirement: REQ-0853
context:
dataset: DM
path: input/dm.csv
record: 3
field: 3
Inputs
Under review1 source fileinput/dm.csv
Editraw CSVShowing raw CSV because the source is not a valid rectangular table.
Binary fixture; inspect it in the benchmark source.
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Comments and assessment materials
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADSL | STUDYID | Study Identifier | character | Copy value from DM.STUDYID. | Predecessor | ||
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from DM.USUBJID. | Predecessor | ||
| ADSL | SITENM | Study Site Name | character | Copy value from DM.SITENM. | Predecessor |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 1.3 | 2026-09-29 | yamaa docs build | Show study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata | ||
| 1.2 | 2026-09-29 | yamaa docs build | Classify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived | ||
| 1.1 | 2026-09-29 | yamaa docs build | Resolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML | ||
| 1.0 | yamaa docs build | Initial generation from spec.yaml |
Comments
Signed in with GitHub; saved in repository Discussions