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: build one record per subject and treatment (EXTRT),
carrying the total dose (DOSECUM) across the exposure records.
Input: subject-treatment records carrying treatment (EXTRT),
and exposure records carrying treatment (EXTRT), sequence number
(EXSEQ), and dose (EXDOSE).
Variables:
EXTRTwould be the treatment name, carried over from the subject-treatment records.DOSECUMwould be the total dose across the subject's exposure records for that treatment.
Note: the list of exposure fields to be read as numbers also names a field the exposure file does not carry. Guessing which field was meant would total the wrong values, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Confirm which exposure column holds the dose. Here it is EXDOSE, which is
already declared numeric, so remove the entry for EXDOSEN, which names no
column of input/ex.csv:
input:
TRT: input/subject_treatment.csv
EX:
path: input/ex.csv
types:
EXDOSE: float
Keep the EXDOSE entry: without it the dose is read as text and cannot be
totalled.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- unknown_field
- rule
- INPUT-6
expected/error.yaml
phase: validation
condition: unknown_field
spec_paths:
- input.EX.types.EXDOSEN
rule: INPUT-6
context:
dataset: EX
field: EXDOSEN
Inputs
Under review2 source filesUnexpected 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 |
|---|---|---|---|---|---|---|---|
| ADEX | STUDYID | Study Identifier | character | Copy value from TRT.STUDYID. | Predecessor | ||
| ADEX | USUBJID | Unique Subject Identifier | character | Copy value from TRT.USUBJID. | Predecessor | ||
| ADEX | EXTRT | Name of Treatment | character | Copy value from TRT.EXTRT. | Predecessor | ||
| ADEX | DOSECUM | Cumulative Dose | numeric | Aggregate SUM(EX.EXDOSE) over records matching on the shared output keys. | Derived |
| 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 |