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 enrollment site (SITEID) for each subject.
Input: collected demographics listing carrying a site field
(SITEID), whose records all end with a separator, which leaves the
header's last field without a name.
Variables:
SITEIDwould be the site the subject enrolled at, copied from the collected listing.
The unnamed field can be asked for by no name, and readers disagree about whether the field is there at all: one reports three fields in every record and another four. The run is rejected and no artifact is accepted.
How to fix
Name every field the listing carries, or, when the listing has no further field, remove the trailing separator from the header and from every record. Removing it from the header alone leaves each record one field longer than the header, which is rejected too:
STUDYID,USUBJID,SITEID
CTX,CTX-01,701
CTX,CTX-02,702
A field worth storing is worth naming, and its name is what every later reference to it uses.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- ingest
- condition
- source_field_name_empty
- requirement
- REQ-0851
expected/error.yaml
phase: ingest
condition: source_field_name_empty
spec_paths:
- input.DM.path
requirement: REQ-0851
context:
dataset: DM
path: input/dm.csv
record: 1
field: 4
Inputs
Under review1 source fileinput/dm.csv
Editraw CSVShowing raw CSV because the source is not a valid rectangular table.
STUDYID,USUBJID,SITEID,
CTX,CTX-01,701,
CTX,CTX-02,702,
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 |
| 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