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
README.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: carry HEIGHTBL into ADSL and submit it as the SAS transport file
adsl.xpt.
Input: one pre-analysis row per subject carrying the baseline height in centimetres, measured to two decimals.
Variables:
HEIGHTBLis the baseline height in centimetres, written with one decimal; missing when not measured.
Note: the transport file carries the heights the published data holds, so heights written with one decimal for display would be submitted rounded. The submission stops before any file is written.
How to fix
Keep the measured heights in the data, so 172.46 travels as 172.46 rather than 172.5, and leave the one-decimal display to the display format the data-definition document already reports, which changes no value. Remove the artifact's display digits:
output:
path: adsl.csv
columns: [STUDYID, USUBJID, HEIGHTBL]
If the analysis itself uses the height to one decimal, round it as part of the value and describe that rounding in the column's method:
derivation:
round_half_away_from_zero: {source: ADSL_RAW.HEIGHTBL, digits: 1}
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- decimals_not_applicable
- rule
- JSON-5
expected/error.yaml
phase: validation
condition: decimals_not_applicable
spec_paths:
- adam.specs[0].output.decimals
rule: JSON-5
context:
dataset: ADSL
specification: spec.yaml
decimals: 1
Inputs
Under review1 source fileinput/adsl_raw.csv
Edit3 rows| STUDYID | USUBJID | HEIGHTBL |
|---|---|---|
| CATH | 172.46 | |
| CATH | — | |
| CATH | 165.21 |
Unexpected Output
Under review3 rows presented to the failing check - not an accepted artifactexpected/adsl.csv
Edit3 rows| STUDYID | USUBJID | HEIGHTBL |
|---|---|---|
| CATH | 172.5 | |
| CATH | — | |
| CATH | 165.2 |
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 ADSL_RAW.STUDYID. | Predecessor | |
| ADSL | USUBJID | Unique Subject Identifier | character | Req | Copy value from ADSL_RAW.USUBJID. | Predecessor | |
| ADSL | HEIGHTBL | Baseline Height (cm) | numeric | Perm | Copy value from ADSL_RAW.HEIGHTBL. | 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 |
yamaa