Reject a Missing Required Argument

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: carry the source identifier through as ID and return the project routine's result as RESULT.

Input: a source file with ID and VALUE, where VALUE holds the numeric value passed to the routine.

Variables:

ID is the source identifier, carried through unchanged.
RESULT would be the numeric result of passing the source VALUE to the project_value routine.

Note: the call omits the numeric input required by the routine. The run is rejected before any project code or data is read, and no artifact is accepted.

How to fix

Supply the required argument declared by the environment:

function:
  name: project_value
  args: {x: SOURCE.VALUE}

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: invalid_function_argument
requirement: REQ-0700

expected/error.yaml

phase: validation
condition: invalid_function_argument
spec_paths:
  - columns.RESULT.derivation.function.args
requirement: REQ-0700
context:
  function: project_value
  argument: x
  cause: missing_required_argument

YAML specification

1 spec file

spec.yaml

Edit27 lines

1schema_version: "1.0"2domain: TEST3keys: [ID]4input:5  SOURCE:6    path: input/source.csv7    types: {VALUE: float}89output:10  path: test.csv11  columns: [ID, RESULT]1213columns:14  - name: ID15    type: str16    label: Identifier17    derivation: SOURCE.ID1819  # The required numeric argument is deliberately omitted, so static20  # checking rejects the call before any project code or study data is read.21  - name: RESULT22    type: float23    label: Project Function Result24    derivation:25      function:26        name: project_value27        args: {}

Inputs

Under review1 source file

input/source.csv

Edit1 row

input/source.csv
ID	VALUE
01	1.5

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Comments and assessment materials

Variable Name	Variable Label	Type	Length	Controlled Terms or Format	Origin	Core	Conversion Definition	Variable Type	Variable Order	Comments for Define
ID	Identifier	Char			Collected		Copy value from SOURCE.ID.	SDTM	1
RESULT	Project Function Result	Num			Derived		Call project function project_value.	SDTM	2

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

Comments

Mapping spec