Heat Wave Shriveling Risk Days
Count caller heat-wave duration policy on observed maximum temperatures; not baseline-percentile WSDI, measured berry water loss or shriveling/damage diagnosis.
Description
A heat spell is a consecutive run of days meeting a temperature policy.
A heat spell is a consecutive run of days meeting a temperature policy. Its duration depends on both the strict threshold and minimum run length.
Count caller heat-wave duration policy on observed maximum temperatures; not baseline-percentile WSDI, measured berry water loss or shriveling/damage diagnosis.
When to use Heat Wave Shriveling Risk Days
Use this tool to count caller heat-wave duration policy on observed maximum temperatures; not baseline-percentile WSDI, measured berry water loss or shriveling/damage diagnosis.
Prepare vineyard measurements, dates or block records for the intended growing period. Keep weights, counts and weather observations in the stated units.
How to use Heat Wave Shriveling Risk Days and understand its results
- Prepare vineyard measurements, dates or block records for the intended growing period. Keep weights, counts and weather observations in the stated units.
- Enter dailyMaximumTemperaturesC, callerHeatThresholdC, callerMinimumHeatRunDays using the field table and calculation rules, then run the tool.
- Read qualifyingHeatSpellStartIndices, qualifyingHeatSpellLengthsDays, totalQualifyingHeatExposureDays. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| dailyMaximumTemperaturesC | Daily maximum temperatures c | list of number | Required |
| callerHeatThresholdC | Caller heat threshold c | number | Required |
| callerMinimumHeatRunDays | Caller minimum heat run days | integer | Required |
Supply a nonempty gap-free daily sequence and positive integer minimum run length. Find runs strictly above the threshold, return zero-based start indices and lengths, and sum qualifying days.1
qualifying run: daily maximum > threshold for at least minimum days Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| qualifyingHeatSpellStartIndices | Qualifying heat spell start indices | list of number |
| qualifyingHeatSpellLengthsDays | Qualifying heat spell lengths days | list of number |
| totalQualifyingHeatExposureDays | Total qualifying heat exposure days | number |
{
"input": {
"dailyMaximumTemperaturesC": [
20,
40,
40,
20,
40
],
"callerHeatThresholdC": 35,
"callerMinimumHeatRunDays": 2
},
"output": {
"qualifyingHeatSpellStartIndices": [
1
],
"qualifyingHeatSpellLengthsDays": [
2
],
"totalQualifyingHeatExposureDays": 2
}
}Limitations and assumptions
This is not a baseline-percentile index, measured berry dehydration or damage diagnosis.
Numbers and computed results must be finite; overflow produces an error. Numeric lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Mildew Infection Period GDM Checker: Audit continuous leaf-wet intervals wholly within caller downy-mildew temperature policy and wet duration; observed exposure criterion is not pathogen presence, validated GDM disease model, infection proof or spray recommendation. For a complementary task, use Frost Risk Budbreak Date Estimate: Locate caller heat-sum budbreak proxy then audit observed subsequent frost, not a repeat GDD accumulator or validated phenology/damage forecast; start/reset and heat calibration must be independently established.
References
-
Heat Wave Shriveling Risk Days — tool.io
Similar or alternative tools
- Mildew Infection Period GDM Checker
Audit continuous leaf-wet intervals wholly within caller downy-mildew temperature policy and wet duration; observed exposure criterion is not pathogen presence, validated GDM disease model, infection proof or spray recommendation.
- Frost Risk Budbreak Date Estimate
Locate caller heat-sum budbreak proxy then audit observed subsequent frost, not a repeat GDD accumulator or validated phenology/damage forecast; start/reset and heat calibration must be independently established.