Chapter 7 Scripting
7.1 Introduction
So far you have only seen R code used in the console, in code chunks of an RMarkdown document, or maybe in an R script in the form of a scratchpad. The code you have seen consisted of (series of) R statements with one or more function calls.
There has been no conditional code, no repeated operations and no extraction of blocks of code into something reusable, a custom function. In short, you have not written any program or script yet.
This chapter deals with that. It introduces conditional execution and custom functions.
7.2 Flow control
Flow control constitutes a series of code elements used to control whether some code blocks are executed or not, and how many times
These programming concepts and structures are used for flow control:
- Conditional execution:
if(){} else if(){} else{}
- Repeated execution:
for() {}
- Repeated conditional execution:
while(){}
For those of you with experience in other programming languages: there is no switch expression. There is a switch()
function however, but it is not dealt with in this eBook.
7.2.1 Conditional execution with if/else
There are several applications for conditionals, with differing language constructs:
- the
if(COND) {<TRUE>} else {<FALSE>}
code block for controlling program flow - the
if (COND) <TRUE> else <FALSE>
expression as a shorthand for the code block - the
ifelse(COND, <TRUE>, <FALSE>)
function for use on dataframes
As you can see there is always a condition to be tested. This expression should return a logical value: TRUE or FALSE.
All three are discussed in the following slides.
The if() {} else {}
code block
The if(COND) {<TRUE>} else {<FALSE>}
code block knows several required and several optional elements.
At the minimum there is an if(COND) {}
element where COND
is an expression evaluating to a Logical.
## [1] "Adult"
if()
shorthand
If there is only one statement within a block you can omit the curly braces:
## [1] "Adult"
Remember that the semicolon at the end of a statement is optional in R and is usually omitted.
if()
can have an else {}
When there is an alternative course of action when the test evaluates to FALSE
you use the else{}
element of this structure.
## [1] "Adult"
Here the curly braces are required:
## Error: <text>:3:1: unexpected 'else'
## 2: if (age >= 18) print("Adult")
## 3: else
## ^
The if()
can have else if()
blocks
If there are more than two courses of action, you must reside to else if()
blocks.
Each of them should have its own CONDition to test on.
age <- 43
if (age < 18) {
print("Minor")
} else if (age >= 65){
print("Senior")
} else if(age >= 18 && age <= 30){
print("Young Adult")
} else {
print("Adult")
}
## [1] "Adult"
if/else real life example
This code chunk checks if a file exists and only downloads it if it is not present
ifelse shorthand
There is also a shorthand for if(){} else{}
. It is also called a ternary.
It has the form
if (COND) <EXPRESSION_FOR_TRUE> else <EXPRESSION_FOR_FALSE>
## [1] "UNEVEN"
if/else on dataframes: ifelse()
When you want to assign values to a vector based on some condition, you need to use the third form, the ifelse()
function.
When you use the regular if/else structures on dataframes you don’t get what you want:
# Only first value (row) is evaluated and this value is cycled
# The whole column gets value 1
airquality$foo <- if (airquality$Ozone < 30) 0 else 1
## Warning in if (airquality$Ozone < 30) 0 else 1: the condition has length > 1 and
## only the first element will be used
## Ozone Solar.R Wind Temp Month Day foo bar
## 1 41 190 7.4 67 May 1 1 1
## 2 36 118 8.0 72 May 2 1 1
## 3 12 149 12.6 74 May 3 1 0
## 4 18 313 11.5 62 May 4 1 0
## 5 NA NA 14.3 56 May 5 1 NA
## 6 28 NA 14.9 66 May 6 1 0
7.2.2 Iteration with for(){}
- Iteration with
for
is used for looping a series of values from a vector. _ You should not use it to iterate columns or rows of a dataframe: the preferred way to do that is withapply()
and its relatives (next presentation)
## [1] "Hello"
## [1] "'Allo"
## [1] "Moi"
Sometimes you need a counter or index when iterating:
greetings <- c("Hello", "'Allo", "Moi")
for (i in 1 : length(greetings)) {
print(paste(i, greetings[i]))
}
## [1] "1 Hello"
## [1] "2 'Allo"
## [1] "3 Moi"
7.2.3 Conditional iteration with while(){}
This is the last flow control structure. It is used to execute a block as long as a certain condition is met. They are not used very much in R.
## [1] 1
## [1] 2
## [1] 3
## [1] 4
7.3 Creating functions
Here is the definition again.
A function is a piece of functionality that you can execute by typing its name, followed by a pair of parentheses. Within these parentheses, you can pass data for the function to work on. Functions often, but not always, return a value.
Thus, functions are named blocks of code with a single well-defined purpose which make them reusable.
You have already used many predefined or build in functions of R: str
, max
, read.table
etc. If you type the name of a function without parenthesis you get its definition.
## function (..., na.rm = FALSE) .Primitive("sum")
Anatomy of a function
A function
- usually, but not always, has a name. in the next chapter you will see examples of anonymous functions that are defined in the location where they are needed.
- has a parameter list (sometimes of size zero) between parentheses. These parameters constitute the required input variables on which the function will operate.
- has a method body. This is a block of one or more lines of code in which the actual work is performed.
- may have a return value. Ther result of a function is usually, but not always returned. The print function, for instance, does not return a value but only outputs to the console. Functions can only retun one single value (vector). If more return values are needed, you need to wrap them in a complex datatype such as a list.
- is defined using the _function keyword_
Here is a function prototype. It shows all characteristics of the above list of properties.
method_name <- function(arg, arg, ...) {
<function body>
return(return_value)
}
A first function
Here is a simple function determining whether some number is even
## [1] FALSE TRUE FALSE TRUE FALSE
Note that return()
is a method call which is very unlike other programming languages.
The return statement is optional. In R, the last statement of a method body is its implicit return value. Therefore, the previous example is equivalent to this:
## [1] FALSE TRUE FALSE TRUE FALSE
Being explicit is always allowed when implicit return is possible, but using a return()
for forcing return values at other points is required:
my_message <- function(age) {
if (age < 18) return("have a lemonade!") # explicit return
"have a beer!" # implicit return statement
}
my_message(20)
## [1] "have a beer!"
Default argument values
It is possible to specify default values for function arguments. This is a value that is attached to a function parameter when the calling code does not provide one. A default value is specified in the parameter list, using this construct: some_arg = <default-value>
. Almost all functions in R have (many) parameters with default values.
You should use default values yourself for function parameters whenever possible. They make using the function so much easier. The following function calculates the exponent (power) of a number. When no power =
value is provided, it defaults to two.
## [1] 1000
## [1] 100
Argument order when calling a function
As we have seen many times before, you do not need to pass arguments by name. In the above example, the names were not used. When you do not use the names of arguments, the order in which you pass them is important; they must match the order in which they are declared in the function. If you use their names, their order is not important:
## [1] 16
To summarize: When calling a function,
- the parameters without default value are mandatory
- the unnamed arguments should come first and should be passed in the order in which they are declared
- passing named arguments may be done in any order
7.3.1 Errors and warnings
When someting is not right, but not enought to quit execution, use a warning to let the user (or yourself) know that there is something wrong:
warning("I am not happy")
When something is terribly wrong, and you cannot continue, you should stop execution with an error message:
stop("I can't go on")
Here is a small errors demo:
demo_inverse <- function(x) {
if (!is.numeric(x)) {
stop("non-numeric vector")
}
return(x / 3)
}
result1 <- demo_inverse(c("a", "b")) #result1 not created!
## Error in demo_inverse(c("a", "b")): non-numeric vector
7.4 Scripting
An R script is a text file with the extension .R
that contains R code. When it is loaded, it is immediately evaluated. Functions are loaded/evaluated, but not executed. Declared variables are stored in main memory - the Global Environment to be precise.
Here is the contents of a very simple R script called source_demo.R
x <- 42
x # echo to console
print(paste0("x = ", x)) #explicit print
# function defined but not called
demo_function <- function(message) {
print(paste("you said", message))
}
You can load this script int your R session by sourcing it; just call source(path/to/source_demo.R)
. Alternatively, when you have it open in the RStudio editor, you can click the “source” button at the top right of the editor panel. After that, you can use the functions and variables defined within the script:
## [1] "x = 42"
## [1] 42
## [1] "you said hi!"
Why scripts?
- To store pieces of functionality you want to reuse (e.g. in different RMarkdown documents)
- To store entire workflows outside RMarkdown
- To run R code from the commandline (terminal)
- To call from other scripts and build applications or packages