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: attempt the total of each subject's collected results
(AVALTOT), written as the row formula SUM(AVAL).
Input: laboratory (LB) records carrying the study and
subject identifiers, the test code (LBTESTCD) used for the
parameter code, and the collected numeric result (LBSTRESN).
Variables:
AVALwould be the collected numeric result fromLBSTRESN; missing when the collected result is missing.AVALTOTwould be the total ofAVALacross the subject's records, repeated on each record for that subject.
SUM(AVAL) is written as a row formula, but a row formula sees
one record at a time and cannot reach the other records it would
have to total, so the run is rejected before any data is read and
no artifact is accepted.
How to fix
Use an aggregate and state the subject-level keys explicitly:
derivation:
aggregate:
group_by: [STUDYID, USUBJID]
expr: "SUM(AVAL)"
The total is then broadcast to each parameter row for that subject.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- prohibited_function
- rule
- FORMULA-13
expected/error.yaml
phase: validation
condition: prohibited_function
spec_paths:
- columns.AVALTOT.derivation
rule: FORMULA-13
context:
expr: "SUM(AVAL)"
function: SUM
Inputs
Under review1 source fileinput/lb.csv
Edit2 rows| STUDYID | USUBJID | LBTESTCD | LBSTRESN |
|---|---|---|---|
| PILOT7 | ALT | 42 | |
| PILOT7 | AST | 31 |
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.LBTESTCD. | Predecessor | ||
| ADLB | AVAL | Analysis Value | numeric | Copy value from LB.LBSTRESN. | Predecessor | ||
| ADLB | AVALTOT | Total Analysis Value | numeric | Compute SUM(AVAL). | Derived |
| 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 |