Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

binary_score

Score one binary forecast with Brier and natural-log loss.

Contract

Binary Brier uses the one-component [0,1] convention. Confidently wrong endpoints produce a tagged positive_infinity log loss, never JSON null.

Fields

FieldTypeRequired
op"binary_score"Yes
outcomebooleanYes
probabilityProbabilityYes

This operation needs no existing question or forecast. Use --memory for a calculation-only session.

Request

Send this object on one line. It is expanded below for readability.

{
  "version": 1,
  "id": "example",
  "command": {
    "op": "binary_score",
    "probability": 0.3,
    "outcome": true
  }
}

Response

This response is generated by executing the example against the current binary. Commit timestamps, when present, are shown as <runtime UTC seconds>; the actual protocol returns integer UTC seconds.

{
  "version": 1,
  "id": "example",
  "result": {
    "binary_brier": 0.48999999999999994,
    "log_loss": {
      "kind": "finite",
      "value": 1.2039728043259361
    }
  }
}

Verification

The documentation gate executes the setup and request, then checks the following result fields against independently specified expectations:

JSON pointer within resultExpected
/binary_brier0.49
/log_loss/kind"finite"

Float comparisons use a 1e-12 tolerance. Request schema validation and cross-record validation still apply. See errors and recovery for failure handling.