Reject a Call to a Project Routine the Project Does Not List

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 each subject's baseline body mass index (BMIBL) from the baseline weight (WEIGHTBL) and height (HEIGHTBL) with the study's bmi routine.

Input: baseline vital signs, one record per subject, with the weight in kilograms and the height in centimetres.

Variables:

WEIGHTBL and HEIGHTBL would be the baseline weight and height as collected.
BMIBL would be the weight divided by the square of the height in metres, as the bmi routine computes it.

Note: the body mass index calls a routine named bmi, but the project lists no routine of that name. The study's routines are only those its project lists, so the run is rejected before any project code or data is read, and no artifact is accepted.

How to fix

Add the study's function file for bmi to the project, beside the specifications it serves:

functions:
- functions/bmi.yaml

The file names the bmi routine, its parameters and tests, and the callable that implements it in each host language.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: unknown_project_function
rule: FUNC-4

expected/error.yaml

phase: validation
condition: unknown_project_function
spec_paths:
  - columns.BMIBL.derivation.function.name
rule: FUNC-4
context:
  function: bmi

YAML specification

1 spec file

spec.yaml

Edit40 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADSL5keys: [STUDYID, USUBJID]6input:7  VS: {path: input/vs.csv, types: {WEIGHTBL: float, HEIGHTBL: float}}89output:10  path: adsl.csv11  columns: [STUDYID, USUBJID, WEIGHTBL, HEIGHTBL, BMIBL]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: VS.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: VS.USUBJID2324  - name: WEIGHTBL25    type: float26    label: Baseline Weight (kg)27    derivation: VS.WEIGHTBL2829  - name: HEIGHTBL30    type: float31    label: Baseline Height (cm)32    derivation: VS.HEIGHTBL3334  - name: BMIBL35    type: float36    label: Baseline BMI (kg/m2)37    derivation:38      function:39        name: bmi40        args: {weight_kg: WEIGHTBL, height_cm: HEIGHTBL}

Inputs

Under review1 source file

input/vs.csv

Edit2 rows

input/vs.csv
STUDYID	USUBJID	WEIGHTBL	HEIGHTBL
YAMAA-01		72.4	175.0
YAMAA-01		58.1	160.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
ADSL	STUDYID	Study Identifier	character	Copy value from VS.STUDYID.	Predecessor
ADSL	USUBJID	Unique Subject Identifier	character	Copy value from VS.USUBJID.	Predecessor
ADSL	WEIGHTBL	Baseline Weight (kg)	numeric	Copy value from VS.WEIGHTBL.	Predecessor
ADSL	HEIGHTBL	Baseline Height (cm)	numeric	Copy value from VS.HEIGHTBL.	Predecessor
ADSL	BMIBL	Baseline BMI (kg/m2)	numeric	Call project function bmi with weight_kg = WEIGHTBL and height_cm = HEIGHTBL.	Derived

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