Review ask

As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs. 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: carry the record identifier (ID) and preserve the concentration unit (UNIT) exactly as received.

Input: a SAS dataset storing its text as UTF-8, with a micro sign in its concentration unit. The requested decoding instead assumes Windows-1252.

Variables:

  • UNIT would hold the received concentration unit. The contradictory text encoding is refused before any output value is accepted.

Note: the file records how its text is encoded. Choosing another encoding would change a micro sign into different characters.

How to fix

Honor the encoding recorded by the sender. Omit the contradictory encoding declaration so the file's own encoding supplies the decoding:

input:
  SRC:
    path: input/concentration.sas7bdat
    types: {ID: int}

An explicit encoding: utf-8 agrees with this file too. A transport file stores no encoding, so its declaration must still be supplied.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
ingest
condition
source_sas_invalid
rule
SAS-7
expected/error.yaml
phase: ingest
condition: source_sas_invalid
rule: SAS-7
spec_paths: [input.SRC.encoding]
context:
  dataset: SRC
  path: input/concentration.sas7bdat
  cause: encoding_mismatch
  declared_encoding: windows-1252
  stored_encoding: utf-8

Inputs

Under review
1 source file

input/concentration.sas7bdat

Edit

Binary fixture; inspect it in the benchmark source.

Unexpected Output

Under review
No artifact is produced

No fixture files in this directory.

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
IDRecord IdentifierNumCollectedCopy value from SRC.ID.SDTM1
UNITConcentration UnitCharCollectedCopy value from SRC.UNIT.SDTM2
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