Reject Fractional Pulse

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: 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: 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 the derivation's 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
rule: VALUE-7

expected/error.yaml

phase: convert
condition: conversion_failed
spec_paths:
  - columns.AVAL
rule: VALUE-7
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

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADVS5keys: [STUDYID, USUBJID, VSSEQ]6input:7  VS: {path: input/vs.csv, types: {VSSTRESN: float}}89output:10  path: advs.csv11  columns: [STUDYID, USUBJID, VSSEQ, AVAL]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: VS.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: VS.USUBJID2324  - name: VSSEQ25    type: int26    label: Sequence Number27    derivation: VS.VSSEQ2829  # No rounding rule is stated, so a fractional result has no int form.30  # With no unconvertible handler declared, the failed conversion is fatal.31  - name: AVAL32    type: int33    label: Analysis Value34    derivation: 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

Human review and assessment

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.	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/vs.csv

Your review

Mapping spec