Reject rounding a coded value

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: build RNDVAL by rounding a value to one decimal place with ties half away from zero.

Input: collected demographics carrying coded sex (SEX).

Variables:

RNDVAL would be the coded sex (SEX) rounded to one decimal place.

Rounding a coded value has no meaning, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Round a numeric variable rather than the coded sex. The demographics input carries none here, so add one and declare its type: a field read without a declared type is text, and rounding it is rejected the same way.

input:
  DM: {path: input/dm.csv, types: {AVAL: float}}

# in the RNDVAL column
round_half_away_from_zero:
  source: DM.AVAL
  digits: 1

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: incompatible_input_type
requirement: REQ-0418

expected/error.yaml

phase: validation
condition: incompatible_input_type
spec_paths:
  - columns.RNDVAL.derivation.round_half_away_from_zero.source
requirement: REQ-0418
context:
  source: SEX
  expected: numeric
  actual: str

YAML specification

1 spec file

spec.yaml

Edit35 lines

1schema_version: "1.0"2domain: ADSL3keys: [STUDYID, USUBJID]4input:5  DM: input/dm.csv67output:8  path: adsl.csv9  columns: [STUDYID, USUBJID, RNDVAL]1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: DM.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: DM.USUBJID2122  - name: SEX23    type: str24    label: Sex25    derivation: DM.SEX2627  # The defect: SEX is a text code, and rounding accepts only a numeric28  # source, so the specification is rejected before any data is read.29  - name: RNDVAL30    type: float31    label: Rounded Value32    derivation:33      round_half_away_from_zero:34        source: SEX35        digits: 1

Inputs

Under review1 source file

input/dm.csv

Edit2 rows

input/dm.csv
STUDYID	USUBJID	SEX
PILOT7		M
PILOT7		F

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
ADSL	STUDYID	Study Identifier	character	Copy value from DM.STUDYID.	Predecessor
ADSL	USUBJID	Unique Subject Identifier	character	Copy value from DM.USUBJID.	Predecessor
ADSL	RNDVAL	Rounded Value	numeric	Round SEX to 1 decimal place, ties away from zero.	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/dm.csv

Comments

Mapping spec