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: carry each laboratory result (AVAL) onto the laboratory analysis
dataset, one record per subject and parameter.
Input: pre-analysis laboratory results named by the path
input//lb.csv.
Variables:
PARAMCDwould be the parameter code as collected.AVALwould be the result as collected.
Note: the path to the results joins the folder and the file name with two separators, which leaves an empty folder name between them. Systems disagree on what such a path names, so the same study could read different files in different places; the run is rejected before any data is read and no artifact is accepted.
How to fix
Write the path with one separator between each folder and the next name:
input:
LB: {path: input/lb.csv, types: {AVAL: float}}
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- resource_path_not_normalized
- rule
- FILE-5
expected/error.yaml
phase: validation
condition: resource_path_not_normalized
spec_paths:
- input.LB.path
rule: FILE-5
context:
path: input//lb.csv
Inputs
Under review1 source fileinput/lb.csv
Edit2 rows| STUDYID | USUBJID | PARAMCD | AVAL |
|---|---|---|---|
| YAMAA-01 | ALT | 31 | |
| YAMAA-01 | ALT | 58 |
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 |
|---|---|---|---|---|---|---|---|
| ADLB | STUDYID | Study Identifier | character | Copy value from LB.STUDYID. | Predecessor | ||
| ADLB | USUBJID | Unique Subject Identifier | character | Copy value from LB.USUBJID. | Predecessor | ||
| ADLB | PARAMCD | Parameter Code | character | Copy value from LB.PARAMCD. | Predecessor | ||
| ADLB | AVAL | Analysis Value | numeric | Copy value from LB.AVAL. | 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 |