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 subject-level analysis dataset with its data definition, written into a package folder.
Input: the demographics domain with the age (AGE), one record per
subject.
Variables:
AGEis the age in years, copied from the demographics domain.
Note: the data definition is written into the folder package, while
the dataset it describes stays beside the project, one folder up. A data
definition points only at files inside its own folder, the package a
reviewer receives, so the submission is refused before any document is
written; the dataset itself still builds.
How to fix
Keep the data definition beside the datasets it describes:
adam:
define: define.xml
or save the dataset into the package folder, with output.path set to
package/adsl.csv.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- artifact_outside_document
- rule
- DEFINE-16
expected/error.yaml
phase: validation
condition: artifact_outside_document
spec_paths:
- adam.specs[0]
rule: DEFINE-16
Inputs
Under review1 source fileinput/dm.csv
Edit2 rows| STUDYID | USUBJID | AGE |
|---|---|---|
| PAR01 | 41 | |
| PAR01 | 73 |
Unexpected Output
Under review2 rows presented to the failing check - not an accepted artifactexpected/adsl.csv
Edit2 rows| STUDYID | USUBJID | AGE |
|---|---|---|
| PAR01 | 41 | |
| PAR01 | 73 |
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADSL | STUDYID | Study Identifier | character | Req | Copy value from DM.STUDYID. | Predecessor | |
| ADSL | USUBJID | Unique Subject Identifier | character | Req | Copy value from DM.USUBJID. | Predecessor | |
| ADSL | AGE | Age | numeric | Req | 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 |