Skip to content

Main content

Rainfall Tip Resolution Uncertainty Bound Tool

Tipping-bucket accumulated completed tips with an optional unknown residual below one tip; excludes gauge catch and calibration uncertainty.

Loading tool…

Description

Multiply nonnegative integer tips by positive depthPerTip for recordedDepth and lowerDepth.

Event boundaries and partial observation intervals depend on a chosen endpoint convention. Equality at a supplied threshold may change a classification even when the underlying measurements are unchanged.

Multiply nonnegative integer tips by positive depthPerTip for recordedDepth and lowerDepth.

When to use this tool

Use Rainfall Tip Resolution Uncertainty Bound when you need to apply an explicit interval or event-separation rule.

How to use the tool and how it works

  1. Enter tips, depthPerTip, includePartialTip. 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 recordedDepth, lowerDepth, upperExclusiveDepth. Use the output convention below.

Multiply nonnegative integer tips by positive depthPerTip for recordedDepth and lowerDepth. Add one tip to the upperExclusiveDepth multiplier only when includePartialTip.1

Input fieldMeaning and unitsAccepted input
tipsTipsRequired. Safe integer; minimum 0.
depthPerTipDepth Per TipRequired. Finite number; strictly above 0.
includePartialTipInclude Partial TipRequired. Boolean.
Output fieldInterpretationReturned shape
recordedDepthRecorded DepthRequired. Finite number.
lowerDepthLower DepthRequired. Finite number.
upperExclusiveDepthUpper endpoint under the supplied partial-tip convention; coincides with recorded depth when no partial tip is allowed.Required. Finite number.
json
{
  "input": {
    "tips": 10,
    "depthPerTip": 0.2,
    "includePartialTip": true
  },
  "output": {
    "recordedDepth": 2,
    "lowerDepth": 2,
    "upperExclusiveDepth": 2.2
  }
}

Limitations and assumptions

  • This is the supplied partial-tip bookkeeping policy, not a statistical uncertainty interval. With no partial allowance the bounds coincide, so upperExclusiveDepth must not be read as an independently justified measurement bound.
  • 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

Document the observation resolution and event-definition policy before comparing records from different sources.

References

  1. Calculation and input contract: hydrometeorology/rainfall-tip-resolution-uncertainty-bound — tool.io

Similar or alternative tools