yamaa 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
EditUnder reviewWhat this benchmark meansREADME.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: carry the date and time of randomization (RANDDTM) onto a
subject listing.
Input: a Parquet export from the randomization system with one record per subject, holding the moment of randomization as a date and time.
Variables:
RANDDTMwould be the date and time the subject was randomized, as the export records it.
A study date and time is recorded to the whole second, but the second subject's time, 10:40:12.250 on 2 March 2026, carries a quarter of a second as well. Keeping 10:40:12 or moving to 10:40:13 would each change a recorded value, and the study states no such rule, so the run is rejected while the export is read, and no artifact is accepted.
How to fix
Ask the randomization system to export its times to the whole second, so that the moment it reports is the one the study keeps:
input:
RND: input/rand.parquet
If the study needs the fraction of a second, export the time as text and state in the study how that text is read.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- ingest
- condition
- source_field_value_invalid
- rule
- PARQUET-9
expected/error.yaml
phase: ingest
condition: source_field_value_invalid
spec_paths:
- input.RND.path
rule: PARQUET-9
context:
dataset: RND
path: input/rand.parquet
field: RANDDTM
record: 2
value: 1772448012250000
Inputs
Under review1 source fileinput/rand.parquet
EditBinary fixture; inspect it in the benchmark source.
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADSL | STUDYID | Study Identifier | character | Copy value from RND.STUDYID. | Predecessor | ||
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from RND.USUBJID. | Predecessor | ||
| ADSL | RANDDTM | Datetime of Randomization | numeric | ISO 8601 | Copy value from RND.RANDDTM. | Predecessor |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 1.7 | 2026-10-20 | yamaa docs build | Read 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.6 | 2026-10-17 | yamaa docs build | Describe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight | ||
| 1.5 | 2026-10-17 | yamaa docs build | Name 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.4 | 2026-10-15 | yamaa docs build | State datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks | ||
| 1.3 | 2026-09-29 | yamaa docs build | Show study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata | ||
| 1.2 | 2026-09-29 | yamaa docs build | Classify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived | ||
| 1.1 | 2026-09-29 | yamaa docs build | Resolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML | ||
| 1.0 | yamaa docs build | Initial generation from spec.yaml |