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: submit the demographics domain with its data definition, from the files its last build saved.
Input: collected demographics, one record per subject, and what the last
build saved: the dataset under its earlier name, dm_v1.csv, and the run
report beside it, dm-report.csv.
Variables:
DOMAINisDMon every record.STUDYIDis the collected study identifier. A record without it is refused.USUBJIDis the collected unique subject identifier. A record without it is refused.
Note: the last build saved dm_v1.csv, but the current submission names
dm.csv. The dataset has not been rebuilt since that name changed. Its run
report still records the earlier filename, so the submission is refused
before any document is written: its data definition would describe a dataset
that no build of the current specification saved.
How to fix
Build and save the dataset again, so that dm.csv and its run report
describe one build, then submit:
p = yamaa.project("project.yaml")
p.spec("DM").run().save()
p.submission("sdtm")
The rebuilt report names its saved file (ARTIFACT), item kind and location
(KIND, SPEC_PATH, NAME), outcome (OUTCOME, CONDITION), counts
(COUNT, TOTAL) and measurements (DETAILS). Check labels and targets
(ID, TARGET), rules and severity (RULE, SEVERITY), and failing subject
keys (KEYS) describe any checks that ran.
Do not edit the run report or rename the saved file to match it: the report
records what a build read and wrote, and only a new build replaces it.
spec_saved.yaml keeps the specification as it stood at that last build.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- stale_artifact
- rule
- PROJECT-15
expected/error.yaml
phase: validation
condition: stale_artifact
spec_paths:
- sdtm.specs[0].output.report
rule: PROJECT-15
context:
dataset: DM
report: dm-report.csv
reason: artifact_path
recorded: dm_v1.csv
actual: dm.csv
Inputs
Under review1 source fileinput/dm_raw.csv
Edit2 rows| STUDYID | USUBJID |
|---|---|
| CATH | |
| CATH |
Unexpected Output
Under review8 rows presented to the failing check - not an accepted artifactexpected/dm-report.csv
Edit6 rows| ARTIFACT | KIND | SPEC_PATH | NAME | ID | TARGET | RULE | SEVERITY | OUTCOME | CONDITION | COUNT | TOTAL | KEYS | DETAILS |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| dm_v1.csv | run | output | — | — | — | — | — | succeeded | — | 2 | — | — | {} |
| dm_v1.csv | input | input.DM_RAW | DM_RAW | — | — | — | — | — | — | 2 | — | — | {"bytes":56,"path":"input/dm_raw.csv","profile":"csv"} |
| dm_v1.csv | rows | base | DM_RAW | — | — | — | — | — | — | 2 | 2 | — | {} |
| dm_v1.csv | column | columns.DOMAIN | DOMAIN | — | — | — | — | — | — | 0 | 2 | — | {"max_length":2} |
| dm_v1.csv | column | columns.STUDYID | STUDYID | — | — | — | — | — | — | 0 | 2 | — | {"max_length":4} |
| dm_v1.csv | column | columns.USUBJID | USUBJID | — | — | — | — | — | — | 0 | 2 | — | {"max_length":14} |
expected/dm_v1.csv
Edit2 rows| DOMAIN | STUDYID | USUBJID |
|---|---|---|
| DM | CATH | |
| DM | CATH |
Human review and assessment
| Variable Name | Variable Label | Type | Length | Controlled Terms or Format | Origin | Core | Conversion Definition | Variable Type | Variable Order | Comments for Define |
|---|---|---|---|---|---|---|---|---|---|---|
| DOMAIN | Domain Abbreviation | Char | Assigned | Set constant value "DM". | SDTM | 1 | ||||
| STUDYID | Study Identifier | Char | Collected | Copy value from DM_RAW.STUDYID. | SDTM | 2 | ||||
| USUBJID | Unique Subject Identifier | Char | Collected | Copy value from DM_RAW.USUBJID. | SDTM | 3 |
| 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 |