Review ask

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

Lifecycle: draftEditUnder review
What this benchmark means
README.md

Public entries: Python and R. Passing coverage requires an installed inventory.

Goal: identify whether each integer value falls inside its own range.

Input: spec_named.yaml, spec_source.yaml and spec_aggregate.yaml are independent alternatives over the same record and range files. Each produces the same ranges.csv table with the same endpoint decisions.

Variables:

  • RANGE, SEQ and VALUE retain the range identifier, sequence number and integer value from the input record.
  • BOTHN is 1 when the value falls within both endpoints, including equality.
  • LEFTN is 1 when the value includes the lower endpoint and excludes the upper.
  • RIGHTN is 1 when the value excludes the lower endpoint and includes the upper.
  • NEITHERN is 1 when the value is strictly inside both endpoints.
  • LOWEREX is 1 when the value exceeds the lower endpoint, without an upper bound.
  • UPPEREX is 1 when the value precedes the upper endpoint, without a lower bound.

Note: Every other answer is blank. A missing value or a missing stated endpoint never matches. Equal endpoints match only with both included; reversed endpoints never match. Omitting a bound leaves that side unrestricted.

Inputs

Under review
2 source files

input/records.csv

Edit
12 rows
input/records.csv
STUDYIDRANGESEQVALUE
SA10
SA21
SA34
SA48
SA59
SA6—
SB78
SC84
SC98
SD104
SE114
SF124

input/windows.csv

Edit
6 rows
input/windows.csv
STUDYIDRANGEWINLOWHIGH
SA118
SB188
SC181
SD1—8
SE11—
SF1——

Expected output

Under review
12 expected rows

expected/ranges.csv

Edit
12 rows
expected/ranges.csv
STUDYIDRANGESEQVALUEBOTHNLEFTNRIGHTNNEITHERNLOWEREXUPPEREX
SA10—————1
SA2111———1
SA34111111
SA481—1—1—
SA59————1—
SA6———————
SB781—————
SC84——————
SC98——————
SD104—————1
SE114————1—
SF124——————
Shaded columns are derived— = missing value

Human review and assessment

Your review

2 questions and your comments · View benchmark discussions

Mapping spec

Generated from the benchmark YAML; do not edit by hand

Variable NameVariable LabelTypeLengthControlled Terms or FormatOriginCoreConversion DefinitionVariable TypeVariable OrderComments for Define
STUDYIDStudy IdentifierCharCollectedCopy value from RECORDS.STUDYID.SDTM1
RANGERange IdentifierCharCollectedCopy value from RECORDS.RANGE.SDTM2
SEQRecord Sequence NumberNumCollectedCopy value from RECORDS.SEQ.SDTM3
VALUERange ValueNumCollectedCopy value from RECORDS.VALUE.SDTM4
BOTHNBOTHN WindowNumDerivedAggregate MIN(WINDOWS.WIN) over records matching on the shared output keys, where VALUE falls within LOW to HIGH.SDTM5
LEFTNLEFTN WindowNumDerivedAggregate MIN(WINDOWS.WIN) over records matching on the shared output keys, where VALUE falls within LOW to HIGH.SDTM6
RIGHTNRIGHTN WindowNumDerivedAggregate MIN(WINDOWS.WIN) over records matching on the shared output keys, where VALUE falls within LOW to HIGH.SDTM7
NEITHERNNEITHERN WindowNumDerivedAggregate MIN(WINDOWS.WIN) over records matching on the shared output keys, where VALUE falls within LOW to HIGH.SDTM8
LOWEREXLOWEREX WindowNumDerivedAggregate MIN(WINDOWS.WIN) over records matching on the shared output keys, where VALUE is LOW or more.SDTM9
UPPEREXUPPEREX WindowNumDerivedAggregate MIN(WINDOWS.WIN) over records matching on the shared output keys, where VALUE is HIGH or less.SDTM10
VersionDateAuthorDescriptionReviewerSign-off
1.72026-10-20yamaa docs buildRead 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.62026-10-17yamaa docs buildDescribe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight
1.52026-10-17yamaa docs buildName 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.42026-10-15yamaa docs buildState datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks
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

Public calls generated from benchmark.yaml; results must match the expected output

R

Edit
5 lines
library(yamaa)yamaa_spec("spec_named.yaml")$run()$save()yamaa_spec("spec_source.yaml")$run()$save()yamaa_spec("spec_aggregate.yaml")$run()$output

Python

Edit
5 lines
import yamaayamaa.spec("spec_named.yaml").run().save()yamaa.spec("spec_source.yaml").run().save()yamaa.spec("spec_aggregate.yaml").run().output