Reject Fractional Pulse

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: derive AVAL from the collected pulse rate.

Input: collected vital signs (VS) records carrying VSTESTCD and VSSTRESN; one record carries a fractional pulse rate.

Variables:

AVAL would be the collected result from VSSTRESN, held as a whole number. A fractional result has no whole-number form unless a rounding rule is stated, so the run fails and no artifact is accepted.

How to fix

If fractional pulse rates are valid for the analysis, preserve the collected precision by declaring the result as float:

- name: AVAL
  type: float
  derivation:
    source: VS.VSSTRESN

If the result must be an integer, the specification must choose an explicit rule, such as round_half_away_from_zero with digits: 0, or FLOOR, CEIL, or TRUNC in a compute expression; conversion will not choose a rounding rule implicitly.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: convert
condition: conversion_failed
requirement: REQ-0021

expected/error.yaml

phase: convert
condition: conversion_failed
spec_paths:
  - columns.AVAL
requirement: REQ-0021
context:
  from: float
  to: int
  value: 72.5
  keys:
    - STUDYID: YAMAA-01
      USUBJID: YAMAA-01-101
      VSSEQ: 2

YAML specification

1 spec file

spec.yaml

Edit34 lines

1schema_version: "1.0"2domain: ADVS3keys: [STUDYID, USUBJID, VSSEQ]4input:5  VS: {path: input/vs.csv, types: {VSSTRESN: float}}67output:8  path: advs.csv9  columns: [STUDYID, USUBJID, VSSEQ, AVAL]1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: VS.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: VS.USUBJID2122  - name: VSSEQ23    type: int24    label: Sequence Number25    derivation: VS.VSSEQ2627  # No rounding rule is stated, so a fractional result has no int form.28  # With no unconvertible handler declared, the failed conversion is fatal.29  - name: AVAL30    type: int31    label: Analysis Value32    derivation:33      value:34        source: VS.VSSTRESN

Inputs

Under review1 source file

input/vs.csv

Edit2 rows

input/vs.csv
STUDYID	USUBJID	VSSEQ	VSTESTCD	VSSTRESN
YAMAA-01		1	PULSE	68
YAMAA-01		2	PULSE	72.5

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
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	AVAL	Analysis Value	numeric	Copy value from VS.VSSTRESN.	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/vs.csv

Comments

Mapping spec