Schemasdiagnostic/v1

Diagnostic

Component

One finding from validating an rtemis config: a stable code, how much it matters, the technical and plain-language accounts of it, the numbers behind it, and -- where a deterministic one exists -- an RFC 6902 JSON Patch that fixes it.

Raw JSONv1Unknown properties rejected

Properties

coderequired

string

Stable identifier for the kind of finding.

one of"SCHEMA_INVALID""OUTCOME_MISSING""OUTCOME_TYPE_MISMATCH""RESAMPLE_MIN_CLASS""RESAMPLE_N_ROWS""FEATURE_CONSTANT""FEATURE_TYPE_UNSUPPORTED""DIM_P_GT_N""MISSING_INCOMPATIBLE"

severityrequired

string

What the finding means for running the config: 'error' the run fails or answers a different question, 'warning' it completes but likely not as wanted, 'note' worth knowing.

one of"error""warning""note"

steprequired

integer | null≥ 1

Position of the config in the plan it came from. Unset when the config was validated on its own.

messagerequired

string

Technical account of the finding, naming the fields involved.

plainrequired

string

Plain-language account of the finding, written for a reader with no statistics background.

evidencerequired

object

The measured values behind the finding, keyed by name.

fixrequired

array | null≥ 1 items

RFC 6902 JSON Patch against the config this finding is about. Unset where no deterministic fix exists.

Relationships

Used by

diagnosticsdiagnostics