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 planned treatment (TRT01P) into ADSL for one
submission package, coded with the study's planned treatments.
Input: one pre-analysis row per subject, the package's project file,
which inherits from the study's project in study/project.yaml, and that
project, which names the package's project as its own parent.
Variables:
TRT01Pwould be the planned treatment, one of the study's coded values.
Note: the two project files inherit from each other, so neither holds a settled set of study metadata, and the run is rejected before any data is read.
How to fix
Remove parent from the study's project: the study's project is the root
that every package inherits from, and names no parent of its own.
yamaa: "1.0"
type: project
codelists:
- codelists: [...]
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- inheritance_cycle
- rule
- LAYER-3
expected/error.yaml
phase: validation
condition: inheritance_cycle
spec_paths:
- parent
rule: LAYER-3
context:
reason: parent_chain_returns_to_entry
Inputs
Under review1 source fileinput/adsl_raw.csv
Edit2 rows| STUDYID | USUBJID | TRT01P |
|---|---|---|
| CATH | VITAMIN D3 | |
| CATH | PLACEBO |
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 ADSL_RAW.STUDYID. | Predecessor | ||
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from ADSL_RAW.USUBJID. | Predecessor | ||
| ADSL | TRT01P | Planned Treatment for Period 01 | character | TRT01P | Copy value from ADSL_RAW.TRT01P. | 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 |