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
README.mdGoal: fill SEVAL, the severity recorded at the visit, from
the collected severity when present, otherwise from SEVAL
itself, defaulting to 0 when neither gives a value.
Input: vital-sign records carrying study, subject, and sequence
entries plus the collected severity (SEVAL), which is missing
when no severity was recorded.
Variables:
SEVAL: the collected severity when one was recorded at the visit, otherwise the value ofSEVALitself, otherwise0. BecauseSEVALreads its own value, there is no earlier value to carry and the definition loops back on itself, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Carry forward from the collected source instead of the column being
derived. Search the subject's earlier collected values in a separate column,
and fall back to it, then to 0, only when the current record has no
severity:
- name: SEVPREV
type: int
derivation:
previous_non_missing:
source: VS.SEVAL
window:
group_by: [STUDYID, USUBJID]
order_by: [VSSEQ]
- name: SEVAL
type: int
derivation:
first_available:
sources: [VS.SEVAL, SEVPREV]
missing: 0
Keep SEVPREV internal by omitting it from output.columns. A subject whose
first record has no severity gets 0 there, because no earlier value exists.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- dependency_cycle
- requirement
- REQ-0072
expected/error.yaml
phase: validation
condition: dependency_cycle
spec_paths:
- columns.SEVAL.derivation.first_available
requirement: REQ-0072
context:
cycle: [SEVAL, SEVAL]
Inputs
Under review1 source fileinput/vs.csv
Edit2 rows| STUDYID | USUBJID | VSSEQ | SEVAL |
|---|---|---|---|
| YAMAA-01 | 1 | — | |
| YAMAA-01 | 2 | 2 |
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 | SEVAL | Severity Value | numeric | First non-missing of VS.SEVAL and SEVAL; all missing → "0". | 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 |
yamaa
Comments
Signed in with GitHub; saved in repository Discussions