yamaa As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs and outputs. 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: show a study inheriting the whole artifact layout from the level it shares with other studies, so the list of published variables is written once rather than copied into every study.
Dataset: adsl.csv, ADSL subject-level dataset. One record per
subject.
Input: two spec files, read root-first:
spec_shared.yamlcarries what every study publishing this table must agree on: the dataset, its keys, the four columns, and the completeoutputnaming them in order;spec_study.yamlis the entry: it names the shared level as its parent and supplies only the study's own demographics file. It declares nooutput.
The chain resolves to expected/spec_resolved.yaml, the default view
in the specification dropdown.
Variables:
AGEandAGEUcarry each subject's collected age and its units from demographics, as the shared level declares them.
Note: the study writes no output, so it inherits all of it. A
study that writes one part of output, such as its own variable list,
keeps every part it leaves out, and an inherited output.path names a
file beside the level that wrote it. Here both levels share one
directory, so the study publishes adsl.csv beside itself.
Inputs
Under review1 source fileinput/dm.csv
Edit3 rows| STUDYID | USUBJID | AGE | AGEU |
|---|---|---|---|
| TEST01 | 34 | YEARS | |
| TEST01 | 58 | YEARS | |
| TEST01 | 71 | YEARS |
Expected output
Under review3 expected rowsexpected/adsl.csv
Edit3 rows| STUDYID | USUBJID | AGE | AGEU |
|---|---|---|---|
| TEST01 | 34 | YEARS | |
| TEST01 | 58 | YEARS | |
| TEST01 | 71 | YEARS |
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 |