Description
Adjust a reported accumulation under an explicit carry-in/carry-out sign convention.
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.
Adjust a reported accumulation under an explicit carry-in/carry-out sign convention.
When to use this tool
Use Precipitation Reporting Window Carry Offset when you already have reportedAccumulation, carryIn, carryOut and need to adjust a reported accumulation under an explicit carry-in/carry-out sign convention.
How to use the tool and how it works
- Enter reportedAccumulation, carryIn, carryOut. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read windowAccumulation. Use the output convention below.
Require all inputs>=0; return reportedAccumulation-carryIn+carryOut.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| reportedAccumulation | Reported Accumulation | Required. Finite number; minimum 0. |
| carryIn | Carry In | Required. Finite number; minimum 0. |
| carryOut | Carry Out | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| windowAccumulation | reportedAccumulation-carryIn+carryOut; both corrections must use the supplied window convention. | Required. Finite number. |
{
"input": {
"reportedAccumulation": 12,
"carryIn": 2,
"carryOut": 3
},
"output": {
"windowAccumulation": 13
}
}Limitations and assumptions
- The terms use this supplied sign convention and common depth/time basis; negative results are retained and reporting-window allocation is not inferred.
- 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
- Weather Forcing Accumulation Offset
Calculate an accumulation increment using a supplied reset reference.
- Precipitation Accumulator Reset Difference
Calculate a precipitation-accumulator increment with a known-zero-reset switch.