Reject Conflicting Ages

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: build one subject-level record carrying the collected age (AGE) and sex (SEX), one for each subject the collected demographics carry.

Input: collected demographics records carrying age (AGE) and sex (SEX), where a subject may be collected on more than one record.

Variables:

AGE would be the collected age, carried into the result unchanged.
SEX would be the collected sex, carried into the result unchanged.

Note: the subject decides how many records come out, so a subject collected twice is still one record and both collected records feed it. A value both records report the same way, or that only one of them reports, is one answer and carries without complaint. Two different ages are two answers to a question the record has one place for, so the run fails where the age is read and no artifact is accepted.

How to fix

Reconcile the two collected records and correct the governed demographics input so it holds one supported age for the subject. If both records are legitimate, declare which one answers, for example the one collected last, rather than leaving the choice to file order:

- name: AGE
  type: int
  derivation:
    source:
      variable: DM.AGE
      order_by: [DM.DMDTC]
      keep: last

The sample records carry no collection date (DMDTC here), so the source has to supply one first.

Do not reach for a row template to make the two records two rows. keys states one record per subject, so a second row for that subject would only move the same rejection to the output gate, as negative-output-duplicate shows.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: derivation
condition: multiple_values_per_key
rule: COLUMN-2

expected/error.yaml

phase: derivation
condition: multiple_values_per_key
spec_paths:
  - columns.AGE.derivation.source
rule: COLUMN-2
context:
  identifier: DM.AGE
  value_count: 2
  keys:
    - STUDYID: YAMAA-01
      USUBJID: YAMAA-01-102

YAML specification

1 spec file

spec.yaml

Edit35 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADSL5keys: [STUDYID, USUBJID]6input:7  DM: input/dm.csv89output:10  path: adsl.csv11  columns: [STUDYID, USUBJID, AGE, SEX]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: DM.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: DM.USUBJID2324  # A subject collected on two records is still one row. Its records hold25  # two different ages and nothing says which answers, so the run fails26  # here. SEX is the same on both records and carries through.27  - name: AGE28    type: int29    label: Age30    derivation: DM.AGE3132  - name: SEX33    type: str34    label: Sex35    derivation: DM.SEX

Inputs

Under review1 source file

input/dm.csv

Edit7 rows

input/dm.csv
STUDYID	AGE	SEX
YAMAA-01	64	F
YAMAA-01	58	M
YAMAA-01	59	M
YAMAA-01	72	F
YAMAA-01	72	F
YAMAA-01	45	M
YAMAA-01	—	M

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	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	AGE	Age	numeric	Copy value from DM.AGE.	Predecessor
ADSL	SEX	Sex	character	Copy value from DM.SEX.	Predecessor

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