Review ask

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.

  1. Task: Would a real study need this derivation, specified this way? Does it follow CDISC ADaM: variable names, controlled terms, record structure? Flag any rule that is ambiguous or that a sponsor would handle differently.
  2. Inputs: Do they look like data collected in a real trial, and do they include the situations you would expect to meet in one?
  3. Expected output: Would independent QC programming reproduce every value from these inputs and rules?

The other tabs beside Comments are background for assessment, not under review.

Summary

Lifecycle: draftEditUnder review
What this benchmark means
README.md

Goal: carry each subject's collected age (AGE) into the ADSL analysis dataset, keeping values outside the expected range of 18 to 100 for later data review.

Input: collected demographics, one record per subject, carrying age.

Variables:

  • AGE: the subject's age in years as collected. A value below 18 or above 100 stays in the dataset as collected, and a missing age stays missing; neither case stops the run.

Note: an age outside 18 to 100 does not stop the run: every subject keeps its record, and the review log records one row for the failed check, naming the dataset (ARTIFACT, LOG_VERSION), what was checked (CONDITION, REQUIREMENT, SPEC_PATH, VERIFICATION_ID), how serious the failure is (SEVERITY), and which subjects failed (FAILURE_COUNT, OFFENDING_KEYS, DETAILS).

Inputs

Under review
1 source file

input/dm.csv

Edit
8 rows
input/dm.csv
STUDYIDUSUBJIDAGE
YAMAA-0134
YAMAA-0118
YAMAA-01100
YAMAA-0117
YAMAA-01101
YAMAA-01214
YAMAA-01—
YAMAA-0157

Expected output

Under review
9 expected rows

expected/adsl-violations.csv

Edit
1 row
expected/adsl-violations.csv
LOG_VERSIONARTIFACTSEVERITYCONDITIONREQUIREMENTSPEC_PATHVERIFICATION_IDFAILURE_COUNTOFFENDING_KEYSDETAILS
1.0adsl.csvwarningrange_failedREQ-0377columns.AGE.verifications[0].range—3[{"STUDYID":"YAMAA-01","USUBJID":"YAMAA-01-104"},{"STUDYID":"YAMAA-01","USUBJID":"YAMAA-01-105"},{"STUDYID":"YAMAA-01","USUBJID":"YAMAA-01-106"}]{"column":"AGE"}

expected/adsl.csv

Edit
8 rows
expected/adsl.csv
STUDYIDUSUBJIDAGE
YAMAA-0134
YAMAA-0118
YAMAA-01100
YAMAA-0117
YAMAA-01101
YAMAA-01214
YAMAA-01—
YAMAA-0157
Shaded columns are derived— = missing value

Comments and assessment materials

Comments

Signed in with GitHub; saved in repository Discussions

Mapping spec

Generated from the benchmark YAML; do not edit by hand

Dataset NameVariable NameVariable LabelTypeCodelist/Controlled TermsCoreComputational MethodOrigin
ADSLSTUDYIDStudy IdentifiercharacterCopy value from DM.STUDYID.Predecessor
ADSLUSUBJIDUnique Subject IdentifiercharacterCopy value from DM.USUBJID.Predecessor
ADSLAGEAgenumericCopy value from DM.AGE.Predecessor
VersionDateAuthorDescriptionReviewerSign-off
1.32026-09-29yamaa docs buildShow study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata
1.22026-09-29yamaa docs buildClassify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived
1.12026-09-29yamaa docs buildResolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML
1.0yamaa docs buildInitial generation from spec.yaml

Agent prompt

The request an agent receives with the input files; each tier states no more than the one above

prompts/adam-adsl-age-quality/full.md

Edit
12 lines

Following CDISC ADaM standards, use the provided DM dataset to create an ADSL dataset with one record per subject.

The output dataset should contain the following columns in this order: STUDYID, USUBJID, AGE

AGE is the subject's age in years as collected. A value below 18 or above 100 stays in the dataset as collected, and a missing age stays missing; neither case stops the run.

Read the source datasets from /app/input and save the completed dataset as /app/output/adsl.csv.

prompts/adam-adsl-age-quality/conventions.md

Edit
8 lines

Following CDISC ADaM standards, use the provided DM dataset to create an ADSL dataset with one record per subject.

The output dataset should contain the following columns in this order: STUDYID, USUBJID, AGE

Read the source datasets from /app/input and save the completed dataset as /app/output/adsl.csv.

prompts/adam-adsl-age-quality/brief.md

Edit
8 lines

Following CDISC ADaM standards, use the provided DM dataset to create an ADSL dataset with one record per subject.

The output dataset should contain the following columns in this order: STUDYID, USUBJID, AGE

Read the source datasets from /app/input and save the completed dataset as /app/output/adsl.csv.

yamaa code

Runs the yamaa specification; its result must match the expected output

run.R

Edit
4 lines
library(yamaa)adsl <- yamaa_domain("spec.yaml")$outputadsl

run.py

Edit
4 lines
import yamaaadsl = yamaa.yamaa_domain("spec.yaml").outputadsl

Solution without yamaa

Written from the full prompt and the inputs alone; CI checks it reproduces the expected output

solutions/adam-adsl-age-quality/result.sas

Edit
19 lines
/* opensas reference solution for the yamaa benchmark adam-adsl-age-quality.   Reads the benchmark inputs and derives the requested output.   Execute with the existing opensas runtime: opensas /app/output/result.sas. */data dm;  length STUDYID USUBJID $1024;  infile "/app/input/dm.csv" dsd dlm="," firstobs=2 truncover lrecl=32767;  input STUDYID : $char1024. USUBJID : $char1024. AGE;run;proc sql;  create table result as  select STUDYID, USUBJID, AGE from dm;quit;proc sql;  create table final as select STUDYID, USUBJID, AGE from result;quit;proc export data=final outfile="/app/output/adsl.csv" dbms=csv replace; run;