Skip to content

Main content

Metrics: Forecast Error Underprediction Weight Tool

Weight one actual-minus-forecast absolute residual with explicit under/overprediction costs; no fitted asymmetric forecasting model.

Loading tool…

Description

Use residual = actual minus forecast.

Signed errors preserve direction while absolute or squared errors emphasize magnitude. Their gradients and small-residual approximations represent specific mathematical terms rather than complete performance evaluations.

Use residual = actual minus forecast.

When to use this tool

Use Metrics: Forecast Error Underprediction Weight when you need an explicit error, gradient, or local loss component.

How to use the tool and how it works

  1. Enter residual, underpredictionWeight, overpredictionWeight. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Use residual = actual minus forecast. Multiply its magnitude by underpredictionWeight for nonnegative residuals or overpredictionWeight otherwise; mark underprediction only for strictly positive residual.1

Input fieldMeaning and unitsAccepted input
residualActual minus forecast; positive means underprediction.Required. Finite number.
underpredictionWeightUnderprediction WeightRequired. Finite number.
overpredictionWeightOverprediction WeightRequired. Finite number.
Output fieldInterpretationReturned shape
resultResultRequired. Object.
result.weightedAbsoluteErrorWeighted Absolute ErrorCalculated result member: number.
result.underpredictionUnderpredictionCalculated result member: boolean.
json
{
  "input": {
    "residual": 2,
    "underpredictionWeight": 3,
    "overpredictionWeight": 1
  },
  "output": {
    "result": {
      "weightedAbsoluteError": 6,
      "underprediction": true
    }
  }
}

Limitations and assumptions

  • Weights are supplied nonnegative costs; a zero residual has zero loss and no strict underprediction flag.
  • Outputs are nested inside result. Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Assess a full error distribution and keep the sign and aggregation conventions consistent across models.

References

  1. Calculation and input contract: metrics/forecast-error-underprediction-weight — tool.io

Similar or alternative tools