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: give each subject the weight measured nearest the date of randomization (WTR) and the date of that measurement (WTRDT).

Input: one spec.yaml over one record per subject, carrying the date of randomization, and weight records, each with its sequence number, measurement date and result in kilograms.

Variables:

  • RANDDT: the date of randomization.
  • WTRDT: the date of the subject's weight measurement nearest the date of randomization, before or after it, counted in calendar days. Of two measurements as many days away, the earlier is chosen.
  • WTR: the weight measured on that date, in kilograms.

Note: days are counted on the calendar, so a measurement on 27 February 2024 is three days before 1 March 2024, the leap day included, and one on 3 March, two days after, is nearer.

Inputs

Under review
2 source files

input/adsl_raw.csv

Edit
3 rows
input/adsl_raw.csv
STUDYIDUSUBJIDRANDDT
YAMAA-012024-02-12
YAMAA-012024-02-20
YAMAA-012024-03-01

input/vs.csv

Edit
7 rows
input/vs.csv
STUDYIDUSUBJIDVSSEQVSDTVSSTRESN
YAMAA-0112024-01-2971.4
YAMAA-0122024-02-0970.8
YAMAA-0132024-02-1671.0
YAMAA-0112024-02-1364.2
YAMAA-0122024-02-2763.5
YAMAA-0112024-02-2782.9
YAMAA-0122024-03-0382.1

Expected output

Under review
3 expected rows

expected/adsl.csv

Edit
3 rows
expected/adsl.csv
STUDYIDUSUBJIDRANDDTWTRDTWTR
YAMAA-012024-02-122024-02-0970.8
YAMAA-012024-02-202024-02-1364.2
YAMAA-012024-03-012024-03-0382.1
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 ADSL_RAW.STUDYID.Predecessor
ADSLUSUBJIDUnique Subject IdentifiercharacterCopy value from ADSL_RAW.USUBJID.Predecessor
ADSLRANDDTDate of RandomizationnumericISO 8601Copy value from ADSL_RAW.RANDDT.Predecessor
ADSLWTRDTDate of Weight Nearest RandomizationnumericISO 8601Take VSDT from the VS record matching on STUDYID and USUBJID, and no match yields blank.Derived
ADSLWTRWeight (kg) Nearest RandomizationnumericTake VSSTRESN from the VS record matching on STUDYID and USUBJID, and no match yields blank.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

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