yamaa As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs. Agreeing with both approves this benchmark; disagreeing with either needs a comment. Propose a fix with the Edit button on any source file, or add it to your comments.
We suggest spending no more than 5 minutes on a review. The other tabs beside Your review are background for assessment, not under review.
Summary
EditUnder reviewWhat this benchmark meansREADME.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: build a subject listing carrying SITEID.
Input: collected subject listing stored as input/dm.txt,
holding SITEID.
Variables:
SITEIDwould be the site the subject enrolled at, taken directly from the collected listing.
The file's .txt ending names neither of the two formats a listing
can be read from, .csv (comma-separated text) or .parquet, so
nothing says how to read it. Its bytes happen to use commas today,
but a reader that decided by looking inside could read the same
file differently another time or differently from the next reader.
The run is rejected before any data is read, so no artifact is
accepted.
How to fix
Store the listing under the name of the format it is in, so that its reader is chosen by what the study declares rather than by inspection:
input:
DM: input/dm.csv
A listing kept in some other format is converted before the study reads it, and the converted file carries the name of what it now holds.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- source_profile_unknown
- rule
- INPUT-1
expected/error.yaml
phase: validation
condition: source_profile_unknown
spec_paths:
- input.DM.path
rule: INPUT-1
context:
dataset: DM
path: input/dm.txt
Inputs
Under review1 source fileinput/dm.txt
EditSTUDYID,USUBJID,SITEID
CTX,CTX-01,701
CTX,CTX-02,702
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| 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 | SITEID | Study Site Identifier | character | Copy value from DM.SITEID. | Predecessor |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 1.7 | 2026-10-20 | yamaa docs build | Read a specification in the 1.0 surface as its 0.5 counterpart; state that missing values stay missing where a mapping declares no missing handler, and leave out a declared missing answer that restates a handler's default | ||
| 1.6 | 2026-10-17 | yamaa docs build | Describe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight | ||
| 1.5 | 2026-10-17 | yamaa docs build | Name collected precision in words instead of letter codes; state imputation fallbacks, minimum source precision, bounds ignored outside the collected period, and invalid text with no handler as an error; describe date and datetime shifts, imputation flag codes, and partial text giving no date part | ||
| 1.4 | 2026-10-15 | yamaa docs build | State datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks | ||
| 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 |