Skip to content

Main content

Metrics: Rmsle Single Pair Domain Check Tool

Return the one-pair log1p residual and squared contribution behind RMSLE for nonnegative values, not an aggregated metric or silent clipping.

Loading tool…

Description

Subtract log1p(actual) from log1p(forecast), then return that residual, its square, and its absolute value.

Logarithmic errors compare multiplicative differences. Positive-domain requirements and any added offset change both valid inputs and the interpretation of small values.

Subtract log1p(actual) from log1p(forecast), then return that residual, its square, and its absolute value.

When to use this tool

Use Metrics: Rmsle Single Pair Domain Check when you need a single log-error term or a logarithm-domain check.

How to use the tool and how it works

  1. Enter actual, forecast. 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.

Require nonnegative actual and forecast. Subtract log1p(actual) from log1p(forecast), then return that residual, its square, and its absolute value.1

Input fieldMeaning and unitsAccepted input
actualObserved value on the same scale and unit as its prediction.Required. Finite number.
forecastForecast value on the same scale and unit as actual.Required. Finite number.
Output fieldInterpretationReturned shape
resultResultRequired. Object.
result.logResidualLog ResidualCalculated result member: number.
result.squaredLogResidualSquared Log ResidualCalculated result member: number.
result.rootSingleSquaredLogErrorRoot Single Squared Log ErrorCalculated result member: number.
json
{
  "input": {
    "actual": 0,
    "forecast": 1
  },
  "output": {
    "result": {
      "logResidual": 0.6931471805599453,
      "squaredLogResidual": 0.4804530139182014,
      "rootSingleSquaredLogError": 0.6931471805599453
    }
  }
}

Limitations and assumptions

  • This is one pair's log error, not an aggregate RMSLE; the unit-dependent +1 convention is fixed.
  • 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

Choose a documented offset and aggregation policy and compare errors on the original scale where useful.

References

  1. Calculation and input contract: metrics/rmsle-single-pair-domain-check — tool.io

Similar or alternative tools