Package Wux': R Topics Documented
Package Wux': R Topics Documented
Package Wux': R Topics Documented
R topics documented:
wux-package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
alpinesummer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
aovWux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
AverageWuxDataFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
cmip3_2050 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1
2 wux-package
cmip3_2100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
CMIP5fromESGF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
CMIP5toModelinput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
cmip5_2050 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
cmip5_2100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
CMIP5_example_changesignal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
CMIP5_example_timeseries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
ensembles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
ensembles_gcms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
hist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
modelinput_test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
models2wux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
plot.wux.aov . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
plot.wux.df . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
plotAnnualCycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
read.wux.table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
reconstruct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
userinput_CMIP5_changesignal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
userinput_CMIP5_timeseries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Index 42
Description
The WUX package is a toolbox to analyze climate change uncertainties projected by numerical
model simulations.
The package provides methods to calculate and interpret climate change signals and time series
from entire multi-model ensembles. Climate model output in binary NetCDF format is read in and
aggregated to a data.frame for statistical analysis with tools provided by the R environment. The
NetCDF format is not restricted to any specific type of climate model. Global circulation models
(GCMs), as the CMIP5 or CMIP3 simulations, can be read in the same way as Regional Climate
Models (RCMs), as e.g. the CORDEX or ENSEMBLES simulations.
Details
This package can currently perform following actions:
• Reading output of climate model simulations from NetCDF files, processing it, and writing it
to a data.frame (the so-called WUX data frame).
• Various plotting options and summarizing utilities for a descriptive analysis of the projected
climate change signals.
• Performing an Analysis of Variance (ANOVA) in order to estimate variance components.
• Performing a simple two-way linear data reconstruction, in order to fill the missing values of
a simulation matrix as e.g. the GCM-RCM simulation matrix of ENSEMBLES.
wux-package 3
Functions:
models2wux Reads NetCDF climate model output, processes it, and writes the results to a data.fram
CMIP5fromESGF Automated downloading of the CMIP5 multi-model climate ensemble
read.wux.table Reads in wux csv file obtained from models2wux from harddisk and creates a data frame
AverageWuxDataFrame WUX data frame averaging function
Datasets:
userinput_CMIP5_changesignal,
userinput_CMIP5_timeseries,
modelinput_test Example config files for models2wux
ensembles, ensembles_gcms,
cmip3_2050, cmip3_2100,
cmip5_2050, cmip5_2100,
CMIP5_example_changesignal,
CMIP5_example_timeseries,
alpinesummer Example data frames calculatated by models2wux
Author(s)
Description
An example temperature timerseries for one subregion Greater Alpine Region (GAR) models2wux
in summer (JJA) of the CMIP5 ensemble for RCP 4.5. This is what a timeseries result from
models2wux would look like.
Usage
data(alpinesummer)
See Also
models2wux
Examples
Description
Usage
Arguments
Value
Returns a object of class wux.aov, a list containing the ANOVA results for each subregion and
season. The names of the list entries are "subreg = xx;season = yy".
Author(s)
Examples
## read WUX test data
library("wux")
data(ensembles)
## calculate ANOVA
anova.list <- aovWux(perc.delta.precipitation_amount ~ acronym +
gcm, reconstruct.df)
6 cmip3_2050
Description
Collapses WUX data frame by averaging over specified factor (column name). The chosen data
frame column will disappear after aggregation.
This function is primarly used to average over model runs (see example).
Usage
AverageWuxDataFrame(x, INDEX, fun = "mean")
Arguments
x wux data.frame (returned by models2wux or read.wux.table)
INDEX character column names from wux data.frame over which aggregation should
take place. Those columns will dissapear after aggregation
fun keyword for aggregation function. Default is mean
Author(s)
Thomas Mendlik <thomas.mendlik@uni-graz.at>
Examples
## load WUX and read WUX test data
require(wux)
data(cmip3_2050)
Description
This dataset contains air temperature and precipitation climate change signals of all climate sim-
ulations from the CMIP3 project from 1961-1990 to 2021-2050. Subregions are defined accord-
ing to the CORDEX project. Subregion EU.ENS contains the European region defined in the EN-
SEMBLES project and World contains the entire earth. http://wcrp.ipsl.jussieu.fr/SF_RCD_
CORDEX.html.
cmip3_2100 7
Details
This dataset is an exemplary output of models2wux.
Source
CMIP3 project: http://www-pcmdi.llnl.gov
References
Meehl, G. A., C. Covey, T. Delworth, M. Latif, B. McAvaney, J. F. B. Mitchell, R. J. Stouffer, and
K. E. Taylor, 2007: The WCRP CMIP3 multi-model dataset: A new era in climate change research,
Bulletin of the American Meteorological Society, 88, 1383-1394.
Examples
require(wux)
data(cmip3_2050)
str(cmip3_2050)
summary(cmip3_2050)
## End(Not run)
Description
This dataset contains air temperature and precipitation climate change signals of all climate sim-
ulations from the CMIP3 project from 1961-1990 to 2071-2100. Subregions are defined accord-
ing to the CORDEX project. Subregion EU.ENS contains the European region defined in the EN-
SEMBLES project and World contains the entire earth. http://wcrp.ipsl.jussieu.fr/SF_RCD_
CORDEX.html.
Details
This dataset is an exemplary output of models2wux.
Source
CMIP3 project: http://www-pcmdi.llnl.gov
8 CMIP5fromESGF
References
Meehl, G. A., C. Covey, T. Delworth, M. Latif, B. McAvaney, J. F. B. Mitchell, R. J. Stouffer, and
K. E. Taylor, 2007: The WCRP CMIP3 multi-model dataset: A new era in climate change research,
Bulletin of the American Meteorological Society, 88, 1383-1394.
Examples
require(wux)
data(cmip3_2100)
str(cmip3_2100)
summary(cmip3_2100)
## End(Not run)
CMIP5fromESGF Downloads CMIP5 climate simulations from the ESGF data portal
Description
Downloads available monthly CMIP5 simulations from ESGF data portal. You need an account
at any ESGF node (see http://cmip-pcmdi.llnl.gov/cmip5/data_getting_started.html).
This function creates subdirectories for each climate simulation in the specified folder, automati-
cally recieves the bash scripts needed for the partiular simulation-variable-experiment combination
and then executes the bash scripts one by one. An external PYTHON script is called for this task.
If either data or bash-scripts exist, the download will be skipped. Use this function with care. You
need a working internet connection for this function to work.
Usage
CMIP5fromESGF(save.to = NULL, variables = NULL,
experiments = NULL, models = NULL)
Arguments
save.to Directory location for downloading CMIP5 data and bash scripts. ATTEN-
TION: subdirectories for each model-experiment combination will be created!
CMIP5fromESGF 9
variables Short variable names for meteorological parameters of interest (e.g. "tas" for 2m
air temperature or "pr" for precipitation amount). See e.g. the IPCC Standard
Output from GCMs (http://www-pcmdi.llnl.gov/ipcc/standard_output.
html).
experiments Experiment of the climate simulation (e.g. c("historical", "rcp45"), see Taylor
(2012) for a detailed description.
models Climate simulations to be downloaded. If no models are provided (default),
all available simulations will be retrieved. See the "Model" column at http://
cmip-pcmdi.llnl.gov/cmip5/availability.html for available simulations.
ATTENTION: This is a considerable amount of data, so watch out for your
diskspace!
Details
Firstly you need an ESGF account. If you do not have any, start here: http://cmip-pcmdi.llnl.
gov/cmip5/data_getting_started.html
This function calls an external python script which
You can find the location of the script with system.file("exec", "CMIP5_downloader.py", package="wux")
This function is an alternative to downloading the corresponding models by point-and-click on the
ESGF node (as http://pcmdi9.llnl.gov or http://esgf-data.dkrz.de), as it takes advantage
of the ESGF search API mechanism for automated data screening and wget-script generation. For
thei nterested user more information on downloading strategies is available at https://github.
com/ESGF/esgf.github.io/wiki/ESGF_Data_Download_Strategies.
Warning
This function automatically creates new directories on your system, downloads wget scripts, flags
them execueable and runs them, which can download quite some data.
Note
Use with care, your harddisk might get stuffed. This tools works on unix platforms only.
Author(s)
Thomas Mendlik <thomas.mendlik@uni-graz.at>
References
Karl E. Taylor, Ronald J. Stouffer, and Gerald A. Meehl, 2012: An Overview of CMIP5 and the
Experiment Design. Bull. Amer. Meteor. Soc., 93, 485-498. doi: http://dx.doi.org/10.1175/BAMS-
D-11-00094.1
10 CMIP5toModelinput
Examples
## Not run:
## download temperature fields of two example GCMs (NorESM1-M and
## CanESM2) with the RCP 8.5 and the historical run
## into your temporary directory. This command will create a folder
## "CMIP5" in "~/tmp" with two subfolders for each model again with
## two subfolders for each experiment.
CMIP5fromESGF(save.to = "~/tmp/CMIP5/",
models = c("NorESM1-M", "CanESM2"),
variables = c("tas"),
experiments= c("historical", "rcp85"))
## End(Not run)
CMIP5toModelinput Creates a "modelinput" input file based on CMIP5 data on your disk
to be further processed by models2wux.
Description
This function creates a "modelinput" list (written into a file). That file can then be used to have all
the relevant CMIP5 model information available for "models2wux". The input for this function is
the directory where CMIP5fromESGF saves all the data. It is crucial for this funcion that the data
is saved in the same directory strucure as created by "CMIP5fromESGF" (GCMname/RCP) . This
function works for CMIP5 data on monthly basis only and can currently process only the parameters
"air_temperature" and "precipitation_amount".
Usage
Arguments
filedir: Direcotry where the CMIP5 data are being stored. It is crucial for
this funcion that the data is saved in the same directory strucure as created by
"CMIP5fromESGF". save.to: character. Filename to safe the modelinupt. ver-
bose: boolean. For additional information printed on the screen.
Direcotry where the CMIP5 data are being stored. It is crucial for this funcion
that the data is saved in the same directory strucure as created by CMIP5fromESGF.
filedir
save.to character. Filename to safe the modelinupt.
verbose boolean. For additional information printed on the screen.
cmip5_2050 11
Details
This function is based on the data obtained by CMIP5fromESGF. However, it is also possible to
download the data manually and run this function. The directory structure must look like this:
"GCMname/RCP" (e.g. /tmp/CMIP5/NorESM1-M/rcp85).
In the background a PYTHON script is executed. You can find the file by typing the command
system.file("exec", "cmip5_to_wux_modeldict.py", package="wux")
Note
Author(s)
References
Karl E. Taylor, Ronald J. Stouffer, and Gerald A. Meehl, 2012: An Overview of CMIP5 and the
Experiment Design. Bull. Amer. Meteor. Soc., 93, 485-498. doi: http://dx.doi.org/10.1175/BAMS-
D-11-00094.1
Examples
## Not run:
## download temperature fields of two example GCMs (NorESM1-M and
## CanESM2) with the RCP 8.5 and the historical run
## into your temporary directory. This command will create a folder
## "CMIP5" in "~/tmp" with two subfolders for each model again with
## two subfolders for each experiment.
CMIP5fromESGF(save.to = "~/tmp/CMIP5/",
models = c("NorESM1-M", "CanESM2"),
variables = c("tas"),
experiments= c("historical", "rcp85"))
## End(Not run)
Description
This dataset contains air temperature and precipitation climate change signals of all climate sim-
ulations from the CMIP5 project from 1961-1990 to 2021-2050. Subregions are defined accord-
ing to the CORDEX project. Subregion EU.ENS contains the European region defined in the EN-
SEMBLES project and World contains the entire earth. http://wcrp.ipsl.jussieu.fr/SF_RCD_
CORDEX.html.
Details
Source
References
Karl E. Taylor, Ronald J. Stouffer, and Gerald A. Meehl, 2012: An Overview of CMIP5 and the
Experiment Design. Bull. Amer. Meteor. Soc., 93, 485-498. doi: http://dx.doi.org/10.1175/BAMS-
D-11-00094.1
Examples
require(wux)
data(cmip5_2050)
str(cmip5_2050)
summary(cmip5_2050)
## End(Not run)
Description
This dataset contains air temperature and precipitation climate change signals of all climate sim-
ulations from the CMIP5 project from 1961-1990 to 2071-2100. Subregions are defined accord-
ing to the CORDEX project. Subregion EU.ENS contains the European region defined in the EN-
SEMBLES project and World contains the entire earth. http://wcrp.ipsl.jussieu.fr/SF_RCD_
CORDEX.html.
Details
Source
References
Karl E. Taylor, Ronald J. Stouffer, and Gerald A. Meehl, 2012: An Overview of CMIP5 and the
Experiment Design. Bull. Amer. Meteor. Soc., 93, 485-498. doi: http://dx.doi.org/10.1175/BAMS-
D-11-00094.1
Examples
require(wux)
data(cmip5_2100)
str(cmip5_2100)
summary(cmip5_2100)
## End(Not run)
CMIP5_example_changesignal
Climate change signals of example userinput for models2wux
14 CMIP5_example_timeseries
Description
This example of a WUX data.frame is the result of running userinput_CMIP5_changesignal with
models2wux.
Usage
data(CMIP5_example_changesignal)
Details
You can download the NetCDF files from ESGF using CMIP5fromESGF.
See Also
models2wux
Examples
## thats what CMIP5_changesignal looks like
data("CMIP5_example_changesignal")
CMIP5_example_changesignal
CMIP5_example_timeseries
Climate change signals of example userinput for models2wux
Description
This example of a WUX data.frame is the result of running userinput_CMIP5_timeseries with
models2wux.
Usage
data(CMIP5_example_timeseries)
ensembles 15
Details
You can download the NetCDF files from ESGF using CMIP5fromESGF.
See Also
models2wux
Examples
## thats what CMIP5_timeseries looks like
data("CMIP5_example_timeseries")
head(CMIP5_example_timeseries)
Description
This dataset contains air temperature and precipitation climate change signals of all 22 A1B forced
climate simulations from the ENSEMBLES project from 1961-1990 to 2021-2050.
Usage
data(ensembles)
Source
The ENSEMBLES project: http://www.ensembles-eu.org/
References
van der Linden P, Mitchell JFB. 2009. ENSEMBLES: Climate Change and its Impacts: Summary
of research and results from the ENSEMBLES project. Met Office Hadley Centre: Exeter.
16 ensembles_gcms
Examples
require(wux)
data(ensembles)
ensembles <- droplevels(subset(ensembles, subreg == "EU.ENS"))
str(ensembles)
parms <- c("delta.air_temperature", "perc.delta.precipitation_amount",
"delta.global_radiation", "delta.wind_speed")
summary(ensembles, parms = parms)
## End(Not run)
Description
This dataset contains air temperature and precipitation climate change signals of the 8 A1B driving
GCMs used as boundary conditions for the ENSEMBLES RCMs. The climate change signal is
from 1961-1990 to 2021-2050.
ensembles_gcms 17
Usage
data(ensembles_gcms)
Source
ENSEMBLES project: http://www.ensembles-eu.org/ CMIP3 project: http://www-pcmdi.
llnl.gov
References
van der Linden P, Mitchell JFB. 2009. ENSEMBLES: Climate Change and its Impacts: Summary
of research and results from the ENSEMBLES project. Met Office Hadley Centre: Exeter.
See Also
cmip3_2050, ensembles, models2wux
Examples
require(wux)
data(ensembles_gcms)
ensembles.gcm.names <- levels(ensembles_gcms$acronym) #8 GCM names
summary(ensembles_gcms)
## Scatterplot
prec.range <- range(gcms.combined$perc.delta.precipitation_amount) + c(-1, 1)
tas.range <- range(gcms.combined$delta.air_temperature)
## Not run: plot(gcms.combined,
"perc.delta.precipitation_amount", "delta.air_temperature",
subreg.subset = "EU.ENS", draw.median.lines = FALSE,
label.only.these.models = ensembles.gcm.names,
xlim = prec.range,
ylim = tas.range,
main = "GCMs from ENSEMBLES project within CMIP3 SRESA1B ensemble",
draw.seperate.legend = TRUE)
## End(Not run)
18 hist
Description
hist plots either one or two histograms and the according kernel density estimates using density.
This plotting routine extracts all the information from the input dataframe which has to be ’WUX-
style’ (see models2wux).
Usage
## S3 method for class 'wux.df'
hist(x, datain2.df = NULL, var.name = "delta.air_temperature",
subreg.subset = NULL, season.subset = NULL, plot.density = TRUE,
Arguments
x 1st WUX dataframe obtained from models2wux.
datain2.df 2nd WUX dataframe obtained from models2wux.
var.name Character string of parameter in WUX dataset. Default is temperature change.
subreg.subset Vector of subregions to be plotted (e.g. c("EU.ENS", "GAR")).
season.subset Vector of seasons to be plotted (e.g. c("MAM", "DJF")).
plot.density Boolean. Indicating if kernel density estimates should be plotted. Default is
TRUE.
hist1.col Character string of the 1st histogram color (e.g. "red").
hist2.col Character string of the 2nd histogram color (e.g. "blue").
bw The smoothing bandwidth to be used in density. Default is "nrd0".
kernel A character string giving the smoothing kernel to be used in density. This must
be one of "gaussian", "rectangular", "triangular", "epanechnikov","biweight",
"cosine" or "optcosine" with default "gaussian".
mark.df Subset of WUX dataframe indicating the models to be marked.
plot.legend Boolean. Indicating if a plot legend indicating the models of mark.df and sample
size should be plotted. Default is FALSE.
xlim Range vector for the x-axis.
ylim Range vector for the y-axis.
xtick.number Number of ticks for the x-axis with default 10.
hist 19
Author(s)
Georg Heinrich <g.heinrich@uni-graz.at>
Examples
## load WUX and read WUX test data
require(wux)
data(ensembles)
## histogram plot
## Not run: hist(x = wuxtest.df, var.name =
"perc.delta.precipitation_amount", xlim = c(-50,50), ylim = c(0,0.12),
xtick.number = 9, xminor.tick = TRUE, ytick.number = 5,
yminor.tick = TRUE, xlab = "Precipitation Amount [%]", main =
"WUX histogram", plot.legend = TRUE, mark.df = mark.df, hist1.col =
"dark blue")
graphics.off()
## End(Not run)
20 modelinput_test
Description
This is an example model specification for WUX, giving information on two example NetCDF
files from the CMIP5 project. The datatype is a list. For specification details see the "Configfile
modelinput" section in models2wux.
Usage
data(modelinput_test)
Details
The two CMIP5 simulations "NorESM1-M" and "CanESM2" (either having historical run and RCP
8.5 forcing) are assumed to be stored in the home directory "~/tmp/CMIP5". You can download
them using CMIP5fromESGF. See the example for a typical workflow.
See Also
models2wux, CMIP5fromESGF
Examples
## Not run:
## Here is how to use the climate model specification file
## "modelinput_test" for models2wux.
## V) ANALYZE data.frame
require(lattice)
wux.test$year <- as.integer(as.character(wux.test$year))
xyplot(air_temperature ~ year|season,
groups=acronym,
data = wux.test,
type = c("l", "g"),
main = "NorESM1-M and CanESM2 simulations over Alpine Region\n
historical and RCP 8.5 forcing")
## End(Not run)
Description
Reads various climate model NetCDF outputs, processes them according to userinput, and writes
the processed data to a data.frame.
The data.frame output of WUX (the WUX data frame) contains the climate change signals for
user-specified periods, regions, seasons, and parameters for each of the indicated climate models as
defined in userinput.
The userinput is a named list object or a file containing a named list. It passes the controlling
parameters to models2wux. The file paths, file names and meta-information on the climate simu-
lations are stored in another list called modelinput. See the "Details" section and the "Configfile
userinput" and "Configfile modelinput" section for a detailed description of these two lists.
Usage
models2wux(userinput, modelinput)
Arguments
userinput The specification of e.g. the parameters, periods, aggregation statistics, seasons,
subregions, and climate models to be processed. This is either a file name con-
taining a list which will be sourced internally, or a list object.
modelinput The specifications of file paths, file names and meta-information of every single
climate simulation output you have stored on your HDD. This is either a file
name containing a list which will be sourced internally, or a list object.
22 models2wux
Details
To process a climate multimodel ensemble of your choice, models2wux needs two config files
userinput and modelinput, both being named list objects or files containing a named list.
modelinput stores general information about your climate data, i.e. the locations of the NetCDF
files and their filenames. It also safes certain metainformation for the specific climate simulations
(e.g. a unique acronym for the simulation; the developing institution; the radiative forcing). Usually
the modelinput information should be stored in a single file on your system and should be updated
when new climate simulations come in. It is advisable to share this file with your collegues if you
work with the same NetCDF files on a shared IT infrastructure.
userinput contains information on what you actually want models2wux to be doing for you,
mainly, which climate simulations defined in modelinput should be processed and what kind of
statistic should be performed. You also define the geographical regions of interest you want to
investigate and what time horizon you want to regard. Here is an overview of all possible tags a
userinput list contains:
This is what models2wux is doing: First, models2wux extracts attributes set in the userinput list
and loads the corresponding model information (storage paths, filenames, ...) from the modelinput
list. It then retrieves the geographical boundaries of the specified regions in subregions (here the
model gridfiles are introduced) and reads the specified parameter data from the NetCDF files within
the boundaries of the actual subregion. Subsequently, models2wux aggregates over the time di-
mension by the indicated months for the specified periods and calculates either the climatological
mean values of the reference and future period and the according climate change signals or time
series. Next, models2wux aggregates over the spatial dimension. models2wux repeats these pro-
cessing steps for each model specified in climate.models, each parameter in parameter.names,
each subregion in subregions, and each period in reference.period and scenario.period, re-
spectively. Finally, the processed data is written to a data.frame and stored to the hard disk as
indicated by save.as.data.
For more detailed information on modelinput and userinput see the corresponding sections
Configfile "modelinput" and Configfile "userinput" in this help page.
Value
A data.frame of class c("wux.df", "data.frame") containing climate change signals for all
models, subregions, and parameters specified in userinput. It also writes a csv file on your HDD.
models2wux 23
Configfile "userinput"
Those are specifications the user provides to control models2wux.
scenario.period: A character specifying the climate change future period defined by "from-to"
("YYYY-YYYY"),
e.g. scenario.period = "2021-2050".
subregions: Named list containing information for geographical regions. You can specify the
boundaries by passing
• a rectangular region by hand
• a shapefile with subregions of interest
• a NetCDF file containing subregions
All longitude coordinate values are forced to the range from -180 to 180 degrees. In case you want
to define a subregion containing the (180,-180)-meridian, you should force the longitude values
to the range from 0 to 360 degrees, as it could be the case for the Australasian domain. This can
be done with the wrap.to-tag (currently defined only for shapefiles).
rectangle: A vector of the form c(lon.west, lon.east, lat.north, lat.south).
e.g. World = c(-180, 180, 90, -90)
shapefile: A named list containing the directory to the shapefiles dirname and the name of the
files filename (without file extension). Optional: If no projection file is available, you can
set a projection tag to
e.g. projection = "+proj=longlat +ellps=WGS84".
24 models2wux
In case there are more regions defined in the shapefile, one can give specific names to the
subregionnames tag e.g subregionnames = c("South_America", "Central_America").
However, sometimes these multiple regions form a set. Then the category.variable tag
merges the subregions with the same category to a single subregion and category.label
gives corresponding labels. category.label has to be a named vector, with the names being
the category values from the category.variable and their values being the labels. Omitting
the category.label vector when using category.variable, WUX tries to get the names
of category.variable. Note that the subregionnames tag and the category.label should
not be used together.
In case you want to wrap your longitudes to the 0-360-degrees grid, flag the named vector
wrap.to = c("my.subregion" = "360"). Example:
CORDEX = list(dirname = "/tmp/shapefiles/cordex", filename = "cordex_regions", subregionnames
NetCDF subregionfile: A named list containing information about the NetCDF file defining the
subregion by a constant value (e.g. all pixels flagged by 1 define a subregion). Names of the
list have to be:
area.fraction: Dealing with gridded data, subregions almost never happen do be cut out
exactly the way your subregion is specified. If the centroid of a single data pixel lies within the
subregion, this datapoint will be taken into analysis, else the datapoint will be considered as lying
outside of the subregion and set NA. This is WUX default behavior (area.fraction = FALSE).
For very small subregions and/or very course data resolution however, it can happen you get very
few data points or even none at all.
However, if you want to take every data pixel which just ’touches’ your subregion, use area.fraction.
The pixel’s centroid doesn’t have to be necessarily inside the subregion to be taken into analysis
then. With area.fraction = TRUE WUX does a weighted spatial average of all these pixels. The
weight is the ratio of the pixel area lying within the subregion and the entire pixel area. So if one
quarter of a data point is wihin the subregion (but its centroid for example is not), the data pixel
value will be taken into analysis and weighted by 0.25 when averaging spatially. Pixels being
covered completely in the subregion have weight 1. area.fraction is useful if you are dealing
with very small subregions and/or small data resolution, resulting in just a few pixels.
spatial.weighting: When averaging data over its spatial component, the simple arithmetic
mean can result in strongly biased areal estimates. The reason for this is due the geographical
projection of the data. The globe has 360 longitudinal degrees and 180 degrees in latitude. The
real distance (km) between latitudes remains the same on the entire globe, whereas the distances
between longitudes depend on the latitude considered. One degree in longitude near equator
represents much more distance (km) than one degree in Norway as the longitudes converge at the
poles.
This fact has to be considered especially when dealing with global data (e.g. GCMs). GCM data
is usually (within WUX so far 100%) stored on a rectangular lon-lat grid. Therefore the poles
seem overproportionaly large in area. Common practice is cosine weighting of latides, resulting
models2wux 25
in smaller weights near the poles and largest weights at the equator. See http://www.grassaf.
org/general-documents/gsr/gsr_10.pdf for more details.
spatial.weighting = TRUE enables cosine weighting of latitudes, whereas omitting or setting
FALSE results in unweighted arithmetic areal mean (default). This option is valid only for data on
a regular grid.
na.rm: It may happen that time slices of NetCDF data may be missing and the user does not
know anything about it. Reason for these artifacts might be short time series (e.g. some models
project only until 2035, so an analysis unitl 2050 would be biased) or simply missing values due
to corrupt or missing NetCDF files.
If na.rm = TRUE is set in the user input, missing values are filled with NA, but the temporal
statistics are calculated using the na.rm = TRUE flag. na.rm = FALSE keeps the NA values and
thus leads to NA statistics.
plot.subregions: A list containing information about diagnostic plotting of grid points within
the subregions. png plots are generated showing the grid points within a subregion. The size of
the drawn circles correspond to the weighting factor of area.fraction. The list contains three
elements: save.subregion.plots, xlim, and ylim.
save.subregion.plots: A character containing only the output path as the filenames are automati-
cally generated via the model and subregion names. For example save.subregion.plots = "/tmp/"
will save the plots in the directory /tmp/. If save.subregion.plots is not specified no plots
will be drawn!
xlim: A vector containing the longitudional boundaries of the plots. For example xlim=c(10,50)
draws the plot from 10 to 50 degrees East. If xlim is not specified the boundaries will be
automatically generated.
ylim: A vector containing the longitudional boundaries of the plots. For example xlim=c(10,50)
draws the plot from 10 to 50 degrees North. If ylim is not specified the boundaries will be
automatically generated.
cex: Factor for pointsize relative to the default.
save.as.data: A character containing both the output path and filename. For example save.as.data = "/tmp/cmip3"
will save files in the directory /tmp/ as cmip3.csv (data frame containing model climatologies),
cmip3_diff.csv (data frame containing the differences of the climatologies, i.e. the climate
change signals) and cmip3.Rdata (a R binary file which can be loaded into the next R session
containing variables wux.data and wux.data.diff data frames analog to the csv-files).
climate.models: A character vector containing the names of the models to be processed. The
names must be identical to the unique acronyms in the modelinput list. Read the next section if
you want to add a model in the modelinput file.
Configfile "modelinput"
When you want to read in a new climate simulation WUX does not know so far, all you need to do
is to specify this model in the modelinput list (which should be stored in a file). You don’t need to
write tedious input routines, WUX does that for you. The modelinput list is a named list of climate
models and contains meta-information of all currently known climate models. Sometimes models
indicate wrong attributes in their NetCDF files needed by modelinput. Therfore: KNOW YOUR
MODEL YOU WANT TO ADD AND TAKE CARE OF THE META-INFORMATION YOU ARE
INDICATING IN modelinput.
26 models2wux
Each tag consists of a named list with the following mandatory tags (i.e. names):
rcm: Character name indicating the RCM acronym; if you are processing a gcm type "".
file.path.default: Default directory of the NetCDF data files. If the files are stored not only
in one directory, use the file.path.alt tag (see below).
file.path.alt: If your files are stored not only in one directory, here you can enter a named
vector of paths. If files are scattered by parameter, pass the parameter name (CF Metadata con-
vention) as the vector name. If they are split by periods, then pass historical and scenario as
vector names. If files are seperated by both period and parameter, you can use nested named lists
instead of vectors.
file.name: Character vector of file names of the NetCDF data files. If there are different file
names for parameters (which will be mostly the case) and/or file names in scenario- and historical
period are of different nature as well, use named or nested lists as in the file.path.alt tag. You
can set this tag NA if this climate model has no files. This makes sense for example for the GKSS
model for global radiation, as this ENSEMBLES model does not provide this parameter. Values
for this model will be NA in the WUX dataframe.
what.timesteps: Default are daily time steps, type "monthly" for monthly data.
calendar: Define the NetCDF time:calender attribute by hand. This is necessary if the NetCDF
file contains wrong information. You can pass 360_days, no_leap or julian.
time.units: Define the NetCDF time:units attribute by hand. E.g. days since 1950-01-06 00:00:00.
count.first.time.value: The time variable in NetCDF files is a vector of time steps relative
to the "time:units" attribute with calendar according to the "time:calendar" attribute. However,
there are cases where certain climate models are dealing with two calendar types at once! Yes,
that’s possible... For example: Data claim to have a "360 days" calendar. The "time:units" at-
tribute is set to days since 1961-01-01 00:00:00 and the time vector looks like
365, 366, ..., 723, 724. The 365th day since 1961-01-01 is definetely not the 1st January of
1962 concerning the 360-days calendar but is correctly in terms of "julian" dates.
In such a case we would set count.first.time.value = "julian" and calendar remains 360
days. Other possibilities are count.first.time.value = "noleap" (or = "360days").
Currently this property is defined for calendar = "360 days" only, but can easily be
extended to other calendars as well.
models2wux 27
parameters: A named vector indicating parameter long- and shortname which belong together,
e.g. parameters = c(air_temperature = "tas_dm", precipitation_amount = "pr_24hc").
This is important if the NetCDF internal variable name deviates from the WUX default parameter
shortname:
Note
This is an awesome tool (rfp).
Author(s)
Thomas Mendlik <thomas.mendlik@uni-graz.at> and Georg Heinrich <g.heinrich@uni-graz.at>
See Also
modelinput_test, userinput_CMIP5_changesignal, cmip5_2050, cmip5_2100, ensembles, ensembles_gcms
Examples
## This example shows a typical workflow for models2wux, the workhorse of
## the wux package. Going through this example step-by-step, you will
## retrieve NetCDF files of two CMIP5 simulations and aggregate them to
## an R data.frame for further analysis.
## II) You need to obtain the climate simulations first. You can get
## started with downloading some example CMIP5 NetCDF files from the
## ESGF visiting for example http://pcmdi9.llnl.gov or using the
## CMIP5fromESGF function. Here, we dowload two simulations "NorESM1-M" and
## "CanESM2" into your home directory "~/tmp/CMIP5/" which will be
## created automatically. You will need a valid account at any ESGF
## node for this function to run. See ?CMIP5fromESGF for further help.
## Not run: CMIP5fromESGF(save.to = "~/tmp/CMIP5/",
models = c("NorESM1-M", "CanESM2"),
28 models2wux
variables = c("tas"),
experiments= c("historical", "rcp85"))
## End(Not run)
## End(Not run)
## This file then would look this:
data(modelinput_test)
## IV) Next, you need to specify which simulations you want to read in
## with models2wux, what kind of statistics to calculate, what subregion
## to analyze, what time periods and seasons to define, and so on. This
## is done with a user input file, which cntains a list with all the
## necessary information. You typically use different userinput files
## for different analysis, whereas your modelinput should remain in ONE
## file which will be updated each time you obtain a new climate
## simulation. One example user input file, which reads in both
## simulations specified above for the Alpine domain and returns their
## projected climate change signal, could look like follows:
data(userinput_CMIP5_changesignal)
str(userinput_CMIP5_changesignal)
## End(Not run)
## VI) Finally you can make all kind of analysis you are interested in,
## using either functions from wux or from any other R funtionality
summary(CMIP5_example_changesignal, parms = "delta.air_temperature")
## or plot timeseries as
require(lattice)
data(CMIP5_example_timeseries)
## Not run: xyplot(air_temperature ~ year|season,
groups = acronym,
data = CMIP5_example_timeseries,
type = c("l", "g"),
main = "NorESM1-M and CanESM2 simulations over Alpine Region\nRCP 8.5 forcing")
## End(Not run)
Description
Barplots of the aovWux results displaying the relative or absolute contribution of the individual
factors to the overall variance.
Usage
## S3 method for class 'wux.aov'
plot(x, ss.relative = TRUE, subreg.subset =
NULL, cex.names = 1.2, cex.lab = 1.2, legend.text = NULL, sd.text =
TRUE, sd.unit = "", ylim = NULL, ylab = NULL, main = NULL,
out.file.directory = NULL, out.file.name = NULL, copyright = FALSE, ...)
30 plot.wux.aov
Arguments
x Object of class wux.aov obtained from the ANOVA aovWux.
ss.relative Boolean. Indicating if the relative contribution of the factors to the overall vari-
ance should be calculated. Default is TRUE.
subreg.subset Vector of subregions to be plotted (e.g. c("EU.ENS", "GAR")).
cex.names Expansion factor for numeric axis labels in bxp. Default is 1.2.
cex.lab Expansion factor for axis names (bar labels) in bxp. Default is 1.2.
legend.text String vector of the factors (e.g. c("GCM", "RCM", "RES")).
sd.text Boolean. Indicating if the overall standard deviation should be displayed. De-
fault is TRUE.
sd.unit Character string of the standard deviation unit with default "" (e.g. "K").
ylim Range vector for the y-axis.
ylab Label for y-axis.
main Main title.
out.file.directory
String of the directory where the plots are exported (e.g. "/tmp/plots/"). If
neither out.file.name nor out.file.directory are passed, the plot will be
displayed on screen.
out.file.name Prefix of the file names of the plots. Files will be stored as out.file.name_subreg_season.eps,
where subreg is one realization of the subreg.subset argument and season is
one realization of season.subset. For example: out.file.name = "Barplot"
will store to the files to Barplot_EUROPE_DJF.eps and Barplot_EUROPE_JJA.eps.
If neither out.file.name nor out.file.directory are passed, the plot will be
displyed on screen.
copyright Boolean. If a copyright message should be plotted. Default is FALSE.
... Further optional arguments passed to barplot.
Author(s)
Georg Heinrich <g.heinrich@uni-graz.at>
Examples
## load WUX and read WUX test data
require(wux)
data(ensembles)
## calculate ANOVA
anova.list <- aovWux(perc.delta.precipitation_amount ~ acronym +
gcm, reconstructLES.df)
## End(Not run)
Description
plot.wux.df plots one or more scatterplots containing climate change signals of selected meteoro-
logical parameters.
This plotting routine extracts all the information from the input data frame which has to be ’WUX-
style’ (see models2wux).
Usage
## S3 method for class 'wux.df'
plot(x,
var1.name = "delta.air_temperature",
var2.name = "perc.delta.precipitation_amount",
subreg.subset = NULL,
season.subset = NULL, boxplots = TRUE,
label.only.these.models = NULL, highlight.models = NULL,
no.text = FALSE,
vert.box.col = "cyan", horiz.box.col = "coral",
zero.line.col = "gray80", median.line.col = "black",
draw.legend = TRUE, draw.seperate.legend = FALSE,
draw.median.lines = TRUE, use.rainbow.colors = TRUE,
xlim = NULL, ylim = NULL, xlab = NULL, ylab = NULL,
main = NULL, out.file.directory = NULL,
out.file.name = NULL, copyright = FALSE, ...)
Arguments
x WUX data.frame (class wux.df) obtained from models2wux’.
var1.name Character string of 1st parameter in WUX dataset. Default is temperature change.
var2.name Character string of 2nd parameter in WUX dataset. Default is precipitation
change.
32 plot.wux.df
Author(s)
Thomas Mendlik <thomas.mendlik@uni-graz.at> and Georg Heinrich <g.heinrich@uni-graz.at>
Examples
require(wux)
## End(Not run)
### now see where ENSMEBLES GCMs lie within CMIP3 ensemble
data(ensembles_gcms) # GCMs for forcing of ENSEMBLES RCMs
data(cmip3_2050) # GCMs of CMIP3 ensemble
## Scatterplot
prec.range <- range(gcms.combined$perc.delta.precipitation_amount) + c(-1, 1)
tas.range <- range(gcms.combined$delta.air_temperature)
## Not run: plot(gcms.combined,
"perc.delta.precipitation_amount", "delta.air_temperature",
subreg.subset = "EU.ENS", draw.median.lines = FALSE,
label.only.these.models = ensembles.gcm.names,
xlim = prec.range,
ylim = tas.range,
main = "GCMs from ENSEMBLES project within CMIP3 SRESA1B ensemble",
draw.seperate.legend = TRUE)
## End(Not run)
34 plotAnnualCycle
Description
plotAnnualCycle plots the monthly or seasonal annual cycle of indicated models and the box-
whisker plots of the underlying distribution.
This plotting routine extracts all the information from the input data frame which has to be ’WUX-
style’ (see models2wux).
Usage
plotAnnualCycle(datain.df, var.name = NULL, subreg.subset = NULL,
season.subset = NULL, plot.quantiles = NULL, quantile.method = 7,
mark.df = NULL, plot.legend = FALSE, cex.names = 1.2, cex.lab = 1.2,
ylab = NULL, main = NULL, out.file.directory = NULL, out.file.name =
NULL, copyright = FALSE, ...)
Arguments
datain.df WUX data frame obtained from models2wux.
var.name Character string of parameter in WUX dataset.
subreg.subset Vector of subregions to be plotted (e.g. c("EU.ENS", "GAR")).
season.subset Vector of seasons to be plotted (e.g. c("MAM", "DJF")).
plot.quantiles 5 element vector indictaing the quantiles to be plotted (e.g. c(0.02,0.25,0.5,0.75,0.98)).
quantile.method
An integer between 1 and 9 selecting one of the nine quantile types in quantiles
with default 7.
mark.df Subset of WUX data frame indicating the models to be marked.
plot.legend Boolean. Indicating if a plot legend indicating the models of mark.df and sam-
ple size should be plotted. Default is FALSE.
cex.names Expansion factor for numeric axis labels in bxp. Default is 1.2.
cex.lab Expansion factor for axis names (bar labels) in bxp. Default is 1.2.
ylab Label for y-axis.
main Main title.
out.file.directory
String of the directory where the plots are exported (e.g. "/tmp/plots/").
out.file.name Prefix of the file names of the plots. Files will be stored as out.file.name_subreg_season.eps,
where subreg is one realization of the subreg.subset argument and season is
one realization of season.subset. For example: out.file.name = "AnnualCycle"
will store to the files to AnnualCycle_EUROPE_DJF.eps and AnnualCycle_EUROPE_JJA.eps.
copyright Boolean. If a copyright message should be plotted. Default is FALSE.
... Further optional arguments passed to bxp.
read.wux.table 35
Author(s)
Georg Heinrich <g.heinrich@uni-graz.at>
Examples
## load WUX and read WUX test data
require(wux)
data(ensembles)
## End(Not run)
Description
Reads in wux csv file obtained from models2wux from harddisk and creates a wux.df object (data
frame) from it.
Usage
read.wux.table(file, ...)
Arguments
file the name of the file which the data are to be read from.
... Further arguments to be passed to read.table.
Value
A wux.df data.frame object.
Author(s)
Thomas Mendlik <thomas.mendlik@uni-graz.at>
36 reconstruct
Examples
## read WUX test data
## Not run: wux.data.frame <- read.wux.table("~/dir/to/data/ensembles_diff.csv")
Description
Performs a simple missing value reconstruction based on an ANOVA with two factors using differ-
ent methods.
Usage
reconstruct(x, factor1.name, factor2.name,
data.name, method = "LES", iterations.num = 100)
Arguments
x WUX data frame of class "wux.df" obtained from models2wux
factor1.name Name of the 1st factor.
factor2.name Name of the 2nd factor.
data.name Name of the variable to be reconstructed.
method One of the currently implemented methods: "LES", "Iterative" or "IterativeCC".
See details section.
iterations.num Number of iterations to be performed. Used only for method "Iterative" or "It-
erativeCC".
Details
Tools for filling missing values of an unbalanced climate model simulation matrix (e.g. missing
RCM-GCM combinations of ENSEMBLES) in order to avoid biased ensemble estimates. Follow-
ing methods are currently implemented:
method = "LES" (default): Performs a simple missing value reconstruction with two factors
based on solving the linear equation system (LES) of the ANOVA. The algorithm follows Déqué
et al. (2007) but the reconstruction is based on solving the linear equation system (LES) of the
ANOVA instead of reconstructing iteratively. The main advantages of this method are that it is
much faster and can be more easily extended to more factors than the original one. However,
keep in mind that the results slightly differ from the iterative procedure proposed by Déqué et al.
(2007). The reconstruction algorithm is based on unique factor combinations (i.e. one element
per combination of factor1.name and factor2.name).
method = "Iterative": The data reconstruction follows the iterative procedure based on the
ANOVA proposed by Déqué et al. (2007). The reconstruction algorithm is based on unique factor
combinations (i.e. one element per combination of factor1.name and factor2.name).
reconstruct 37
method = "IterativeCC": Performs a leave one out cross calculation (CC) of the ANOVA
based missing value reconstruction with two factors based on and following the iterative procedure
of method = "Iterative".
Value
Returns a WUX data frame containing the reconstructed data of class c("rwux.df", "wux.df", "data.frame").
Author(s)
Georg Heinrich <g.heinrich@uni-graz.at> and Thomas Mendlik <thomas.mendlik@uni-graz.at>
References
Déqué M, Rowell DP, Lüthi D, Giorgi F, Christensen JH, Rockel B, Jacob D, Kjellström E, de
Castro M, van den Hurk B. 2007. An intercomparison of regional climate simulations for Europe:
Assessing uncertainties in model projections. Climatic Change 81: 53–70. DOI:10.1007/s10584-
006-9228-x.
Examples
## load WUX and read WUX test data
require(wux)
data(ensembles)
Description
Prints a screen summary of a WUX data.frame (class wux.df).
Usage
## S3 method for class 'wux.df'
summary(object, parms = c("perc.delta.precipitation_amount",
"delta.air_temperature"), average.over.gcm.runs = FALSE, ...)
Arguments
object WUX data.frame (wux.df object) obtained from models2wux
parms String vector specifying the parameters to be evaluated. Default is perc.delta.precipitation_amount
(percentage of precipitation change) and delta.air_temperature (air temper-
ature change in K).
average.over.gcm.runs
Boolean. Should the runs of the same GCM be averaged out? This is recom-
mended, as same GCMs tend to behave very similarly when run with different
initial conditions and would thus lead to biased statistics when regarding as in-
dependent. Only available for GCM analysis.
... Further optional arguments. Not active now.
Details
summary.wux.df gives an overview of model frequenzy and calculates statistics for each meteoro-
logical parameter within each season in each subregion for all emission scenarios.
print.summaryWuxdf prints the result to the screen.
Value
Returns a summaryWuxdf object, which is a list, but will be printed in a special way. The list has
two elements, namely overall.stats and parms.stats. Both are lists again. overall.stats
stores all categorical statistics (climate model counts, emmission scenarios, rcm-gcm crosstables,
...). parms.stats is a list with statistics of continuous climate change signals (mean, standard
deviation, coeficent of variation and quantiles) split by season, emission scenario, meteorological
parameters and subregions.
Author(s)
Thomas Mendlik <thomas.mendlik@uni-graz.at>
userinput_CMIP5_changesignal 39
Examples
## ENSEMBLES data summary
data(ensembles)
summary(ensembles)
userinput_CMIP5_changesignal
Example userinput for models2wux
Description
This example userinput_CMIP5_changesignal can be used to test the models2wux functionality.
A userinput is a list of configurations used to read and process climate model data. In general, you
should store it as an own file somewhere on your system. It calculates the climate change signal of
1971-2000 and 2071-2100 for temperature over the Alpine region of 2 CMIP5 models "NorESM1-
M" and "CanESM2". It aggregates the monthly NetCDF model output to boreal seasons, winter,
spirng, summer and autumn. It also stores the output as a csv-file in your "/tmp" directory.
Usage
data(userinput_CMIP5_changesignal)
Details
See "Configfile userinput" section in models2wux.
See Also
models2wux, userinput_CMIP5_timeseries
Examples
## thats what userinput_CMIP5_changesignal looks like:
## it contains a single list named user.input
## describing 2 CMIP5 models in the alpine region
data("userinput_CMIP5_changesignal")
is.list(userinput_CMIP5_changesignal)
str(userinput_CMIP5_changesignal)
40 userinput_CMIP5_timeseries
data(modelinput_test)
## the result is what the data.set would look like, if you ran the code
## above:
data(CMIP5_example_changesignal)
wux.test <- CMIP5_example_changesignal
wux.test
## example summary though the statistics not make much sense with 2 models
summary(wux.test, parms = "delta.air_temperature")
userinput_CMIP5_timeseries
Example userinput for models2wux
Description
This example userinput_CMIP5_changesignal can be used to test the models2wux functionality.
A userinput is a list of configurations used to read and process climate model data. In general, you
should store it as an own file somewhere on your system. It calculates a time series of the historical
run 1971-2005 and RCP 8.5 2006-2100 for temperature over the Alpine region of 2 CMIP5 models
"MIROC5" and "CanESM2". It aggregates the monthly NetCDF model output to boreal seasons,
winter, spirng, summer and autumn. It also stores the output as a csv-file in your "/tmp" directory.
Usage
data(userinput_CMIP5_timeseries)
Details
See "Configfile userinput" section in models2wux.
See Also
models2wux, userinput_CMIP5_changesignal
userinput_CMIP5_timeseries 41
Examples
## thats what userinput_CMIP5_timeseries looks like:
## it contains a single list named user.input
## describing 2 CMIP5 models in the alpine region
data("userinput_CMIP5_timeseries")
is.list(userinput_CMIP5_timeseries)
str(userinput_CMIP5_timeseries)
data(modelinput_test)
## the result is what the data.set would look like, if you ran the code
## above:
data(CMIP5_example_timeseries)
wux.test <- CMIP5_example_timeseries
## End(Not run)
Index
∗Topic IO CMIP5fromESGF, 8
AverageWuxDataFrame, 6 CMIP5toModelinput, 10
CMIP5fromESGF, 8 models2wux, 21
CMIP5toModelinput, 10 read.wux.table, 35
models2wux, 21 ∗Topic hplot
read.wux.table, 35 hist, 18
∗Topic NA plot.wux.aov, 29
aovWux, 5 plot.wux.df, 31
reconstruct, 36 plotAnnualCycle, 34
∗Topic classes ∗Topic interface
aovWux, 5 CMIP5fromESGF, 8
reconstruct, 36 CMIP5toModelinput, 10
∗Topic connection ∗Topic iteration
CMIP5fromESGF, 8 AverageWuxDataFrame, 6
CMIP5toModelinput, 10 reconstruct, 36
∗Topic database ∗Topic manip
CMIP5fromESGF, 8 AverageWuxDataFrame, 6
CMIP5toModelinput, 10 summary, 38
∗Topic datagen ∗Topic methods
aovWux, 5 summary, 38
AverageWuxDataFrame, 6 ∗Topic models
models2wux, 21 aovWux, 5
reconstruct, 36 plot.wux.aov, 29
∗Topic datasets reconstruct, 36
alpinesummer, 4 ∗Topic multivariate
cmip3_2050, 6 models2wux, 21
cmip3_2100, 7 plot.wux.df, 31
cmip5_2050, 11 ∗Topic package
cmip5_2100, 12 wux-package, 2
CMIP5_example_changesignal, 13 ∗Topic print
CMIP5_example_timeseries, 14 summary, 38
ensembles, 15 ∗Topic programming
ensembles_gcms, 16 CMIP5fromESGF, 8
modelinput_test, 20 CMIP5toModelinput, 10
userinput_CMIP5_changesignal, 39 ∗Topic regression
userinput_CMIP5_timeseries, 40 aovWux, 5
∗Topic distribution plot.wux.aov, 29
hist, 18 reconstruct, 36
∗Topic file ∗Topic spatial
42
INDEX 43
models2wux, 21
∗Topic ts
models2wux, 21
∗Topic univar
AverageWuxDataFrame, 6
hist, 18
plotAnnualCycle, 34
summary, 38
alpinesummer, 3, 4
aov, 5
aovWux, 3, 5, 29, 30
AverageWuxDataFrame, 3, 6
cmip3_2050, 3, 6, 17
cmip3_2100, 3, 7
cmip5_2050, 3, 11, 27
cmip5_2100, 3, 12, 27
CMIP5_example_changesignal, 3, 13
CMIP5_example_timeseries, 3, 14
CMIP5fromESGF, 3, 8, 14, 15, 20
CMIP5toModelinput, 10
hist, 18
hist.wux.df, 3
modelinput_test, 3, 20, 27
models2wux, 3–6, 14, 15, 17, 18, 20, 21, 31,
34–36, 38–40
plot.wux.aov, 3, 29
plot.wux.df, 3, 31
plotAnnualCycle, 3, 34
read.table, 35
read.wux.table, 3, 6, 35
reconstruct, 3, 36
summary, 38
summary.wux.df, 3
wux (wux-package), 2
wux-package, 2