As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs and outputs. 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: give each subject the sequence of their first dose ending in day
band 2 (B2SEQ).
Input: alternative specifications share subjects, dose starts and lengths, and inclusive day bands. The self-join reads the dose file again under a second input identifier.
Variables:
B2SEQis the earliest dose sequence ending in band 2, and blank when no dose ends there. In the self-join it is the earliest dose whose most recent earlier dose has sequence 1.
Note: an earlier value computed for each dose is available to the selection that dose reads, bare or qualified by its input identifier.
Specification variants
spec_filter_qualified.yamlandspec_filter_bare.yamlcompare the dose's computed last day to both band bounds in a correlated filter.spec_between_qualified.yamlandspec_between_bare.yamluse the same computed last day as the range value.spec_filter_expression.yamlrepeats the last-day arithmetic.spec_self_join.yamlcompares another dose's start to the reading dose's computed last day, while excluding the reading dose and later doses.
Inputs
Under review3 source filesExpected output
Under review18 expected rowsexpected/between_bare.csv
Edit3 rows| USUBJID | B2SEQ |
|---|---|
| 2 | |
| 2 | |
| — |
expected/between_qualified.csv
Edit3 rows| USUBJID | B2SEQ |
|---|---|
| 2 | |
| 2 | |
| — |
expected/filter_bare.csv
Edit3 rows| USUBJID | B2SEQ |
|---|---|
| 2 | |
| 2 | |
| — |
expected/filter_expression.csv
Edit3 rows| USUBJID | B2SEQ |
|---|---|
| 2 | |
| 2 | |
| — |
expected/filter_qualified.csv
Edit3 rows| USUBJID | B2SEQ |
|---|---|
| 2 | |
| 2 | |
| — |
expected/self_join.csv
Edit3 rows| USUBJID | B2SEQ |
|---|---|
| 2 | |
| 2 | |
| — |
Human review and assessment
| Variable Name | Variable Label | Type | Length | Controlled Terms or Format | Origin | Core | Conversion Definition | Variable Type | Variable Order | Comments for Define |
|---|---|---|---|---|---|---|---|---|---|---|
| USUBJID | Unique Subject Identifier | Char | Collected | Copy value from SUBJECTS.USUBJID. | SDTM | 1 | ||||
| B2SEQ | First Qualifying Dose Sequence | Num | Derived | Take SEQ from the first DOSES record matching on USUBJID, where DOSES.PRIORSEQ = 1, ordered by DOSES.DAY, and no match yields blank. | SDTM | 2 |
| 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 |
R
Edit8 lineslibrary(yamaa)yamaa_spec("spec_filter_qualified.yaml")$run()$save()yamaa_spec("spec_filter_bare.yaml")$run()$save()yamaa_spec("spec_between_qualified.yaml")$run()$save()yamaa_spec("spec_between_bare.yaml")$run()$save()yamaa_spec("spec_filter_expression.yaml")$run()$save()yamaa_spec("spec_self_join.yaml")$run()$outputPython
Edit8 linesimport yamaayamaa.spec("spec_filter_qualified.yaml").run().save()yamaa.spec("spec_filter_bare.yaml").run().save()yamaa.spec("spec_between_qualified.yaml").run().save()yamaa.spec("spec_between_bare.yaml").run().save()yamaa.spec("spec_filter_expression.yaml").run().save()yamaa.spec("spec_self_join.yaml").run().output
yamaa