yamaa 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
EditUnder reviewWhat this benchmark meansREADME.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: show that a non-finite number (positive infinity, negative infinity, or Not-a-Number, NaN) is stored as missing, whichever of three routes brings it into a column: a value written in the specification, a value read from the source, or a value returned by a study calculation.
Input: one spec.yaml over a subject-level dataset whose numeric
fields POSITIVE_INFINITY, NEGATIVE_INFINITY, and NOT_A_NUMBER
each hold one non-finite value.
Columns: every one of these is stored as missing.
YAML_PINF,YAML_NINF, andYAML_NANwrite positive infinity, negative infinity, and NaN directly inspec.yaml.SOURCE_PINF,SOURCE_NINF, andSOURCE_NANcopy them fromPOSITIVE_INFINITY,NEGATIVE_INFINITY, andNOT_A_NUMBER.FUNCTION_PINF,FUNCTION_NINF, andFUNCTION_NANtake them from the study calculationnumeric_constant. Its contract allows a missing result; a calculation that may not return one fails the run when it returns a non-finite value.
Note: a quoted spelling such as '.inf' remains text unless
converted to a numeric type.
Engines: numeric_constant belongs to the ordinary installed packages
in rust/tests/project-programs. The function file
functions/numeric_constant.yaml declares it once, with its inline tests, and
names the Python and R implementations, which return the same three
non-finite constants.
Inputs
Under review1 source fileinput/dm.csv
Edit1 row| USUBJID | POSITIVE_INFINITY | NEGATIVE_INFINITY | NOT_A_NUMBER |
|---|---|---|---|
| .inf | -.Inf | .NAN |
Expected output
Under review1 expected rowexpected/adsl.csv
Edit1 row| USUBJID | YAML_PINF | YAML_NINF | YAML_NAN | SOURCE_PINF | SOURCE_NINF | SOURCE_NAN | FUNCTION_PINF | FUNCTION_NINF | FUNCTION_NAN |
|---|---|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — | — |
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from DM.USUBJID. | Predecessor | ||
| ADSL | YAML_PINF | Positive Infinity YAML Literal | numeric | Set constant value "inf". | Assigned | ||
| ADSL | YAML_NINF | Negative Infinity YAML Literal | numeric | Set constant value "-inf". | Assigned | ||
| ADSL | YAML_NAN | Not-a-Number YAML Literal | numeric | Set constant value "nan". | Assigned | ||
| ADSL | SOURCE_PINF | Positive Infinity Source Value | numeric | Copy value from DM.POSITIVE_INFINITY. | Predecessor | ||
| ADSL | SOURCE_NINF | Negative Infinity Source Value | numeric | Copy value from DM.NEGATIVE_INFINITY. | Predecessor | ||
| ADSL | SOURCE_NAN | Not-a-Number Source Value | numeric | Copy value from DM.NOT_A_NUMBER. | Predecessor | ||
| ADSL | FUNCTION_PINF | Positive Infinity Function Result | numeric | Call project function numeric_constant with kind = positive-infinity. | Derived | ||
| ADSL | FUNCTION_NINF | Negative Infinity Function Result | numeric | Call project function numeric_constant with kind = negative-infinity. | Derived | ||
| ADSL | FUNCTION_NAN | Not-a-Number Function Result | numeric | Call project function numeric_constant with kind = nan. | Derived |
| 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 |