yamaa / Benchmark

ADaM.ADSL

Inherited Output

input files
1
subjects
3
expected rows
3
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 reviewWhat this benchmark means
README.md

Goal: show a study inheriting the whole artifact layout from the level it shares with other studies, so the list of published variables is written once rather than copied into every study.

Dataset: adsl.csv, ADSL subject-level dataset. One record per subject.

Input: two spec files, read root-first:

  • spec_shared.yaml carries what every study publishing this table must agree on: the dataset, its keys, the four columns, and the complete output naming them in order;
  • spec_study.yaml is the entry: it names the shared level as its parent and supplies only the study's own demographics file. It declares no output.

The chain resolves to expected/spec_resolved.yaml, the default view in the specification dropdown.

Variables:

  • AGE and AGEU carry each subject's collected age and its units from demographics, as the shared level declares them.

Note: output is inherited whole. A study that writes its own output replaces all of it, variable list included, and an inherited output.path names a file beside the level that wrote it. Here both levels share one directory, so the study publishes adsl.csv beside itself.

Inputs

Under review1 source file

input/dm.csv

Edit3 rows
STUDYIDUSUBJIDAGEAGEU
TEST0134YEARS
TEST0158YEARS
TEST0171YEARS

Expected output

Under review3 expected rows

expected/adsl.csv

Edit3 rows
STUDYIDUSUBJIDAGEAGEU
TEST0134YEARS
TEST0158YEARS
TEST0171YEARS
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

Variable NameVariable LabelTypeLengthControlled Terms or FormatOriginCoreConversion DefinitionVariable TypeVariable OrderComments for Define
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

yamaa code

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

run.R

Edit4 lines
library(yamaa)adsl <- yamaa_domain("spec_study.yaml")$outputadsl

run.py

Edit4 lines
import yamaaadsl = yamaa.yamaa_domain("spec_study.yaml").outputadsl