Introduction to the Course; Basics of Data ======================================================== author: 36-350 date: 25 August 2014 font-family: Garamond Agenda ======================================================== - Course overview and mechanics - Built-in data types - Built-in functions and operators - First data structures: Vectors and arrays Why good statisticians learn to program ======================================================== - _Independence_: Otherwise, you rely on someone else having given you exactly the right tool - *Honesty*: Otherwise, you end up distorting your problem to match the tools you have - *Clarity*: Making your method something a machine can do disciplines your thinking and makes it public; that's science How this class will work ======================================================== - No programming knowledge presumed - Some stats. knowledge presumed - General programming mixed with data-manipulation and statistical inference - Class will be _very_ cumulative - Keep up with the readings and assignments! Mechanics ======================================================== - Two lectures a week: concepts, methods, examples - Lab to try stuff out and get fast feedback (10%) - HW weekly to do longer and more complex things (30%) - Mid-term project (2 weeks) (20%) - Final group project (1 month) (40%) ======================================================== Assignments, office hours, class notes, grading policies, useful links on R: http://www.stat.cmu.edu/~cshalizi/statcomp/14 Blackboard for a grade-book and for turning in homework _only_, check the class website for everything else The class in a nutshell: Functional programming ======================================================== 2 sorts of things (**objects**): **data** and **functions** - **Data**: things like 7, "seven", $7.000$, the matrix $\left[ \begin{array}{ccc} 7 & 7 & 7 \\ 7 & 7 & 7\end{array}\right]$ - **Functions**: things like $\log{}$, $+$ (two arguments), $<$ (two), $\mod{}$ (two), mean (one) > A function is a machine which turns input objects (**arguments**) into an output object (**return value**), possibly with **side effects**, according to a definite rule ========== Programming is writing functions to transform inputs into outputs Good programming ensures the transformation is done easily and correctly Machines are made out of machines; functions are made out of functions, like $f(a,b) = a^2 + b^2$ >The route to good programming is to take the big transformation and break it down into smaller ones, and then break those down, until you come to tasks which the built-in functions can do Before functions, data ==== Different kinds of data object All data is represented in binary format, by **bits** (TRUE/FALSE, YES/NO, 1/0) - **Booleans** Direct binary values: TRUE or FALSE in R - **Integers**: whole numbers (positive, negative or zero), represented by a fixed-length block of bits - **Characters** fixed-length blocks of bits, with special coding; **strings** = sequences of characters - **Floating point numbers**: a fraction (with a finite number of bits) times an exponent, like $1.87 \times {10}^{6}$, but in binary form - **Missing or ill-defined values**: NA, NaN, etc. Operators ==== - **Unary** - for arithmetic negation, ! for Boolean - **Binary** usual arithmetic operators, plus ones for modulo and integer division; take two numbers and give a number === {r} 7+5 7-5 7*5 7^5  ==== {r} 7/5 7 %% 5 7 %/% 5  The R Console ==== Basic interaction with R is by typing in the **console**, a.k.a. **terminal** or **command-line** You type in commands, R gives back answers (or errors) Menus and other graphical interfaces are extras built on top of the console Operators cont'd. === **Comparisons** are also binary operators; they take two objects, like numbers, and give a Boolean {r} 7 > 5 7 < 5 7 >= 7 7 <= 5  === {r} 7 == 5 7 != 5  Boolean operators === Basically "and" and "or": {r} (5 > 7) & (6*7 == 42) (5 > 7) | (6*7 == 42)  (will see special doubled forms, && and ||, later) More types === typeof() function returns the type is._foo_() functions return Booleans for whether the argument is of type _foo_ as._foo_() (tries to) "cast" its argument to type _foo_ --- to translate it sensibly into a _foo_-type value === {r} typeof(7) is.numeric(7) is.na(7) is.na(7/0) is.na(0/0)  Why is 7/0 not NA, but 0/0 is? === {r} is.character(7) is.character("7") is.character("seven") is.na("seven")  === {r} as.character(5/6) as.numeric(as.character(5/6)) 6*as.numeric(as.character(5/6)) 5/6 == as.numeric(as.character(5/6))  (why is that last FALSE?) Data can have names === We can give names to data objects; these give us **variables** A few variables are built in: {r} pi  Variables can be arguments to functions or operators, just like constants: {r} pi*10 cos(pi)  === Most variables are created with the **assignment operator**, <- or = {r} approx.pi <- 22/7 approx.pi diameter.in.cubits = 10 approx.pi*diameter.in.cubits  === The assignment operator also changes values: {r} circumference.in.cubits <- approx.pi*diameter.in.cubits circumference.in.cubits circumference.in.cubits <- 30 circumference.in.cubits  === Using names and variables makes code: easier to design, easier to debug, less prone to bugs, easier to improve, and easier for others to read Avoid "magic constants"; use named variables you will be graded on this! Named variables are a first step towards **abstraction** The workspace === What names have you defined values for? {r} ls() objects()  Getting of variables: {r} rm("circumference.in.cubits") ls()  First data structure: vectors === Group related data values into one object, a **data structure** A **vector** is a sequence of values, all of the same type {r} x <- c(7, 8, 10, 45) x is.vector(x)  c() function returns a vector containing all its arguments in order x[1] is the first element, x[4] is the 4th element x[-4] is a vector containing all but the fourth element === vector(length=6) returns an empty vector of length 6; helpful for filling things up later {r} weekly.hours <- vector(length=5) weekly.hours[5] <- 8  Vector arithmetic === Operators apply to vectors "pairwise" or "elementwise": {r} y <- c(-7, -8, -10, -45) x+y x*y  Recycling === **Recycling** repeat elements in shorter vector when combined with longer {r} x + c(-7,-8) x^c(1,0,-1,0.5)  Single numbers are vectors of length 1 for purposes of recycling: {r} 2*x  === Can also do pairwise comparisons: {r} x > 9  Note: returns Boolean vector Boolean operators work elementwise: {r} (x > 9) & (x < 20)  === To compare whole vectors, best to use identical() or all.equal(): {r} x == -y identical(x,-y) identical(c(0.5-0.3,0.3-0.1),c(0.3-0.1,0.5-0.3)) all.equal(c(0.5-0.3,0.3-0.1),c(0.3-0.1,0.5-0.3))  Functions on vectors === Lots of functions take vectors as arguments: - mean(), median(), sd(), var(), max(), min(), length(), sum(): return single numbers - sort() returns a new vector - hist() takes a vector of numbers and produces a histogram, a highly structured object, with the side-effect of making a plot - Similarly ecdf() produces a cumulative-density-function object - summary() gives a five-number summary of numerical vectors - any() and all() are useful on Boolean vectors Addressing vectors === Vector of indices: {r} x[c(2,4)]  Vector of negative indices {r} x[c(-1,-3)]  (why that, and not 8 10?) === Boolean vector: {r} x[x>9] y[x>9]  which() turns a Boolean vector in vector of TRUE indices: {r} places <- which(x > 9) places y[places]  Named components === You can give names to elements or components of vectors {r} names(x) <- c("v1","v2","v3","fred") names(x) x[c("fred","v1")]  note the labels in what R prints; not actually part of the value === names(x) is just another vector (of characters): {r} names(y) <- names(x) sort(names(x)) which(names(x)=="fred")  Take-Aways === - We write programs by composing functions to manipulate data - The basic data types let us represent Booleans, numbers, and characters - Data structure let us group related values together - Vectors let us group values of the same type - Use variables rather a profusion of magic constants - Name components of structures to make data more meaningful Peculiarites of floating-point numbers === The more bits in the fraction part, the more precision The R floating-point data type is a double, a.k.a. numeric back when memory was expensive, the now-standard number of bits was twice the default Finite precision $\Rightarrow$ arithmetic on doubles $\neq$ arithmetic on $\mathbb{R}$. === {r} 0.45 == 3*0.15 0.45 - 3*0.15  === Often ignorable, but not always - Rounding errors tend to accumulate in long calculations - When results should be $\approx 0$, errors can flip signs - Usually better to use all.equal() than exact comparison {r} (0.5 - 0.3) == (0.3 - 0.1) all.equal(0.5-0.3, 0.3-0.1)  Peculiarities of Integers === Typing a whole number in the terminal doesn't make an integer; it makes a double, whose fractional part is 0 {r} is.integer(7)  This looks like an integer {r} as.integer(7)  To test for being a whole number, use round(): {r} round(7) == 7