Reject Unit Suffix

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 one record per subject and treatment carrying DOSECUM, the total dose administered across the matching exposure records.

Input: a subject-treatment inventory carrying EXTRT, plus component exposure records carrying EXTRT, EXSEQ, and EXDOSE, where the dose is declared numeric.

Variables:

DOSECUM would be the total of EXDOSE across the matching exposure records for the same subject and treatment, and missing when no matching record carries a dose.

A stored dose that is not a plain number, such as 200 mg with its unit attached, is rejected while the exposure records are read, so no artifact is accepted.

How to fix

Normalize the source into separate value and unit fields before declaring the dose numeric. For this record, the corrected input should carry EXDOSE as 200 and EXDOSU as mg; then the existing declaration is valid:

EX:
  path: input/ex.csv
  types:
    EXDOSE: float

If the composite text must remain unchanged, ingest it as text, preserve it for traceability, and derive a validated numeric dose before attempting the aggregate. A numeric type declaration must not strip the unit implicitly.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: ingest
condition: field_parse_failed
requirement: REQ-0536

expected/error.yaml

phase: ingest
condition: field_parse_failed
spec_paths:
  - input.EX.types.EXDOSE
requirement: REQ-0536
context:
  dataset: EX
  field: EXDOSE
  type: float
  value: "200 mg"

YAML specification

1 spec file

spec.yaml

Edit37 lines

1schema_version: "1.0"2domain: ADEX3keys: [STUDYID, USUBJID, EXTRT]4input:5  TRT: input/subject_treatment.csv6  # EXDOSE is read as a number, so a stored dose with its unit attached7  # (200 mg) fails while the file is read.8  EX: {path: input/ex.csv, types: {EXDOSE: float}}9base: TRT1011output:12  path: adex.csv13  columns: [STUDYID, USUBJID, EXTRT, DOSECUM]1415columns:16  - name: STUDYID17    type: str18    label: Study Identifier19    derivation: TRT.STUDYID2021  - name: USUBJID22    type: str23    label: Unique Subject Identifier24    derivation: TRT.USUBJID2526  - name: EXTRT27    type: str28    label: Name of Treatment29    derivation: TRT.EXTRT3031  # Sum over the EX records sharing this row's study, subject and treatment;32  # missing when none of them carries a dose.33  - name: DOSECUM34    type: float35    label: Cumulative Dose36    derivation:37      aggregate: "SUM(EX.EXDOSE)"

Inputs

Under review2 source files

input/ex.csv

Edit5 rows

input/ex.csv
STUDYID	EXTRT	EXSEQ	EXDOSE
YAMAA-01	Carboplatin	1	100
YAMAA-01	Carboplatin	2	200 mg
YAMAA-01	Carboplatin	3	—
YAMAA-01	Paclitaxel	1	150
YAMAA-01	Paclitaxel	2	175

input/subject_treatment.csv

Edit3 rows

input/subject_treatment.csv
STUDYID	USUBJID	EXTRT
YAMAA-01		Carboplatin
YAMAA-01		Paclitaxel
YAMAA-01		Cisplatin

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
ADEX	STUDYID	Study Identifier	character	Copy value from TRT.STUDYID.	Predecessor
ADEX	USUBJID	Unique Subject Identifier	character	Copy value from TRT.USUBJID.	Predecessor
ADEX	EXTRT	Name of Treatment	character	Copy value from TRT.EXTRT.	Predecessor
ADEX	DOSECUM	Cumulative Dose	numeric	Aggregate SUM(EX.EXDOSE).	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/ex.csv

input/subject_treatment.csv

Comments

Mapping spec