yamaa As a clinical trial statistician or programmer, challenge anything in this benchmark: describe a problem in Comments, or propose a fix with the Edit button on any source file.
- Task: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
- Inputs: Do they trigger the failure for the reason the summary gives?
- Expected failure: Is this the right error, raised at the right point, and would it tell the programmer what to fix?
The other tabs beside Comments are background for assessment, not under review.
Summary
EditUnder reviewWhat this benchmark meansREADME.mdGoal: attempt one record for every subject carrying the collected
age (AGE) and sex (SEX), written to a SAS Transport file.
Input: collected demographics records, one per subject.
Variables:
AGEwould be the collected age, carried into the result unchanged.SEXwould be the sex collected in the demographics records, carried into the result unchanged.
Note: the result file named here is a SAS Transport file. That container bounds names to eight uppercase characters, labels to forty, and text to two hundred bytes, and it has no whole-number type and no calendar type, so it cannot hold everything this language admits. A transport file is produced by the packaging step that assembles a submission from published results, not by this run, so the run is rejected before any data is read and no result is accepted.
How to fix
Name a file this language writes: .csv for a reviewable artifact, or
.parquet for a production one that carries its own types.
output:
path: adsl.parquet
columns: [STUDYID, USUBJID, AGE, SEX]
Convert the published artifact to SAS Transport in the packaging step that assembles the submission. The name, label, text, number, and date limits the container imposes are decided there, against the submission being built, and a name or a value the container cannot carry is a packaging failure rather than a silent change to the dataset.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- unknown_artifact_profile
- requirement
- REQ-0760
expected/error.yaml
phase: validation
condition: unknown_artifact_profile
spec_paths:
- output.path
requirement: REQ-0760
context:
path: adsl.xpt
permitted: ['.csv', '.parquet']
Inputs
Under review1 source fileinput/dm.csv
Edit2 rows| STUDYID | USUBJID | AGE | SEX |
|---|---|---|---|
| PILOT7 | 64 | F | |
| PILOT7 | 58 | M |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Comments and assessment materials
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADSL | STUDYID | Study Identifier | character | Copy value from DM.STUDYID. | Predecessor | ||
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from DM.USUBJID. | Predecessor | ||
| ADSL | AGE | Age | numeric | Copy value from DM.AGE. | Predecessor | ||
| ADSL | SEX | Sex | character | Copy value from DM.SEX. | Predecessor |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 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 |
Comments
Signed in with GitHub; saved in repository Discussions