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: fill the analysis value (AVAL) of each planned vital-sign
visit with the value collected there, or carry forward the latest
earlier collected value for the same subject and parameter.
Input: planned vital-sign assessments, one record per subject,
parameter, and planned visit number (AVISITN), each holding a
collected value or a gap.
Variables:
AVALwould be the value collected at the visit when there is one, otherwise the latest earlier collected value for the same subject and parameter, and blank when no earlier value exists. Zero is a collected value, not a gap.
The input covers the cases that matter: a leading gap at visit 0, a trailing gap after the last collected value, a collected zero that must not be confused with a gap, and a parameter collected nowhere. But carrying a value forward needs an order that says which visits count as earlier, and the window names none, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Name the assessment order in the window, here the planned visit number:
locf:
source: AVALCOL
window:
group_by: [USUBJID, PARAMCD]
order_by: [AVISITN]
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- window_order_by_required
- requirement
- REQ-0340
expected/error.yaml
phase: validation
condition: window_order_by_required
spec_paths:
- columns.AVAL.derivation.locf.window
requirement: REQ-0340
context:
operation: locf
Inputs
Under review1 source fileinput/vs.csv
Edit9 rows| USUBJID | PARAMCD | AVISITN | AVALCOL |
|---|---|---|---|
| SYSBP | 0 | — | |
| SYSBP | 1 | 5 | |
| SYSBP | 2 | — | |
| SYSBP | 3 | — | |
| SYSBP | 4 | 6 | |
| SYSBP | 1 | — | |
| SYSBP | 2 | 0 | |
| SYSBP | 3 | — | |
| DIABP | 1 | — |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Comments and assessment materials
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADVS | USUBJID | Unique Subject Identifier | character | Copy value from VS.USUBJID. | Predecessor | ||
| ADVS | PARAMCD | Parameter Code | character | Copy value from VS.PARAMCD. | Predecessor | ||
| ADVS | AVISITN | Analysis Visit Number | numeric | Copy value from VS.AVISITN. | Predecessor | ||
| ADVS | AVAL | Analysis Value | numeric | Last observation carried forward from AVALCOL within each group of USUBJID, PARAMCD. | Derived |
| 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