Description
Calculate an accumulation increment using a supplied reset reference.
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.
Calculate an accumulation increment using a supplied reset reference.
When to use this tool
Use Weather Forcing Accumulation Offset when you already have currentAccumulation, precedingAccumulation, resetOccurred, resetBase and need to calculate an accumulation increment using a supplied reset reference.
How to use the tool and how it works
- Enter currentAccumulation, precedingAccumulation, resetOccurred, resetBase. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read increment. Use the output convention below.
Return current-resetBase when resetOccurred=true, otherwise current-precedingAccumulation.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| currentAccumulation | Current Accumulation | Required. Finite number. |
| precedingAccumulation | Preceding Accumulation | Required. Finite number. |
| resetOccurred | When true subtract resetBase rather than precedingAccumulation; signed increments are retained. | Required. Boolean. |
| resetBase | Reset Base | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| increment | Increment | Required. Finite number. |
{
"input": {
"currentAccumulation": 18,
"precedingAccumulation": 12,
"resetOccurred": false,
"resetBase": 0
},
"output": {
"increment": 6
}
}Limitations and assumptions
- All inputs may be signed; the reset and its reference are asserted, not detected, and the result need not include accumulation lost before a reset.
- 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
Similar or alternative tools
- Precipitation Accumulator Reset Difference
Calculate a precipitation-accumulator increment with a known-zero-reset switch.
- Precipitation Reporting Window Carry Offset
Adjust a reported accumulation under an explicit carry-in/carry-out sign convention.