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: attempt to prepare subject records reusing shared
definitions named by https://example.test/organization.yaml.
Input: demographics records carrying the unique subject identifier.
Variables:
The requested result names no variables. It would carry subject records prepared from the shared definitions.
Note: the run is rejected before any data is read and no artifact is accepted: a remote resource can change independently and cannot provide a reproducible local build.
How to fix
Review and store the parent file locally, then reference it with a relative or
absolute filesystem parents path. Do not use a URL or URI.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- invalid_parent_path
- requirement
- REQ-0653
expected/error.yaml
phase: validation
condition: invalid_parent_path
spec_paths:
- parents
requirement: REQ-0653
context:
reason: remote_reference
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