check_temperature_record

This function performs basic tests to determine whether a temperature record
complies with chillR's formatting rules. If desired, the function also checks
whether the record is complete (has rows for all time units in the interval)
and how many values are missing.

utilities

The phenology of plants (i.e. the timing of their annual life
phases) depends on climatic cues. For temperate trees and many other plants,
spring phases, such as leaf emergence and flowering, have been found to result
from the effects of both cool (chilling) conditions and heat. Fruit tree
scientists (pomologists) have developed some metrics to quantify chilling
and heat (e.g. see Luedeling (2012) <doi:10.1016/j.scienta.2012.07.011>).
'chillR' contains functions for processing temperature records into
chilling (Chilling Hours, Utah Chill Units and Chill Portions) and heat units
(Growing Degree Hours). Regarding chilling metrics, Chill Portions are often
considered the most promising, but they are difficult to calculate. This package
makes it easy. 'chillR' also contains procedures for conducting a PLS analysis
relating phenological dates (e.g. bloom dates) to either mean temperatures or
mean chill and heat accumulation rates, based on long-term weather and phenology
records (Luedeling and Gassner (2012) <doi:10.1016/j.agrformet.2011.10.020>).
As of version 0.65, it also includes functions for generating weather
scenarios with a weather generator, for conducting climate change analyses
for temperature-based climatic metrics and for plotting results from such
analyses. Since version 0.70, 'chillR' contains a function for interpolating
hourly temperature records.

Eike Luedeling

chillR

Statistical Methods for Phenology Analysis in Temperate Fruit
Trees

Lars Caspersen

Eduardo Fernandez

check_temperature_record function

<dl><dt>weather</dt>
<dd>object to be tested for whether it contains chillR-compatible
temperature data.</dd>
<dt>hourly</dt>
<dd>boolean parameter indicating whether temp_record contains hourly
data. If not, it is assumed to consist of daily records (the default).</dd>
<dt>completeness_check</dt>
<dd>boolean parameter indicating whether the records should be
checked for completeness.</dd>
<dt>no_variable_check</dt>
<dd>boolean parameter to indicate whether the function should
check if the dataset contains the usual chillR temperature variables. Defaults to
TRUE, but should be set to FALSE for different data formats.</dd></dl>

Arguments

Author

Check a daily or hourly temperature record for compliance with chillR's standards — check_temperature_record

<dl>

<dt>weather</dt>
<dd>object to be tested for whether it contains chillR-compatible
temperature data.</dd>


<dt>hourly</dt>
<dd>boolean parameter indicating whether temp_record contains hourly
data. If not, it is assumed to consist of daily records (the default).</dd>


<dt>completeness_check</dt>
<dd>boolean parameter indicating whether the records should be
checked for completeness.</dd>


<dt>no_variable_check</dt>
<dd>boolean parameter to indicate whether the function should
check if the dataset contains the usual chillR temperature variables. Defaults to
TRUE, but should be set to FALSE for different data formats.</dd>

</dl>

check_temperature_record: Check a daily or hourly temperature record for compliance with chillR's standards

Description

Usage

Value

Arguments

Author

References

Examples