yamaa 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 meansREADME.mdGoal: prepare subject records from definitions shared through a reusable file.
Input: demographics (DM) records identified by subject.
Variables:
No variables are requested, so no output is produced. The entry
file reuses layers/parent.yaml, which points back to the entry
file, so no stable set of definitions can be reached, and the run
is rejected before any data is read.
How to fix
Remove the backward parents reference so that every path
through the chain terminates. Keep genuinely shared definitions
in one common ancestor.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- inheritance_cycle
- requirement
- REQ-0655
expected/error.yaml
phase: validation
condition: inheritance_cycle
spec_paths:
- parents
requirement: REQ-0655
context:
reason: parent_chain_returns_to_entry
Inputs
Under review1 source fileinput/dm.csv
Edit1 row| USUBJID |
|---|
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
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 |
|---|
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 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 |
Comments
Signed in with GitHub; saved in repository Discussions