Reject Overlapping Windows

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: give each analysis record the visit (AVISIT) of the one window whose first and last analysis days surround the record's analysis day (ADY).

Input: analysis records carrying the analysis day (ADY), and one study-wide window table giving each visit its first (AWLO) and last (AWHI) analysis day.

Variables:

ADY: the record's analysis day, carried through as given.
AVISIT would be the visit of the window whose first and last days, both included, surround the analysis day; missing when no window holds the day or the day is missing.

Note: a day that falls in two windows has no single visit, and choosing either would depend on a rule the study did not state, so the whole run fails and no dataset is produced.

How to fix

First correct unintended overlap in the window table, so that each analysis day falls in at most one window (here, end WEEK 2 on day 14). If overlap is intentional, state and justify a deterministic selection policy with order_by and keep on the window lookup; do not rely on source-row order. For example, to give a shared day to the window that starts later:

intermediates:
  - id: AWIN
    dataset: AWINDOW
    key: STUDYID
    between: {value: ADY, lower: AWLO, upper: AWHI}
    order_by: [AWINDOW.AWLO]
    keep: last

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: join
condition: multiple_matches
requirement: REQ-0127

expected/error.yaml

phase: join
condition: multiple_matches
spec_paths:
  - intermediates[0]
requirement: REQ-0127
context:
  intermediate: AWIN
  dataset: AWINDOW
  key:
    - STUDYID
  intermediate_key:
    STUDYID: CATH
  match_count: 2
  keys:
    - STUDYID: CATH
      USUBJID: CATH-UCSD-0099
      PARAMCD: SYSBP
      VSSEQ: 1

YAML specification

1 spec file

spec.yaml

Edit59 lines

1schema_version: "1.0"2domain: ADVS3keys: [STUDYID, USUBJID, PARAMCD, VSSEQ]4input:5  ADVS_RAW:6    path: input/advs_raw.csv7    types: {VSSEQ: int, ADY: int}8  AWINDOW:9    path: input/awindow.csv10    types: {AWLO: int, AWHI: int}11base: ADVS_RAW1213output:14  path: advs.csv15  columns: [STUDYID, USUBJID, PARAMCD, VSSEQ, ADY, AVISIT]1617intermediates:18  # The study's window whose first and last analysis days (both included)19  # surround the record's ADY. Two windows holding the same day are two20  # matches with no rule to choose one, so the run stops.21  - id: AWIN22    dataset: AWINDOW23    key: STUDYID24    between: {value: ADY, lower: AWLO, upper: AWHI}2526columns:27  - name: STUDYID28    type: str29    label: Study Identifier30    derivation: ADVS_RAW.STUDYID3132  - name: USUBJID33    type: str34    label: Unique Subject Identifier35    derivation: ADVS_RAW.USUBJID3637  - name: PARAMCD38    type: str39    label: Parameter Code40    derivation: ADVS_RAW.PARAMCD4142  - name: VSSEQ43    type: int44    label: Sequence Number45    derivation: ADVS_RAW.VSSEQ4647  - name: ADY48    type: int49    label: Analysis Relative Day50    derivation: ADVS_RAW.ADY5152  - name: AVISIT53    type: str54    label: Analysis Visit55    derivation: AWIN.AVISIT5657verifications:58  - unique:59      columns: [STUDYID, USUBJID, PARAMCD, VSSEQ]

Inputs

Under review2 source files

input/advs_raw.csv

Edit1 row

input/advs_raw.csv
STUDYID	USUBJID	PARAMCD	VSSEQ	ADY
CATH		SYSBP	1	15

input/awindow.csv

Edit2 rows

input/awindow.csv
STUDYID	AVISIT	AWLO	AWHI
CATH	WEEK 2	2	21
CATH	WEEK 3	15	28

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
ADVS	STUDYID	Study Identifier	character	Copy value from ADVS_RAW.STUDYID.	Predecessor
ADVS	USUBJID	Unique Subject Identifier	character	Copy value from ADVS_RAW.USUBJID.	Predecessor
ADVS	PARAMCD	Parameter Code	character	Copy value from ADVS_RAW.PARAMCD.	Predecessor
ADVS	VSSEQ	Sequence Number	numeric	Copy value from ADVS_RAW.VSSEQ.	Predecessor
ADVS	ADY	Analysis Relative Day	numeric	Copy value from ADVS_RAW.ADY.	Predecessor
ADVS	AVISIT	Analysis Visit	character	Take AVISIT from the AWINDOW record matching on STUDYID, where ADY falls within AWLO to AWHI, and a row with no match is an error.	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/advs_raw.csv

input/awindow.csv

Comments

Mapping spec