As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs. Agreeing with both approves this benchmark; disagreeing with either needs a comment. Propose a fix with the Edit button on any source file, or add it to your comments.
We suggest spending no more than 5 minutes on a review. The other tabs beside Your review are background for assessment, not under review.
Summary
README.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: add the analysis duration (ADURN) to an adverse event dataset
from a reusable duration file, on top of the adverse event template.
Input: collected adverse events, one record per event; the template in
layers/ae.yaml; and the duration file in layers/duration.yaml.
Variables:
ADURNwould be the number of days from the analysis start date to the analysis end date, counting both days.
Note: the template already adds the duration file, and the entry adds it again on top of the template. A file contributes to a dataset at most once, because a second copy would apply its definitions again after everything between the two copies, so the run is rejected before any data is read.
How to fix
Add the duration file in one place. Keep it in the template when every
dataset built on the template needs the duration, and remove it from the
entry's include list:
yamaa: "1.0"
type: spec
parent: layers/ae.yaml
domain: ADAE
Otherwise remove it from the template and list it only in the entries that need it.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- duplicate_layer
- rule
- LAYER-3
expected/error.yaml
phase: validation
condition: duplicate_layer
spec_paths:
- include[0]
rule: LAYER-3
context:
path: layers/duration.yaml
Inputs
Under review1 source fileinput/ae.csv
Edit1 row| USUBJID | AESTDTC | AEENDTC |
|---|---|---|
| 2026-01-05 | 2026-01-07 |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 1.7 | 2026-10-20 | yamaa docs build | Read a specification in the 1.0 surface as its 0.5 counterpart; state that missing values stay missing where a mapping declares no missing handler, and leave out a declared missing answer that restates a handler's default | ||
| 1.6 | 2026-10-17 | yamaa docs build | Describe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight | ||
| 1.5 | 2026-10-17 | yamaa docs build | Name collected precision in words instead of letter codes; state imputation fallbacks, minimum source precision, bounds ignored outside the collected period, and invalid text with no handler as an error; describe date and datetime shifts, imputation flag codes, and partial text giving no date part | ||
| 1.4 | 2026-10-15 | yamaa docs build | State datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks | ||
| 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