Reject Mixed Scales

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: carry DTHDT and LSTVSDY through and take the later of the two in LSTALVDT as the date the subject was last known alive.

Input: collected demographics carrying the date of death (DTHDTC) and the last-visit study day (LSTVSDY), including one subject with no recorded death date and one with no recorded last-visit day.

Variables:

DTHDT would be the date of death, carried over from DTHDTC, and missing when no death date was collected.
LSTVSDY would be the study day of the last visit, counted from the first dose, and missing when no last visit was recorded.
LSTALVDT would be the later of DTHDT and LSTVSDY as the date last known alive.

Note: a calendar date and a day number share no common order, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Put both candidates on the same scale before comparing them. For example, carry the actual last-visit date in the source and compare two date columns:

- name: LSTVSDT
  type: date
  derivation: DM.LSTVSDTC

- name: LSTALVDT
  type: date
  derivation:
    greatest:
      sources: [DTHDT, LSTVSDT]

If only LSTVSDY is available, derive its calendar date from the study-day reference under a separately stated rule before using greatest.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: incomparable_sources
rule: VALUE-19

expected/error.yaml

phase: validation
condition: incomparable_sources
spec_paths:
  - columns.LSTALVDT.derivation.greatest
rule: VALUE-19
context:
  sources: [DTHDT, LSTVSDY]
  types: [date, int]

YAML specification

1 spec file

spec.yaml

Edit42 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADSL5keys: [STUDYID, USUBJID]6input:7  DM: {path: input/dm.csv, types: {DTHDTC: date}}89output:10  path: adsl.csv11  columns: [STUDYID, USUBJID, DTHDT, LSTVSDY, LSTALVDT]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: DM.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: DM.USUBJID2324  - name: DTHDT25    type: date26    label: Date of Death27    derivation: DM.DTHDTC2829  - name: LSTVSDY30    type: int31    label: Last Visit Study Day32    derivation: DM.LSTVSDY3334  # Intentionally mixes scales: DTHDT is a calendar date and LSTVSDY a35  # study-day number, which share no order, so the specification is rejected36  # before any data is read.37  - name: LSTALVDT38    type: date39    label: Date Last Known Alive40    derivation:41      greatest:42        sources: [DTHDT, LSTVSDY]

Inputs

Under review1 source file

input/dm.csv

Edit3 rows

input/dm.csv
STUDYID	DTHDTC	LSTVSDY
YAMAA-01	2023-05-14	118
YAMAA-01	—	142
YAMAA-01	2024-01-30	—

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
ADSL	STUDYID	Study Identifier	character		Copy value from DM.STUDYID.	Predecessor
ADSL	USUBJID	Unique Subject Identifier	character		Copy value from DM.USUBJID.	Predecessor
ADSL	DTHDT	Date of Death	numeric	ISO 8601	Copy value from DM.DTHDTC.	Predecessor
ADSL	LSTVSDY	Last Visit Study Day	numeric		Copy value from DM.LSTVSDY.	Predecessor
ADSL	LSTALVDT	Date Last Known Alive	numeric	ISO 8601	Greatest of DTHDT and LSTVSDY.	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/dm.csv

Your review

Mapping spec