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: 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
- requirement
- REQ-0851
expected/error.yaml
phase: ingest
condition: source_record_width
spec_paths:
- input.DM.path
requirement: REQ-0851
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.
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 | 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.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