Reject Self-Filled Weight

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: fill a missing weight from the most recent earlier weight, carrying ADT, AVAL, and AVALF for each measurement.

Input: collected weight records carrying the collection date (VSDTC), the test code (VSTESTCD), and the collected result (VSSTRESN).

Variables:

ADT would be the analysis date taken from the collection date.
AVAL would be the collected weight taken from the collected result, and missing when no measurement was taken.
AVALF would be the current weight or, when it is missing, the filled weight of the previous measurement in date order. After two gaps in a row, the second would read a weight that was itself filled in, so the filled weight is stated in terms of itself.

Note: filling one gap and stopping, or resolving the records in an order nothing states, would each give a different answer from the same data, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Carry from the collected series rather than from the filled output. Search the earlier collected values, then take the first available of AVAL and PRIOR:

- name: PRIOR
  type: float
  derivation:
    previous_non_missing:
      source: AVAL
      window:
        group_by: [STUDYID, USUBJID, PARAMCD]
        order_by: [ADT, VSSEQ]

- name: AVALF
  type: float
  derivation:
    first_available:
      sources: [AVAL, PRIOR]

Keep PRIOR internal by omitting it from output.columns.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: dependency_cycle
requirement: REQ-0072

expected/error.yaml

phase: validation
condition: dependency_cycle
spec_paths:
  - columns.AVALF.derivation.first_available
  - columns.PRIORF.derivation.row_value
requirement: REQ-0072
context:
  cycle: [AVALF, PRIORF, AVALF]

YAML specification

1 spec file

spec.yaml

Edit61 lines

1schema_version: "1.0"2domain: ADVS3keys: [STUDYID, USUBJID, VSSEQ]4input:5  VS: {path: input/vs.csv, types: {VSDTC: date}}67output:8  path: advs.csv9  columns: [STUDYID, USUBJID, VSSEQ, PARAMCD, ADT, AVAL, AVALF]1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: VS.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: VS.USUBJID2122  - name: VSSEQ23    type: int24    label: Sequence Number25    derivation: VS.VSSEQ2627  - name: PARAMCD28    type: str29    label: Parameter Code30    derivation: VS.VSTESTCD3132  - name: ADT33    type: date34    label: Analysis Date35    derivation: VS.VSDTC3637  - name: AVAL38    type: float39    label: Analysis Value40    derivation: VS.VSSTRESN4142  # The defect: AVALF reads PRIORF, and PRIORF reads the previous row's43  # AVALF, so each column waits on the other and the specification is44  # rejected before any data is read.45  - name: AVALF46    type: float47    label: Filled Analysis Value48    derivation:49      first_available:50        sources: [AVAL, PRIORF]5152  - name: PRIORF53    type: float54    label: Prior Filled Analysis Value55    derivation:56      row_value:57        source: AVALF58        offset: -159        window:60          group_by: [STUDYID, USUBJID, PARAMCD]61          order_by: [ADT, VSSEQ]

Inputs

Under review1 source file

input/vs.csv

Edit4 rows

input/vs.csv
STUDYID	VSSEQ	VSDTC	VSTESTCD	VSSTRESN
PILOT7	1	2025-01-05	WEIGHT	70.5
PILOT7	2	2025-02-05	WEIGHT	—
PILOT7	3	2025-03-05	WEIGHT	—
PILOT7	4	2025-04-05	WEIGHT	72.0

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	Codelist/Controlled Terms	Computational Method	Origin
ADVS	STUDYID	Study Identifier	character		Copy value from VS.STUDYID.	Predecessor
ADVS	USUBJID	Unique Subject Identifier	character		Copy value from VS.USUBJID.	Predecessor
ADVS	VSSEQ	Sequence Number	numeric		Copy value from VS.VSSEQ.	Predecessor
ADVS	PARAMCD	Parameter Code	character		Copy value from VS.VSTESTCD.	Predecessor
ADVS	ADT	Analysis Date	numeric	ISO 8601	Copy value from VS.VSDTC.	Predecessor
ADVS	AVAL	Analysis Value	numeric		Copy value from VS.VSSTRESN.	Predecessor
ADVS	AVALF	Filled Analysis Value	numeric		First non-missing of AVAL and PRIORF.	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/vs.csv

Comments

Mapping spec