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: give each subject's total dose in milligrams (TOTDOSE) on the subject-level analysis dataset.

Input: subjects from the collected demographics, and collected exposure records with the dose given (EXDOSE) stored as text, several per subject.

Variables:

  • TOTDOSE would be the sum of the subject's doses, each read as a number.

Note: each record's dose is read as a number under the name DOSEMG, but the total sums DOSE_MG, a name given to no per-record value. Nothing says what that name holds, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Sum the per-record value under the name it was given:

aggregate:
  key: [STUDYID, USUBJID]
  derivations:
    DOSEMG:
      type: float
      derivation: EX.EXDOSE
  expr: "SUM(DOSEMG)"

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
unknown_derive_variable
rule
LOOKUP-22
expected/error.yaml
phase: validation
condition: unknown_derive_variable
spec_paths:
  - columns.TOTDOSE.derivation.aggregate.expr
rule: LOOKUP-22
context:
  variable: DOSE_MG

Inputs

Under review
2 source files

input/dm.csv

Edit
2 rows
input/dm.csv
STUDYIDUSUBJID
YAMAA-01
YAMAA-01

input/ex.csv

Edit
3 rows
input/ex.csv
STUDYIDUSUBJIDEXSEQEXDOSE
YAMAA-011100
YAMAA-012100
YAMAA-01150

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
ADSLSTUDYIDStudy IdentifiercharacterCopy value from DM.STUDYID.Predecessor
ADSLUSUBJIDUnique Subject IdentifiercharacterCopy value from DM.USUBJID.Predecessor
ADSLTOTDOSETotal Dose (mg)numericAggregate SUM(DOSE_MG) over records matching on STUDYID and USUBJID, with DOSEMG as EX.EXDOSE.Derived
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