CPP 527: Foundations of Data Science II



Lab 02 is an extension of the Monty Hall Problem that was implemented in Lab 01.

In this lab you will be practicing loops constructors, and collectors.

Last week you worked to build five distinct functions, one for each step of the game:

  1. Game set-up
  2. Contestant selects first door
  3. Host opens a goat door
  4. Contestant decides to stay or switch doors
  5. Host reveals prize to determine if they won

We now have all of the pieces that we need to start analyzing our problem. Which strategy is best in this scenario? Should we stay with our first selection? Or should we switch doors when given the option?

We can answer some of these hard analytical questions either (1) with an explicit closed-form mathematical solution (i.e. a proof), or (2) using simulation to examine the effectiveness of both strategies by playing the game over and over and looking at which strategy yields higher returns.

Simulation Set-Up

Using the functions you created last week or those provided in the solutions, package them all together into a single play_game() function which executes each step of a single game in order.

Once we have this implemented, we are ready to ready to run the simulation.

Adding the Game to a Loop

When running simulations for inferential purposes the general rule of thumb is they should run at least 10,000 times in order for the simulated statistics to converge close to the actual theoretial value (average proportion of wins achieved by each strategy in this case).

Recall that our loop has three parts you will need to define:

##         outcome
## strategy LOSE  WIN
##   stay   6737 3263
##   switch 3263 6737

Or to make it a bit easier to interpret, what are the proportion of each outcome? Divide by the total number of games:

##         outcome
## strategy LOSE  WIN
##   stay   0.67 0.33
##   switch 0.33 0.67

Or use the table proportions function prop.table(). The default is to report each cell as a proportion of the total, margin=1 returns row proportions (the total is the sum of all values across a row) and margin=2 returns a column proportion.

##         outcome
## strategy LOSE  WIN
##   stay   0.67 0.33
##   switch 0.33 0.67

Note that each game played produces a data frame with two rows and two columns:

We use the collector data frame results.df to gather all of the results together. We do this by appending each new data frame on the end of the old data frame inside the loop:

Note on Append Functions

During simulations we play the game a bunch of times and save the results in the object called results.df:

Note that c() is used to append items on the end of a a vector:

## [1] 1 2 3 4 9

And rbind() is the equivalent for stacking new rows onto the bottom of an existing data frame:

If we would try to append new rows onto a data frame with c() we would break our object type and end up with a mess:

## $strategy
## [1] "stay"   "switch"
## 
## $outcome
## [1] "WIN"  "LOSE"
## 
## $strategy
## [1] "stay"   "switch"
## 
## $outcome
## [1] "WIN"  "LOSE"

So it’s important to use the proper appending functions when you are building objects inside of loops.

The other thing to note is you need to create or “declare” your collector object before you can use it inside of the append function. We do this using a NULL assignment. If we skip this step we will get an error during the rbind() call.

Lab 02 Questions

So far we have shown how to create a wrapper function that makes it easier to control and repeat the steps of the game in your simulation:

And how to use that function inside of a loop to quickly generate a bunch of data:

##         outcome
## strategy LOSE  WIN
##   stay   6585 3415
##   switch 3415 6585

We can then quickly determine the optimal outcome:

##         outcome
## strategy LOSE  WIN
##   stay   0.66 0.34
##   switch 0.34 0.66

Last week there were two challenge questions that inquired about how the code could be modified slightly to allow for more flexible games. Use these games to answer the following questions:

Part I

The first challenge question required you build a game with 5 doors: 3 goats and 2 cars. The rest of the game is the same except instead of opening a single goat door after the contestant makes their initial selection, the host now opens a goat door AND a car door.

In this new game set-up, is SWITCH still the dominant strategy for contestants?

Using the solutions provided for Lab 01 (or your own functions if you were able to successfully implement it) wrap the game steps into a single play_game() function. Similar to the example above, return a data frame that contains results from one game.

Use a loop to build a simulation that plays the game 10,000 times. Create a table to report the results.

Q1: Is SWITCH still the dominant strategy? Support your answer with your data.

Part II

The second challenge question asks that you create a game that allows the user to specify (1) how many goats and (2) how many cars are included in the game, also determining the number of doors the contestants can choose from. The host only opens one goat door, similar to the original game.

Using solutions for the second challenge problem on Lab-01, create a wrapper play_game() function and build a simulation loop the same as the last problem.

Create three separate simulations, each with 10 doors total but analyzing three different scenarios.

  • 1 car, 9 goats
  • 2 cars, 8 goats
  • 3 cars, 7 goats

Use your results to answer the following questions:

Q1: Is SWITCH still the dominant strategy? Report your chances of winning for each strategy for each scenario.

Q2: How much better off are you switching in the original game? How much did it improve your chances of winning?

  • \(Pr( win | switch ) - Pr( win | stay )\)

Q3: How much better off are you switching in each of the three scenario with 10 doors and 1 to 3 cars?


Challenge Question

