Review ask

As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs and outputs. 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: derive AOUTCOME, the lesion count each subject is analysed with, copying a missing count from the most similar subject of the same study, and record that donor in DONORID and its distance in DONORDST.

Input: spec.yaml reads one subjects file: study, subject, baseline age, baseline score and the observed lesion count, missing for some subjects.

Variables:

  • AGE, BSCORE and OUTCOME are the subject's baseline age, baseline score and observed lesion count, as collected.
  • SDAGE and SDBSCORE are the sample standard deviations of age and of baseline score over every subject of the study with a value.
  • DONORID is the donor of a subject whose count is missing: the subject of the same study with an observed count whose age and score lie nearest, each difference divided by its study standard deviation. It is missing for a subject with an observed count, and when the study has no donor.
  • DONORDST is that donor's distance, the square root of the sum of the two squared scaled differences.
  • AOUTCOME is the observed count, or else the donor's count; it is missing when the subject has neither.

Note: subject 104 of study S1 is nearest subject 103 (age 55 against 54, score 11 against 12), so it is analysed with 103's count of 3. Subject 105 has no age, so it has no distance and is never a donor. In study S2, subjects 201 and 202 are equally near 203; the lower subject number, 201, is the donor. Study S3 has no subject with an observed count, so its subjects keep a missing count. The standard deviations are columns of the dataset, which the donor selection reads for the subject being imputed.

Inputs

Under review
1 source file

input/subjects.csv

Edit
10 rows
input/subjects.csv
STUDYIDUSUBJIDAGEBSCOREOUTCOME
S152102
S161145
S155113
S15412—
S1—119
S24081
S244104
S2429—
S35010—
S35612—

Expected output

Under review
10 expected rows

expected/lesion.csv

Edit
10 rows
expected/lesion.csv
STUDYIDUSUBJIDAGEBSCOREOUTCOMESDAGESDBSCOREDONORIDDONORDSTAOUTCOME
S1521023.8729833462074171.51657508881031——2
S1611453.8729833462074171.51657508881031——5
S1551133.8729833462074171.51657508881031——3
S15412—3.8729833462074171.516575088810311030.70813083209412583
S1—1193.8729833462074171.51657508881031——9
S2408121——1
S24410421——4
S2429—212011.41421356237309511
S35010—4.2426406871192851.4142135623730951———
S35612—4.2426406871192851.4142135623730951———
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

Variable NameVariable LabelTypeLengthControlled Terms or FormatOriginCoreConversion DefinitionVariable TypeVariable OrderComments for Define
STUDYIDStudy IdentifierCharCollectedCopy value from SUBJ.STUDYID.SDTM1
USUBJIDUnique Subject IdentifierCharCollectedCopy value from SUBJ.USUBJID.SDTM2
AGEAge at BaselineNumCollectedCopy value from SUBJ.AGE.SDTM3
BSCOREBaseline ScoreNumCollectedCopy value from SUBJ.BSCORE.SDTM4
OUTCOMEObserved Lesion CountNumCollectedCopy value from SUBJ.OUTCOME.SDTM5
SDAGEStudy Standard Deviation of AgeNumDerivedAggregate STDDEV(AGE) over records grouped by STUDYID, matching on the shared output keys.SDTM6
SDBSCOREStudy Standard Deviation of Baseline ScoreNumDerivedAggregate STDDEV(BSCORE) over records grouped by STUDYID, matching on the shared output keys.SDTM7
DONORIDDonor Subject IdentifierCharDerivedTake USUBJID from the first SUBJ record matching on STUDYID, where SUBJ.OUTCOME IS NOT NULL AND SUBJ.DIST IS NOT NULL AND LESION.OUTCOME IS NULL, ordered by SUBJ.DIST then SUBJ.USUBJID, and no match yields blank.SDTM8
DONORDSTScaled Distance to the DonorNumDerivedTake DIST from the first SUBJ record matching on STUDYID, where SUBJ.OUTCOME IS NOT NULL AND SUBJ.DIST IS NOT NULL AND LESION.OUTCOME IS NULL, ordered by SUBJ.DIST then SUBJ.USUBJID, where DIST is derived as compute SQRT(ZAGE * ZAGE + ZBSCORE * ZBSCORE), and no match yields blank.SDTM9
AOUTCOMEAnalysis Lesion CountNumDerivedFirst non-missing of: OUTCOME; OUTCOME from the first SUBJ record matching on STUDYID, where SUBJ.OUTCOME IS NOT NULL AND SUBJ.DIST IS NOT NULL AND LESION.OUTCOME IS NULL, ordered by SUBJ.DIST then SUBJ.USUBJID, and no match yields blank.SDTM10
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

yamaa code

Public calls generated from benchmark.yaml; results must match the expected output

R

Edit
3 lines
library(yamaa)yamaa_spec("spec.yaml")$run()$output

Python

Edit
3 lines
import yamaayamaa.spec("spec.yaml").run().output