Reject Missing Prior

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: derive ADT, AVAL, and PREVAL for collected weight measurements, where PREVAL holds the weight from the prior visit.

Input: collected weight records carrying a collection date (VSDTC) and a numeric weight (VSSTRESN).

Variables:

ADT would be the analysis date, carried over from the collected date.
AVAL would be the analysis weight, carried over from the collected numeric weight.
PREVAL would be the previous analysis weight, taken from the subject's prior record in date order, with ties broken by sequence number.

The request steps zero records along that order, so it asks for the record itself. A record's own weight is already the analysis weight, and a second name for it would let two spellings of one value drift apart, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Move to the preceding row with a negative step in the stated ascending visit order:

row_value:
  source: AVAL
  offset: -1
  window:
    group_by: [STUDYID, USUBJID]
    order_by: [ADT, VSSEQ]

The first row for each subject then stays missing because it has no preceding visit. If the current value is intended, use the analysis weight directly instead of a neighboring-row read.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: zero_offset
rule: WINDOW-7

expected/error.yaml

phase: validation
condition: zero_offset
spec_paths:
  - columns.PREVAL.derivation.row_value.offset
rule: WINDOW-7
context:
  offset: 0

YAML specification

1 spec file

spec.yaml

Edit50 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADVS5keys: [STUDYID, USUBJID, VSSEQ]6input:7  VS: {path: input/vs.csv, types: {VSDTC: date}}89output:10  path: advs.csv11  columns: [STUDYID, USUBJID, VSSEQ, ADT, AVAL, PREVAL]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: VS.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: VS.USUBJID2324  - name: VSSEQ25    type: int26    label: Sequence Number27    derivation: VS.VSSEQ2829  - name: ADT30    type: date31    label: Analysis Date32    derivation: VS.VSDTC3334  - name: AVAL35    type: float36    label: Analysis Value37    derivation: VS.VSSTRESN3839  # The defect: a zero step reads the record's own AVAL rather than the40  # prior visit's, so the specification is rejected before any data is read.41  - name: PREVAL42    type: float43    label: Previous Analysis Value44    derivation:45      row_value:46        source: AVAL47        offset: 048        window:49          group_by: [STUDYID, USUBJID]50          order_by: [ADT, VSSEQ]

Inputs

Under review1 source file

input/vs.csv

Edit2 rows

input/vs.csv
STUDYID	USUBJID	VSSEQ	VSDTC	VSSTRESN
PILOT7		1	2023-03-01	72.4
PILOT7		2	2023-04-01	71.8

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	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	ADT	Analysis Date	numeric	ISO 8601	Copy value from VS.VSDTC.	Predecessor
ADVS	AVAL	Analysis Value	numeric		Copy value from VS.VSSTRESN.	Predecessor
ADVS	PREVAL	Previous Analysis Value	numeric		Take AVAL from the same row within each group of STUDYID, USUBJID, ordered by ADT then VSSEQ.	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/vs.csv

Your review

Mapping spec