assert_forecast_generic

The function runs input checks that apply to all input data, regardless of
forecast type. The function<ul>
<li>asserts that the forecast is a data.table which has columns <code>observed</code> and
<code>predicted</code></li>
<li>checks the forecast type and forecast unit</li>
<li>checks there are no duplicate forecasts</li>
<li>checks that observed values are constant within each forecast unit</li>
<li>if appropriate, checks the number of samples / quantiles is the same
for all forecasts.</li>
</ul>

internal_input_check

Facilitate the evaluation of forecasts in a convenient
framework based on data.table. It allows user to to check their forecasts
and diagnose issues, to visualise forecasts and missing data, to transform
data before scoring, to handle missing forecasts, to aggregate scores, and
to visualise the results of the evaluation. The package mostly focuses on
the evaluation of probabilistic forecasts and allows evaluating several
different forecast types and input formats. Find more information about the
package in the Vignettes as well as in the accompanying paper,
<doi:10.48550/arXiv.2205.07090>.

Nikos Bosse

scoringutils

Utilities for Scoring and Assessing Predictions

Sam Abbott

Hugo Gruson

Johannes Bracher

Toshiaki Asakura 

James Mba Azam

Sebastian Funk

Michael Chirico

assert_forecast_generic function

<dl><dt>data</dt>
<dd>A data.table with forecasts and observed values that should
be validated.</dd>
<dt>verbose</dt>
<dd>Logical. If <code>FALSE</code> (default is <code>TRUE</code>), no messages and
warnings will be created.</dd></dl>

Arguments

Validation common to all forecast types — assert_forecast_generic

<dl>

<dt>data</dt>
<dd>A data.table with forecasts and observed values that should
be validated.</dd>


<dt>verbose</dt>
<dd>Logical. If <code>FALSE</code> (default is <code>TRUE</code>), no messages and
warnings will be created.</dd>

</dl>

Validation common to all forecast types

assert_forecast_generic: Validation common to all forecast types

Description

Usage

Value

Arguments