yamaa 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.
- Task: Would a real study need this derivation, specified this way? Does it follow CDISC standards: variable names, controlled terms, record structure? Flag any rule that is ambiguous or that a sponsor would handle differently.
- Inputs: Do they look like data collected in a real trial, and do they include the situations you would expect to meet in one?
- 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
EditUnder reviewWhat this benchmark meansREADME.mdGoal: assign dense sequence numbers within each group in original source record order.
Input: spec.yaml reads interleaved groups, labels collected in reverse
alphabetical order, excluded records, and otherwise identical records.
Variables:
GROUP_ID: the collected group identifier.ROW_SEQUENCE: consecutive sequence numbers starting at 1 within each group.RECORD_LABEL: the collected label, without alphabetical sorting.SOURCE_ORDINAL: the original one-based position of each data record.
Note: sequences restart at 1 in each group. Filtering removes excluded
records without changing the surviving source ordinals. Identical records
retain distinct positions and sequence values. This listing includes
SOURCE_ORDINAL for review.
Inputs
Under review1 source fileinput/source.csv
Edit6 rows| GroupID | RecordLabel | Include |
|---|---|---|
| G2 | ROW_B | Y |
| G1 | ROW_B | Y |
| G1 | SKIPPED | N |
| G2 | ROW_A | Y |
| G1 | ROW_A | Y |
| G1 | ROW_A | Y |
Expected output
Under review5 expected rowsexpected/records.csv
Edit5 rows| GROUP_ID | ROW_SEQUENCE | RECORD_LABEL | SOURCE_ORDINAL |
|---|---|---|---|
| G1 | 1 | ROW_B | 2 |
| G1 | 2 | ROW_A | 5 |
| G1 | 3 | ROW_A | 6 |
| G2 | 1 | ROW_B | 1 |
| G2 | 2 | ROW_A | 4 |
Shaded columns are derived— = missing value
Comments and assessment materials
Not under review
| Variable Name | Variable Label | Type | Length | Controlled Terms or Format | Origin | Core | Conversion Definition | Variable Type | Variable Order | Comments for Define |
|---|---|---|---|---|---|---|---|---|---|---|
| GROUP_ID | Group Identifier | Char | Collected | Copy value from SOURCE.GroupID. | SDTM | 1 | ||||
| ROW_SEQUENCE | Source Order Sequence | Num | Derived | Row number within each group of GROUP_ID, ordered by SOURCE.SourceOrdinal. | SDTM | 2 | ||||
| RECORD_LABEL | Collected Record Label | Char | Collected | Copy value from SOURCE.RecordLabel. | SDTM | 3 | ||||
| SOURCE_ORDINAL | Original Source Record Position | Num | Collected | Copy value from SOURCE.SourceOrdinal. | SDTM | 4 |
| Template | Include when |
|---|---|
| included | SOURCE.Include = 'Y' |
| 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