Review ask

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

Lifecycle: draftEditUnder review
What this benchmark means
README.md

Public 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:

  • ADURN would 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

Edit
the run is rejected; no artifact is accepted
expected/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 review
1 source file

input/ae.csv

Edit
1 row
input/ae.csv
USUBJIDAESTDTCAEENDTC
2026-01-052026-01-07

Unexpected Output

Under review
No artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Your review

2 questions and your comments · View benchmark discussions

Mapping spec

Generated from the benchmark YAML; do not edit by hand

Dataset NameVariable NameVariable LabelTypeCodelist/Controlled TermsCoreComputational MethodOrigin
VersionDateAuthorDescriptionReviewerSign-off
1.72026-10-20yamaa docs buildRead 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.62026-10-17yamaa docs buildDescribe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight
1.52026-10-17yamaa docs buildName 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.42026-10-15yamaa docs buildState datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks
1.32026-09-29yamaa docs buildShow study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata
1.22026-09-29yamaa docs buildClassify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived
1.12026-09-29yamaa docs buildResolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML
1.0yamaa docs buildInitial generation from spec.yaml