Reject Row Aggregate

Review ask

As a clinical trial statistician or programmer, challenge anything in this benchmark: describe a problem in Comments, or propose a fix with the Edit button on any source file.

Task: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
Inputs: Do they trigger the failure for the reason the summary gives?
Expected failure: Is this the right error, raised at the right point, and would it tell the programmer what to fix?

The other tabs beside Comments are background for assessment, not under review.

Summary

EditUnder reviewWhat this benchmark means

README.md

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:

AVAL would be the collected numeric result from LBSTRESN; missing when the collected result is missing.
AVALTOT would be the total of AVAL across 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 accepted

expected/error.yaml

phase: validation
condition: prohibited_function
requirement: REQ-0440

expected/error.yaml

phase: validation
condition: prohibited_function
spec_paths:
  - columns.AVALTOT.derivation.compute.expr
requirement: REQ-0440
context:
  expr: "SUM(AVAL)"
  function: SUM

YAML specification

1 spec file

spec.yaml

Edit40 lines

1schema_version: "1.0"2domain: ADLB3keys: [STUDYID, USUBJID, PARAMCD]4input:5  LB: input/lb.csv67output:8  path: adlb.csv9  columns: [STUDYID, USUBJID, PARAMCD, AVAL, AVALTOT]1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: LB.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: LB.USUBJID2122  - name: PARAMCD23    type: str24    label: Parameter Code25    derivation: LB.LBTESTCD2627  - name: AVAL28    type: float29    label: Analysis Value30    derivation: LB.LBSTRESN3132  # The defect: SUM totals several records, but a row formula sees one33  # record at a time, so the specification is rejected before any data is34  # read.35  - name: AVALTOT36    type: float37    label: Total Analysis Value38    derivation:39      compute:40        expr: "SUM(AVAL)"

Inputs

Under review1 source file

input/lb.csv

Edit2 rows

input/lb.csv
STUDYID	USUBJID	LBTESTCD	LBSTRESN
PILOT7		ALT	42
PILOT7		AST	31

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Comments and assessment materials

Dataset Name	Variable Name	Variable Label	Type	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
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/lb.csv

Comments

Mapping spec