Can you create a version of the first game above that not only returns the results, but all of the game metadata as well? It would need to return all of the following as part of a data frame:

  • game set-up ( use paste0( game, collapse=" " ) to turn it into a single character
  • initial contestant selection
  • opened door
  • final selection
  • strategy
  • game outcome




Submission Instructions

When you have completed your assignment, knit your RMD file to generate your rendered HTML file. Platforms like BlackBoard and Canvas often disallow you from submitting HTML files when there is embedded computer code, so create a zipped folder with both the RMD and HTML files.

Login to Canvas at http://canvas.asu.edu and navigate to the assignments tab in the course repository. Upload your zipped folder to the appropriate lab submission link.

Remember to:





Some Notes on Constructors

The term constructors refers to the act of creating a new object. We have typically used assignment to do this:

There are many cases, however, where we might need to create an ** empty object** that we plan to use to store data. This is common step during simulation.

There are several ways we can do this:

## NULL
## [1] "" "" "" "" ""
## [1] 0 0 0 0 0

Since we are comparing strategies we want to examine outcomes for each strategy each time we play the game and save the results as outcome.stay and outcome.switch.

Recall that functions in R can only return one object (or in some cases NULL).

Since we have two outcomes of interest here, we need to bind them together in order to return them from the function.

Here we have a bit of a connundrum. We need to decide how to efficiently bundle our results. We have a few options.

We could simply bind the results together with the combine c() function and append them to the end of a collector vector.

## [1] "LOSE" "WIN"

The problem is that now when we put the game function into a loop we have no idea how to interpret the results because we do not know which game they belong to.

##  [1] "WIN"  "WIN"  "LOSE" "WIN"  "LOSE" "WIN"  "WIN"  "WIN"  "LOSE" "WIN" 
## [11] "WIN"  "LOSE" "WIN"  "WIN"  "WIN"  "LOSE" "LOSE" "WIN"  "WIN"  "LOSE"

We can utilize vector attributes to assign each game outcome a label:

##   stay switch   stay switch   stay switch   stay switch   stay switch 
## "LOSE" "LOSE" "LOSE"  "WIN"  "WIN" "LOSE" "LOSE" "LOSE" "LOSE" "LOSE"

This is a big improvement because now we won’t mix up which result belong to which strategy.

The only problem is that we can’t access the strategy during the analysis.

## results
## LOSE  WIN 
##    8    2
##   stay switch   stay switch   stay switch   stay switch   stay switch 
##  FALSE  FALSE  FALSE  FALSE  FALSE  FALSE  FALSE  FALSE  FALSE  FALSE

We would have to use the names() function to extract the attribute and store it as a new vector.

##         results
## strategy LOSE WIN
##   stay      4   1
##   switch    4   1

Not horrible, but it makes our life a little harder. What if we organized them as a data frame instead of a vector?

We now have a one-row data frame:

And we can bind our results using the row bind function rbind().

We can now analyze each column fairly easily:

## [1] 0.2
## [1] 0.6

But we still can’t reference the strategy directly as it’s own variable. If we follow tidy data principles each attribute should be stored as it’s own column so it is easy to incorporate into analysis. They tidy version would look like this:

##         
##          LOSE WIN
##   stay      3   2
##   switch    2   3

This tidy format will make our analytical steps more efficient, so when possible default to that format.

Efficient Collectors

The examples above used append operators like rbind() to build the results data frame inside of a loop:

This is a quick and easy way to create a collector, but it turns out to also be a super inefficient implementation. The problem is that each time you add another element onto a vector or another row onto a data frame, you have changed the size of the object, which often forces the computer to create a new object in memory, then delete the old one. It can make the process slow, and also crash your RAM.

It is typically best practice to create an empty collector object that is the right size, then fill each slot with the appropriate data.

This works well when we are doing things like bootstrapping standard errors in statistics since each time through the loop we are creating a single parameter that can be stored in a vector.

If we repeat the operation 10,000 times, our collector vector will have length 10,000.

Unforunately we can’t create an empty data frame simply by declaring its size. But we have a couple of options.

We can build it with empty values or NAs:

And we can replace existing rows with new ones:

The other option is to use a list, which is a more flexible data type. We can store a bunch of rows inside a list, and then easily convert it to a data frame when we are ready. Note that assignment to lists occurs with double brackets:

## [[1]]
##   strategies game.outcomes
## 1       stay          LOSE
## 2     switch           WIN
## 
## [[2]]
##   strategies game.outcomes
## 1       stay           WIN
## 2     switch          LOSE
## 
## [[3]]
##   strategies game.outcomes
## 1       stay           WIN
## 2     switch          LOSE
## 
## [[4]]
##   strategies game.outcomes
## 1       stay          LOSE
## 2     switch           WIN
## 
## [[5]]
##   strategies game.outcomes
## 1       stay          LOSE
## 2     switch           WIN

Convert to a data frame with dplyr::bind_rows()

Even if we do not pre-declare the size of the vector it will still scale well using this approach.




Notes on Knitting

Note that when you knit a file, it starts from a blank slate. You might have packages loaded or datasets active on your local machine, so you can run code chunks fine. But when you knit you might get errors that functions cannot be located or datasets don’t exist. Be sure that you have included chunks to load these in your RMD file.

Your RMD file will not knit if you have errors in your code. If you get stuck on a question, just add eval=F to the code chunk and it will be ignored when you knit your file. That way I can give you credit for attempting the question and provide guidance on fixing the problem.

Markdown Trouble?

If you are having problems with your RMD file, visit the RMD File Styles and Knitting Tips manual.






ds4ps

Data Science for
Public Service