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-level result carrying the enrollment
site (SITEID) and the recorded sex (SEX) for each subject.
Input: subject listing records holding the enrollment site
(SITEID) and the recorded sex (SEX). One record carries one
more field than the header names, and nothing says what the
surplus value holds.
Variables:
SITEIDwould be the site the subject enrolled at, taken from the collected listing.SEXwould be the recorded sex, taken from the collected listing.
Reading the longer record would mean either dropping a collected value or shifting every value after it into the wrong field, so the run is rejected while reading the listing and no artifact is accepted.
How to fix
Export one field for each named field in every record. Where the extra value is itself collected, name it in the header and give every record the field, left empty where nothing was collected:
STUDYID,USUBJID,SITEID,SEX,SITENM
CTX,CTX-01,701,F,
CTX,CTX-02,702,M,Royal Infirmary
A bare separator inside a value produces the same surplus, so a value holding a separator is quoted rather than left bare.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- ingest
- condition
- source_record_width
- rule
- CSV-16
expected/error.yaml
phase: ingest
condition: source_record_width
spec_paths:
- input.DM.path
rule: CSV-16
context:
dataset: DM
path: input/dm.csv
record: 3
field: 5
Inputs
Under review1 source fileinput/dm.csv
Editraw CSVShowing raw CSV because the source is not a valid rectangular table.
STUDYID,USUBJID,SITEID,SEX
CTX,CTX-01,701,F
CTX,CTX-02,702,M,Royal Infirmary
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 | ||
| ADSL | SEX | Sex | character | Copy value from DM.SEX. | 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 |