What Consecutive Dry Days represents
A day is dry when precipitation is strictly below the entered threshold. The algorithm resets the run on a day meeting or exceeding threshold.
Consecutive Dry Days begins with dry-day threshold, day 1 precipitation, day 2 precipitation, day 3 precipitation, day 4 precipitation, day 5 precipitation, day 6 precipitation, day 7 precipitation. Label each input as observed, homogenized, modeled, assumed, or derived, and preserve its site, spatial support, calendar period, reference interval, and aggregation method.
Where the climate model stops
Longer climate indices need complete seasonal records and explicit missing-day rules. Gauge errors and threshold choice can split runs.
Consecutive Dry Days is transparent arithmetic, not an official climate normal, drought declaration, seasonal forecast, attribution study, agricultural recommendation, water allocation, or operational safety authority.
Continue the Consecutive Dry Days workflow with the related Average Diurnal Temperature Range Calculator, retaining the same calendar, reference period, and dataset support.
Uncertainty and sensitivity
Vary the least certain Consecutive Dry Days input over a credible range and report how far maximum consecutive dry days moves. Display digits cannot overcome short records, station moves, retrieval changes, sampling gaps, or uncertain PET coefficients.
That Consecutive Dry Days range is a sensitivity check, not automatically a confidence interval. It omits autocorrelation, spatial dependence, structural breaks, reference-period uncertainty, and model-form error outside the displayed fields.
Normals, anomalies, and standardization
A normal is a defined reference-period average; an anomaly subtracts a reference; a standardized value also divides by reference variability. Consecutive Dry Days must retain which operation and period were used.
Rebaselining can change a Consecutive Dry Days anomaly without changing the observation. Mixing reference means or standard deviations from different periods breaks the intended comparison.
Probability and percentile conventions
Percentiles in Consecutive Dry Days depend on sample, tie handling, and empirical ranking. Date probabilities additionally depend on the selected distribution and whether the event is defined as occurring by or after a target date.
A 50% fitted Consecutive Dry Days probability at a mean date is not a deterministic forecast. Climate nonstationarity and small tail samples can make historical probabilities poor descriptions of a future year.
Water balance and PET conventions
Precipitation, PET, actual evapotranspiration, runoff, and soil storage are distinct. Consecutive Dry Days should preserve the PET method because Hargreaves, Thornthwaite, and physically based methods can disagree.
Annual ratios inside Consecutive Dry Days hide seasonality. The same annual precipitation and PET can accompany very different monthly water availability, snow storage, and ecosystem response.
Continue the Consecutive Dry Days workflow with the related Standardized Temperature Anomaly Calculator, retaining the same calendar, reference period, and dataset support.
Keeping an auditable record
Save raw Consecutive Dry Days inputs, conversions, thresholds, coefficient sources, formula version, unrounded output, rounded result, and flags. A reviewer should reproduce the answer without guessing calendar, reference period, or missing-data treatment.
When a source series changes, create a dated Consecutive Dry Days revision and preserve the prior result. Label quality-control corrections separately from a later observation or alternative scenario.
Continue the Consecutive Dry Days workflow with the related Climate Trend Slope Calculator, retaining the same calendar, reference period, and dataset support.
Formula and unit path
The working relationship is Longest run with precipitation < threshold. Consecutive Dry Days uses only displayed inputs and retrieves no station series, gridded data, normals, forecasts, or climate classifications.
Carry temperature scale, precipitation depth, day-of-year calendar, duration, and denominator units through Consecutive Dry Days. Keep an absolute anomaly separate from a standardized anomaly, and keep a fitted probability separate from an observed frequency.
Checked numerical example
The displayed sequence with 1 mm threshold returns exactly 3 consecutive dry days.
Reset restores this Consecutive Dry Days example. Repeat it independently with the stated threshold, endpoint, tie, or distribution convention before substituting climate observations.
Assembling compatible climate inputs
Use complete daily totals under one accumulation clock and threshold. Distinguish trace, zero, missing, and corrected precipitation.
For Consecutive Dry Days, record station or grid identifier, coordinates, elevation, dataset version, valid calendar, reference period, missing-data rule, homogenization status, spatial weighting, units, and quality flags as applicable.
Interpreting Maximum consecutive dry days
The default series has a three-day dry run on days four through six. It describes only the seven displayed days.
Compare Consecutive Dry Days outputs only after aligning variable definition, temporal scale, season, reference record, threshold, distribution method, and spatial support. Similar numbers can represent different climate constructs.
Boundary and sanity checks
A value exactly equal to threshold is not dry under the strict-less-than convention.
Change one Consecutive Dry Days input at a time and predict the response. This exposes reversed frost dates, inclusive-versus-exclusive duration errors, zero denominators, mismatched Celsius and Kelvin, and threshold equality mistakes. For Consecutive Dry Days, also record how leap days, trace values, incomplete periods, ties, and endpoint inclusion were handled so later recalculation uses the same climate convention.
Frequent climate-calculation errors
Typical Consecutive Dry Days errors include averaging averages with unequal support, counting missing precipitation as zero, mixing calendar and water years, using maximum width instead of mean, or fitting a trend from only selected endpoints.
Reject impossible Consecutive Dry Days combinations rather than forcing an answer. Preserve true zero, trace, censored, and missing states separately; keep threshold equality explicit; and test whether the result changes when the reference period changes.
Checking this climate statistic
When should I recalculate?
Recalculate Consecutive Dry Days when the dataset, site, valid period, reference interval, threshold, method, or source value changes.
What does Consecutive Dry Days calculate?
Consecutive Dry Days calculates maximum consecutive dry days from the displayed climate inputs and formula.
Can forecast or scenario values be entered?
Yes. Label the Consecutive Dry Days output as a scenario; the page does not fetch or validate a forecast.
How can I verify Consecutive Dry Days?
Repeat Longest run with precipitation < threshold with recorded conversions, then test the checked example and a boundary.
Why could an official source differ?
Official products may use different station histories, grids, reference periods, missing-data rules, distributions, PET methods, thresholds, or rounding than Consecutive Dry Days.
Does this create an official climate classification?
No. Consecutive Dry Days does not replace authoritative normals, drought products, seasonal outlooks, or qualified climate analysis.