yamaa 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
EditUnder reviewWhat this benchmark meansREADME.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: report what a run did in one table: the run and its outcome, the input it read, the rows it built, each output column, and every check it evaluated, held or violated, in the order the run evaluated it.
Input: subject-level records with an AGE each; one age (214) falls
outside the expected 18-to-100 range.
Checks:
not_missingonAGE: held, every age is present.rangeonAGE: violated by the age outside 18-to-100; it is a warning, so the run still succeeds and the run report lists the offending subject.row_count: held, the run produced at least one row.
The run report (adsl-checks.csv) has one row per item, named by its kind
(KIND): the run with its outcome (OUTCOME) and output row count, the
input with the records and bytes read, the rows built from the records
read, one column row per output column with its missing values and
longest text, and one check row per check. Every row names the dataset
(ARTIFACT), its place in the spec (SPEC_PATH) and its subject
(NAME). A check row also carries its optional label (ID), the column
it covers (TARGET), the rule it applies (RULE), its SEVERITY, and how
many units failed out of how many it examined (COUNT, TOTAL): rows for
a row-by-row check and the whole dataset as one unit for row_count. A
held check leaves CONDITION and KEYS empty and has empty details
({}).
Note: the report says what was read, built and checked, and for a
violated check what broke and for whom: its KEYS list every offending
subject, so it can be investigated without stopping the run, and its
DETAILS hold the remaining facts.
Inputs
Under review1 source fileinput/dm.csv
Edit3 rows| STUDYID | USUBJID | AGE |
|---|---|---|
| STUDY01 | 30 | |
| STUDY01 | 214 | |
| STUDY01 | 45 |
Expected output
Under review11 expected rowsexpected/adsl-checks.csv
Edit8 rows| ARTIFACT | KIND | SPEC_PATH | NAME | ID | TARGET | RULE | SEVERITY | OUTCOME | CONDITION | COUNT | TOTAL | KEYS | DETAILS |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| adsl.csv | run | output | — | — | — | — | — | succeeded | — | 3 | — | — | {} |
| adsl.csv | input | input.DM | DM | — | — | — | — | — | — | 3 | — | — | {"bytes":66,"path":"input/dm.csv","profile":"csv"} |
| adsl.csv | rows | base | DM | — | — | — | — | — | — | 3 | 3 | — | {} |
| adsl.csv | column | columns.USUBJID | USUBJID | — | — | — | — | — | — | 0 | 3 | — | {"max_length":3} |
| adsl.csv | column | columns.AGE | AGE | — | — | — | — | — | — | 0 | 3 | — | {} |
| adsl.csv | check | columns.AGE.verifications[0].not_missing | not_missing | — | AGE | CHECK-5 | error | held | — | 0 | 3 | — | {} |
| adsl.csv | check | columns.AGE.verifications[1].range | range | — | AGE | CHECK-7 | warning | violated | range_failed | 1 | 3 | [{"USUBJID":"S-2"}] | {"column":"AGE"} |
| adsl.csv | check | verifications[0].row_count | row_count | — | — | CHECK-13 | error | held | — | 0 | 1 | — | {} |
expected/adsl.csv
Edit3 rows| USUBJID | AGE |
|---|---|
| 30 | |
| 214 | |
| 45 |
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from DM.USUBJID. | Predecessor | ||
| ADSL | AGE | Age | numeric | Copy value from DM.AGE. | 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 |