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: record SEX for each subject, accepting only M, F,
and U.
Input: collected demographics carrying subject sex (SEX).
Variables:
SEXwould be the subject's sex, copied from the collected records, holdingM,F, orU.
Note: the text pattern the codes are checked against names a
group in a spelling ((?P<code>...)) that only some pattern readers
accept, so the run is rejected before any data is read and no
artifact is accepted.
How to fix
Decide which codes the study collects, then write the check in the one
notation every reader uses. A named group is spelled (?<name>...) rather
than (?P<name>...), and a check that must describe the whole value anchors
itself:
- matches:
pattern: '^[MFU]$'
When the permitted set is small and fixed, list it instead. The list needs no text rule at all and cannot drift from the codes it names:
- allowed_values:
values: [M, F, U]
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- invalid_regex
- rule
- TEXT-6
expected/error.yaml
phase: validation
condition: invalid_regex
spec_paths:
- columns.SEX.verifications[0].matches.pattern
rule: TEXT-6
context:
pattern: '(?P<code>[MFU])'
Inputs
Under review1 source fileinput/dm.csv
Edit2 rows| STUDYID | USUBJID | SEX |
|---|---|---|
| CATH | M | |
| CATH | F |
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 | 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 |