Skip to content

Main content

Storm Inter Event Gap

Compare a supplied dry interval with an explicit inclusive storm-separation rule without selecting a storm definition.

Loading tool…

Description

Separate storm events under a supplied inter-event gap rule.

Weather accumulation records need explicit reset, carry, observation-time and area-weight conventions. Trace or missing precipitation differs from measured zero, and radar dBZ must be converted to a linear basis before a linear reflectivity mean. Supplied density, timing and weighting terms do not create a forecast or verify actual weather conditions.

Separate storm events under a supplied inter-event gap rule.

When to use this tool

Use Storm Inter Event Gap when you already have previousEndHours, nextStartHours, suppliedSeparationHours and need to separate storm events under a supplied inter-event gap rule.

How to use the tool and how it works

  1. Enter previousEndHours, nextStartHours, suppliedSeparationHours. 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 gapHours, separateUnderRule. Inspect separateUnderRule before interpreting the associated values.

Require nextStartHours>=previousEndHours and separation>=0; return next-start minus previous-end and flag gap>=separation.1

Input fieldMeaning and unitsAccepted input
previousEndHoursPrevious End HoursRequired. Finite number.
nextStartHoursAt least previousEndHours; overlapping storm intervals are rejected.Required. Finite number.
suppliedSeparationHoursSupplied Separation HoursRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
gapHoursGap HoursRequired. Finite number.
separateUnderRuleSeparate Under RuleRequired. Boolean.
json
{
  "input": {
    "previousEndHours": 10,
    "nextStartHours": 18,
    "suppliedSeparationHours": 6
  },
  "output": {
    "gapHours": 8,
    "separateUnderRule": true
  }
}

Limitations and assumptions

  • Equality satisfies the rule, while overlapping intervals are rejected; no storm is detected or meteorological separation threshold selected.
  • 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

Review the original gauge/radar series, clock and accumulation metadata, including resets and missing intervals. Use the complete spatial or process model for basin precipitation, snow or forecasting; local depth contributions and reference gaps do not infer unobserved weather.

References

  1. Calculation and input contract: hydrometeorology/storm-inter-event-gap — tool.io

Similar or alternative tools