Reject Integer Overflow

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: compute CELLTOT, the whole number of cells in the sample, as CELLCNT * VOLUML for each subject.

Input: laboratory records carrying the collected cell concentration (CELLCNT) and the sample volume (VOLUML) for four subjects: an ordinary count and volume, a product exactly at the largest whole number the result can hold (9,223,372,036,854,775,807), a missing concentration, and a product past that largest whole number.

Variables:

CELLTOT would contain the whole number of cells, CELLCNT multiplied by VOLUML, and missing when either is missing. A product beyond the largest whole number the result can hold stops the run, and no artifact is accepted.

How to fix

Verify the transcription and correct CELLCNT in the source before running the calculation. If the verified count genuinely cannot fit in a signed 64-bit integer, the specification cannot represent it exactly as int; change the measurement unit or representation upstream rather than allowing the multiplication to wrap or converting the count to an approximate value.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: derivation
condition: integer_overflow
requirement: REQ-0434

expected/error.yaml

phase: derivation
condition: integer_overflow
spec_paths:
  - columns.CELLTOT.derivation.compute
requirement: REQ-0434
context:
  expr: "CELLCNT * VOLUML"
  keys:
    - STUDYID: YAMAA-01
      USUBJID: YAMAA-01-102

YAML specification

1 spec file

spec.yaml

Edit41 lines

1schema_version: "1.0"2domain: ADLB3keys: [STUDYID, USUBJID]4input:5  LB: input/lb.csv67output:8  path: adlb.csv9  columns: [STUDYID, USUBJID, CELLTOT]1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: LB.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: LB.USUBJID2122  # The input declares no types, so these two columns read the collected23  # text as whole numbers for the product below.24  - name: CELLCNT25    type: int26    label: Cell Concentration27    derivation: LB.CELLCNT2829  - name: VOLUML30    type: int31    label: Sample Volume (L)32    derivation: LB.VOLUML3334  # A whole-number product beyond the signed 64-bit range fails the run35  # rather than wrapping or becoming an approximate value.36  - name: CELLTOT37    type: int38    label: Total Cell Count39    derivation:40      compute:41        expr: "CELLCNT * VOLUML"

Inputs

Under review1 source file

input/lb.csv

Edit4 rows

input/lb.csv
STUDYID	CELLCNT	VOLUML
YAMAA-01	5000000	20
YAMAA-01	9007199254740993	1024
YAMAA-01	9223372036854775807	1
YAMAA-01	—	10

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
ADLB	STUDYID	Study Identifier	character	Copy value from LB.STUDYID.	Predecessor
ADLB	USUBJID	Unique Subject Identifier	character	Copy value from LB.USUBJID.	Predecessor
ADLB	CELLTOT	Total Cell Count	numeric	Compute CELLCNT * VOLUML.	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/lb.csv

Comments

Mapping spec