Reject Numeric Filter

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: number collected laboratory results within each subject, with VISITSEQ giving the collection sequence for each result.

Input: collected laboratory results carrying the numeric result (LBSTRESN) and the collection sequence.

Variables:

VISITSEQ would number each result within its subject in collection-sequence order, counting only the results a stated condition selects; the other results would keep their rows with a missing number. The condition arrives as a bare number (7) instead of a comparison, so which results it selects is undefined, and the run is rejected before any data is read and no artifact is accepted.

How to fix

Decide which rows the study numbers, then state the rule as a comparison. When every collected result counts, leave the filter out entirely:

- name: VISITSEQ
  type: int
  derivation:
    row_number:
      window:
        group_by: [STUDYID, USUBJID]
        order_by: [LBSEQ]

When only some results count, write the condition they satisfy under window, for example filter: "LBSTRESN > 5.5", rather than numbering the rows by hand. The results it excludes keep their rows with a missing number.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: invalid_field_type
requirement: REQ-0287

expected/error.yaml

phase: validation
condition: invalid_field_type
spec_paths:
  - columns.VISITSEQ.derivation.row_number.window.filter
requirement: REQ-0287
context:
  expected: predicate
  actual: int

YAML specification

1 spec file

spec.yaml

Edit42 lines

1schema_version: "1.0"2domain: ADLB3keys: [STUDYID, USUBJID, LBSEQ]4input:5  LB: input/lb.csv67output:8  path: adlb.csv9  columns: [STUDYID, USUBJID, LBSEQ, LBSTRESN, VISITSEQ]1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: LB.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: LB.USUBJID2122  - name: LBSEQ23    type: int24    label: Sequence Number25    derivation: LB.LBSEQ2627  - name: LBSTRESN28    type: float29    label: Numeric Result30    derivation: LB.LBSTRESN3132  # The defect: the window filter is the number 7 rather than a condition,33  # so the specification is rejected before any data is read.34  - name: VISITSEQ35    type: int36    label: Visit Sequence37    derivation:38      row_number:39        window:40          group_by: [STUDYID, USUBJID]41          order_by: [LBSEQ]42          filter: 7

Inputs

Under review1 source file

input/lb.csv

Edit2 rows

input/lb.csv
STUDYID	USUBJID	LBSEQ	LBSTRESN
PILOT7		1	5.2
PILOT7		2	5.8

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	LBSEQ	Sequence Number	numeric	Copy value from LB.LBSEQ.	Predecessor
ADLB	LBSTRESN	Numeric Result	numeric	Copy value from LB.LBSTRESN.	Predecessor
ADLB	VISITSEQ	Visit Sequence	numeric	Row number within each group of STUDYID, USUBJID, ordered by LBSEQ.	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