POST/forecastsadmin

Register a forecast BEFORE the moment it is for (409 once target_at has passed): value and 10–90% band, how it was made, an inputs hash (or inputs to hash), and the naive baselines' values for skill.

Body

subjectwhat is forecast
target_atISO date/time it is for
valuenumber
low10% quantile
high90% quantile
methodname (e.g. swarm+release)
designdesign key
runrun id
inputsanything; hashed (sha256, canonical JSON) when inputs_hash is absent
inputs_hash
baselines{name: value}, e.g. {last: 120, no_change: 0}
GET/forecastsmember

Registered forecasts, by target date, each with its outcome once scored.

Query

subject
method
scoredtrue | false
limit1..500 (50)
DELETE/forecasts/:idadmin

Remove a registered forecast and its outcome.

POST/forecasts/actualsadmin

Post actuals; every open forecast for that subject and day, made before it, is scored at once (absolute and percentage error, sMAPE, pinball, within band, error of each baseline).

Body

actuals[{subject, at, value}] (or one at the top level)
sourcewhere they came from
POST/forecasts/actuals/pulladmin

Pull actuals from one of the tenant's read-only tools (called with {subject, ...args}, answering {actuals: [{at, value}]}) and score them.

Body

tooltool name
subject
args{}
GET/forecasts/ledgermember

The accuracy ledger: per method, design or the whole tenant: scored count, MAE, MAPE, sMAPE, pinball, band coverage, skill against each baseline (1 - MAE/MAE baseline), month by month; per design also its backtests' skill.

Query

bymethod | design | tenant
subject
A glass tree whose crown holds many small worlds like fruit

Which world will you live in?

What grows here is meant to reach the real world. Start with a world of your own.