yamaa 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 meansREADME.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
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:
IDis the source identifier, carried through unchanged.RESULTwould be the result of passing the sourceVALUEto theproject_valueroutine.
Note: the project lists two routine files, and both define a routine
named project_value: the second is a working copy of the first. The name
no longer says which routine a call runs, so the run is rejected before any
project code or data is read, and no artifact is accepted.
How to fix
Keep one file per routine name. Remove the working copy from the project's list, or give its routine a name of its own if both are meant to be used:
functions:
- functions/project_value.yaml
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- function_file_invalid
- rule
- FUNC-2
expected/error.yaml
phase: validation
condition: function_file_invalid
spec_paths:
- name
rule: FUNC-2
context:
environment_path: functions[1]
Inputs
Under review1 source fileinput/source.csv
Edit2 rows| ID | VALUE |
|---|---|
| 01 | 1.5 |
| 02 | 0.0 |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| 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 with x = SOURCE.VALUE. | SDTM | 2 |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 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 |