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: carry the randomized population flag (RANDFL) onto a subject listing.

Input: a Parquet export from the randomization system with one record per subject, in which RANDFL is stored as a true-or-false (Boolean) value rather than as text.

Variables:

  • RANDFL would be Y for a subject in the randomized population, taken from the export.

A true-or-false value is none of the kinds of value a study column holds: text, a whole number, a number, a date or a date and time. Reading it as text, as true or 1, or as a number would each be a choice the study never made, and none of them is the Y the flag takes. The run is rejected while the export is read, and no artifact is accepted.

How to fix

Have the randomization system export the flag the way the study defines it: the text Y for a randomized subject and an empty value for one who was not. The study does not need to change.

input:
  RND: input/rand.parquet

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
ingest
condition
source_field_type_unsupported
rule
PARQUET-7
expected/error.yaml
phase: ingest
condition: source_field_type_unsupported
spec_paths:
  - input.RND.path
rule: PARQUET-7
context:
  dataset: RND
  path: input/rand.parquet
  field: RANDFL

Inputs

Under review
1 source file

input/rand.parquet

Edit

Binary fixture; inspect it in the benchmark source.

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 RND.STUDYID.Predecessor
ADSLUSUBJIDUnique Subject IdentifiercharacterCopy value from RND.USUBJID.Predecessor
ADSLRANDFLRandomized Population FlagcharacterCopy value from RND.RANDFL.Predecessor
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