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: demonstrate an aggregate's per-record bindings for #789: a
binding reads a named intermediate that declares keep, so one
row-scoped value is visible to every record the aggregate reduces.
Input: exposure records with sequence numbers (EXSEQ) and
doses (EXDOSE), plus dose caps (CAPDOSE), which a subject may
have more than one of.
Variables:
CUMDOSE: the cumulative dose over all of the subject's exposure records, after capping each record's dose at the subject's lowest cap. A subject with no cap has their doses summed uncapped, and a record with a missing dose counts as the full cap.
Mechanism: the DOSECAP intermediate sorts each subject's cap
records by CAPDOSE and keeps the first, the lowest cap, so it
holds one record per subject. The aggregate binds CAP from
DOSECAP.CAPDOSE for each exposure record, caps that record's
DOSE with least, which ignores a missing value, and the reducer
sums the capped values. The keep declaration is what makes the
intermediate read valid. Each output row is built from the
subject's first exposure record (EXSEQ 1), one row per subject.
Inputs
Under review2 source filesExpected output
Under review1 expected rowexpected/adex.csv
Edit1 row| STUDYID | USUBJID | CUMDOSE |
|---|---|---|
| PILOT7 | 400 |
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADEX | STUDYID | Study Identifier | character | Copy value from EX.STUDYID. | Predecessor | ||
| ADEX | USUBJID | Unique Subject Identifier | character | Copy value from EX.USUBJID. | Predecessor | ||
| ADEX | CUMDOSE | Cumulative Capped Dose | numeric | Aggregate SUM(CAPPED) over records matching on STUDYID and USUBJID, with DOSE as EX.EXDOSE, with CAP as CAPDOSE from the first DS record matching on STUDYID and USUBJID, ordered by DS.CAPDOSE, and a row with no match is an error, with CAPPED as least of DOSE and CAP. | Derived |
| Template | Include when |
|---|---|
| exposure | EX.EXSEQ = 1 |
| 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 |