Skip to content
Changeset Second Opinion

Refit the cut points from reviewers' decisions

POST
/api/v1/config/calibrate
curl --request POST \
  --url https://example.com/api/v1/config/calibrate \
  --header 'Content-Type: application/json' \
  --data '{ "apply": false, "pack_id": "example" }'

Without apply this is the same dry run as the reliability report. With apply the fitted cut points become a new configuration version (the pack’s file is not edited) and active; runs already made keep the version they used. Nothing here ever runs by itself.

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
CalibrateRequest

Body of POST /config/calibrate: which pack, and whether to apply the result.

object
apply
Apply
boolean
pack_id
Any of:
string
<= 40 characters

Responses

Section titled “Responses”

200

Section titled “200”

Successful Response

Media typeapplication/json
CalibrationResult

The report, and what applying did (nothing when applied is false).

object
applied
required
Applied
boolean
bands
required
Bands
Array<object>
BandReliability

How often the readings behind runs of one band were right (a report; cut-offs never move).

object
band
required
Band

Backend-assigned sharpness band of the model output.

string
Allowed values: confident unsure cannot_tell
correct
required
Correct
integer
decided
required
Decided
integer
lower
required
Lower
number
n
required
N
integer
status
required
Status
string
Allowed values: reported insufficient_data
upper
required
Upper
number
calibration_id
Any of:
string
config_version
Any of:
string
min_labels
required
Min Labels

Labelled readings a probe needs before it is tuned

integer
n_labelled_outcomes
required
N Labelled Outcomes
integer
n_outcomes
required
N Outcomes

Cases whose newest decision was counted

integer
pack_id
required
Pack Id
string
probes
required
Probes
Array<object>
ProbeReliability

How one fact probe fared against the reviewers’ outcomes, and the cut points it would get.

object
correct
required
Correct

Decided readings that were right at the default cuts

integer
coverage
Any of:
number
decided
required
Decided
integer
default_high
required
Default High
number
<= 1
default_low
required
Default Low
number
<= 1
high
required
High
number
<= 1
label
required
Label
string
low
required
Low
number
<= 1
lower
required
Lower
number
n
required
N

Labelled readings for this probe

integer
probe
required
Probe
string
status
required
Status
string
Allowed values: fitted kept_default insufficient_data
tuned_correct
required
Tuned Correct
integer
tuned_decided
required
Tuned Decided
integer
tuned_lower
required
Tuned Lower
number
tuned_upper
required
Tuned Upper
number
upper
required
Upper
number
reason
Any of:
string
synthetic_outcomes
Synthetic Outcomes

Counted decisions that are synthetic demo data

integer
0

Example 

{
  "bands": [
    {
      "band": "confident",
      "status": "reported"
    }
  ],
  "probes": [
    {
      "status": "fitted"
    }
  ],
  "synthetic_outcomes": 0
}

401

Section titled “401”

Unauthorized

Problem

Application/problem+json body. Extension members (for example job_id) are allowed.

object
detail
Any of:
string
errors
Any of:
Array<object>
FieldError

One validation failure: where, what, and a stable machine code (never the input value).

object
loc
required
Loc
Array
msg
required
Msg
string
type
required
Type
string
instance
Any of:
string
request_id
required
Request Id
string
status
required
Status
integer
title
required
Title
string
type
Type
string
default: about:blank
key
additional properties
any

Example 

{
  "type": "about:blank"
}

403

Section titled “403”

Forbidden

Problem

Application/problem+json body. Extension members (for example job_id) are allowed.

object
detail
Any of:
string
errors
Any of:
Array<object>
FieldError

One validation failure: where, what, and a stable machine code (never the input value).

object
loc
required
Loc
Array
msg
required
Msg
string
type
required
Type
string
instance
Any of:
string
request_id
required
Request Id
string
status
required
Status
integer
title
required
Title
string
type
Type
string
default: about:blank
key
additional properties
any

Example 

{
  "type": "about:blank"
}

404

Section titled “404”

Not Found

Problem

Application/problem+json body. Extension members (for example job_id) are allowed.

object
detail
Any of:
string
errors
Any of:
Array<object>
FieldError

One validation failure: where, what, and a stable machine code (never the input value).

object
loc
required
Loc
Array
msg
required
Msg
string
type
required
Type
string
instance
Any of:
string
request_id
required
Request Id
string
status
required
Status
integer
title
required
Title
string
type
Type
string
default: about:blank
key
additional properties
any

Example 

{
  "type": "about:blank"
}

422

Section titled “422”

Validation Error

Media typeapplication/json
HTTPValidationError
object
detail
Detail
Array<object>
ValidationError
object
ctx
Context
object
input
Input
loc
required
Location
Array
msg
required
Message
string
type
required
Error Type
string

Example generated

{
  "detail": [
    {
      "ctx": {},
      "input": "example",
      "loc": [
        "example"
      ],
      "msg": "example",
      "type": "example"
    }
  ]
}

Map data © OpenStreetMap contributors, under the Open Database Licence. Code under the Apache-2.0 licence. Made by Yogesh.

Changeset Second Opinion is an independent open source tool for OpenStreetMap reviewers. It is not endorsed by, sponsored by or affiliated with the OpenStreetMap Foundation. OpenStreetMap is a trademark of the OpenStreetMap Foundation, used under itstrademark policy.