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: derive ADT, AVAL, and PREVAL for collected weight
measurements, where PREVAL holds the weight from the prior
visit.
Input: collected weight records carrying a collection date
(VSDTC) and a numeric weight (VSSTRESN).
Variables:
ADTwould be the analysis date, carried over from the collected date.AVALwould be the analysis weight, carried over from the collected numeric weight.PREVALwould be the previous analysis weight, taken from the subject's prior record in date order, with ties broken by sequence number.
The request steps zero records along that order, so it asks for the record itself. A record's own weight is already the analysis weight, and a second name for it would let two spellings of one value drift apart, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Move to the preceding row with a negative step in the stated ascending visit order:
row_value:
source: AVAL
offset: -1
window:
group_by: [STUDYID, USUBJID]
order_by: [ADT, VSSEQ]
The first row for each subject then stays missing because it has no preceding visit. If the current value is intended, use the analysis weight directly instead of a neighboring-row read.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- zero_offset
- requirement
- REQ-0328
expected/error.yaml
phase: validation
condition: zero_offset
spec_paths:
- columns.PREVAL.derivation.row_value.offset
requirement: REQ-0328
context:
offset: 0
Inputs
Under review1 source fileinput/vs.csv
Edit2 rows| STUDYID | USUBJID | VSSEQ | VSDTC | VSSTRESN |
|---|---|---|---|---|
| PILOT7 | 1 | 2023-03-01 | 72.4 | |
| PILOT7 | 2 | 2023-04-01 | 71.8 |
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 | STUDYID | Study Identifier | character | Copy value from VS.STUDYID. | Predecessor | ||
| ADVS | USUBJID | Unique Subject Identifier | character | Copy value from VS.USUBJID. | Predecessor | ||
| ADVS | VSSEQ | Sequence Number | numeric | Copy value from VS.VSSEQ. | Predecessor | ||
| ADVS | ADT | Analysis Date | numeric | ISO 8601 | Copy value from VS.VSDTC. | Predecessor | |
| ADVS | AVAL | Analysis Value | numeric | Copy value from VS.VSSTRESN. | Predecessor | ||
| ADVS | PREVAL | Previous Analysis Value | numeric | Take AVAL from the same row within each group of STUDYID, USUBJID, ordered by ADT then VSSEQ. | 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