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: prepare subject records from definitions shared through a reusable file.
Input: demographics (DM) records identified by subject.
Variables:
No variables are requested: the entry file names no output variables.
Note: the entry file reuses layers/parent.yaml, which states
that it needs language version 2.0. This engine reads only version
1.0, so it cannot read the shared definitions: the run is rejected
before any data is read and no artifact is accepted.
How to fix
Find out which language version the parent really needs. A file declares the
oldest version whose features it uses, and this parent uses nothing newer
than 1.0, so "1.0" is the value to correct it to:
yamaa: "1.0"
type: spec
The entry file and its parent may declare different versions. A parent that
does need a newer version needs an engine that reads it; raising the entry
file to "2.0" as well is rejected the same way.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- unsupported_language_version
- rule
- LAYER-4
expected/error.yaml
phase: validation
condition: unsupported_language_version
spec_paths:
- parent
rule: LAYER-4
context:
version: "2.0"
Inputs
Under review1 source fileinput/dm.csv
Edit1 row| USUBJID |
|---|
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| Variable Name | Variable Label | Type | Length | Controlled Terms or Format | Origin | Core | Conversion Definition | Variable Type | Variable Order | Comments for Define |
|---|
| 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 |