Reject a Largest Daily Dose Written as One Summary Inside Another

Review ask

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 means

README.md

Public entries: Python and R. Passing coverage requires an installed inventory.

Goal: give each subject's largest total dose on any one study day (MAXDDOSE) on the subject-level analysis dataset.

Input: subjects from the collected demographics, and collected exposure records with the study day (EXSTDY) and dose given (EXDOSE), several per day.

Variables:

MAXDDOSE would be the largest of the subject's daily dose totals.

Note: the daily totals and their maximum are written as one summary inside another. A summary of the subject's records returns one value, so nothing says which records form each day's total, and the run is rejected before any data is read; no artifact is accepted.

How to fix

Total each day in a dataset of its own, one record per subject and study day, and save it. In that specification, keyed by subject and study day:

- name: DDOSE
  type: float
  label: Daily Dose
  derivation:
    aggregate:
      key: [STUDYID, USUBJID, EXSTDY]
      expr: "SUM(EX.EXDOSE)"

The subject-level dataset then reads the saved daily totals, linked through schema to the specification that produced them, and takes the largest with MAX(DAILY.DDOSE).

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: nested_reduction
rule: FORMULA-21

expected/error.yaml

phase: validation
condition: nested_reduction
spec_paths:
  - columns.MAXDDOSE.derivation.aggregate.expr
rule: FORMULA-21
context:
  outer: MAX
  inner: SUM

YAML specification

1 spec file

spec.yaml

Edit37 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADSL5keys: [STUDYID, USUBJID]6input:7  DM: input/dm.csv8  # yamaa-lint: allow unused_declaration -- only the faulty reduction reads it9  EX:10    path: input/ex.csv11    types: {EXSEQ: int, EXSTDY: int, EXDOSE: float}12base: DM1314output:15  path: adsl.csv16  columns: [STUDYID, USUBJID, MAXDDOSE]1718columns:19  - name: STUDYID20    type: str21    label: Study Identifier22    derivation: DM.STUDYID2324  - name: USUBJID25    type: str26    label: Unique Subject Identifier27    derivation: DM.USUBJID2829  # The largest daily dose, written as a sum inside a maximum, as if one30  # expression could total each day and then take the largest total.31  - name: MAXDDOSE32    type: float33    label: Maximum Daily Dose34    derivation:35      aggregate:36        key: [STUDYID, USUBJID]37        expr: "MAX(SUM(EX.EXDOSE))"

Inputs

Under review2 source files

input/dm.csv

Edit2 rows

input/dm.csv
STUDYID	USUBJID
YAMAA-01
YAMAA-01

input/ex.csv

Edit4 rows

input/ex.csv
STUDYID	EXSEQ	EXSTDY	EXDOSE
YAMAA-01	1	1	100
YAMAA-01	2	1	100
YAMAA-01	3	2	150
YAMAA-01	1	1	50

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Dataset Name	Variable Name	Variable Label	Type	Computational Method	Origin
ADSL	STUDYID	Study Identifier	character	Copy value from DM.STUDYID.	Predecessor
ADSL	USUBJID	Unique Subject Identifier	character	Copy value from DM.USUBJID.	Predecessor
ADSL	MAXDDOSE	Maximum Daily Dose	numeric	Aggregate MAX(SUM(EX.EXDOSE)) over records matching on STUDYID and USUBJID.	Derived

Version	Date	Author	Description
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

How to fix

input/dm.csv

input/ex.csv

Your review

Mapping spec