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 COUNTRY on one record per subject, holding the
subject's collected country in capitals, or the site country when
the subject's own entry is blank.
Input: collected demographics records carrying the collected
country (COUNTRY) and the site country (SITECNTY).
Variables:
COUNTRYwould be the subject's own country in capitals, or the site country in capitals when the subject's own entry is blank.
Note: the uppercasing step is also asked to choose between the two entries, but it can only read one named value. Choosing the entry is a step of its own whose result must be named first, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Derive the selected source in a helper column, then pass that value to the uppercasing step:
- name: COUNTRYSRC
type: str
derivation:
first_available:
sources: [DM.COUNTRY, DM.SITECNTY]
- name: COUNTRY
type: str
derivation:
str_case:
source: COUNTRYSRC
to: upper
Keep the helper column out of the artifact by leaving it off the artifact
column list. A subject with both entries blank then stops the run; if that can
happen, add missing: null beside source: COUNTRYSRC to leave that
subject's country blank instead.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- invalid_field_type
- requirement
- REQ-0287
expected/error.yaml
phase: validation
condition: invalid_field_type
spec_paths:
- columns.COUNTRY.derivation.str_case.source
requirement: REQ-0287
context:
expected: variable
actual: mapping
Inputs
Under review1 source fileinput/dm.csv
Edit2 rows| STUDYID | USUBJID | COUNTRY | SITECNTY |
|---|---|---|---|
| PILOT7 | Deutschland | Germany | |
| PILOT7 | — | France |
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 | COUNTRY | Country | character | Convert {'first_available': {'sources': ['DM.COUNTRY', 'DM.SITECNTY']}} to upper case. | Derived |
| 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