In this lab we will focus on sensitivity analysis and Monte Carlo simulations.
Sensitivity analysis is the study of how the uncertainty in the output of a mathematical model or system (numerical or otherwise) can be apportioned to different sources of uncertainty in its inputs. We will use the lpSolveAPI R-package as we did in the previous lab.
Monte Carlo Simulations utilize repeated random sampling from a given universe or population to derive certain results. This type of simulation is known as a probabilistic simulation, as opposed to a deterministic simulation.
An example of a Monte Carlo simulation is the one applied to approximate the value of pi. The simulation is based on generating random points within a unit square and see how many points fall within the circle enclosed by the unit square (marked in red). The higher the number of sampled points the closer the result is to the actual result. After selecting 30,000 random points, the estimate for pi is much closer to the actual value within the four decimal points of precision.
In this lab, we will learn how to generate random samples with various simulations and how to run a sensitivity analysis on the marketing use case covered so far.
Remember to always set your working directory to the source file location. Go to ‘Session’, scroll down to ‘Set Working Directory’, and click ‘To Source File Location’. Read carefully the below and follow the instructions to complete the tasks and answer any questions. Submit your work to RPubs as detailed in previous notes.
For your assignment you may be using different data sets than what is included here. Always read carefully the instructions on Sakai. Tasks/questions to be completed/answered are highlighted in larger bolded fonts and numbered according to their particular placement in the task section.
In order to conduct the sensitivity analysis, we will need to download again the lpSolveAPI package unless you have it already installed in your R environment
# Require will load the package only if not installed
# Dependencies = TRUE makes sure that dependencies are install
if(!require("lpSolveAPI",quietly = TRUE))
install.packages("lpSolveAPI",dependencies = TRUE, repos = "https://cloud.r-project.org")
We will revisit and solve again the marketing case discussed in class (also part of previous lab).
# We start with `0` constraint and `2` decision variables. The object name `lpmark` is discretionary.
lpmark = make.lp(0, 2)
# Define type of optimization as maximum and dump the screen output into a `dummy` variable
dummy = lp.control(lpmark, sense="max")
# Set the objective function coefficients
set.objfn(lpmark, c(275.691, 48.341))
Add all constraints to the model.
add.constraint(lpmark, c(1, 1), "<=", 350000)
add.constraint(lpmark, c(1, 0), ">=", 15000)
add.constraint(lpmark, c(0, 1), ">=", 75000)
add.constraint(lpmark, c(2, -1), "=", 0)
add.constraint(lpmark, c(1, 0), ">=", 0)
add.constraint(lpmark, c(0, 1), ">=", 0)
Now, view the problem setting in tabular/matrix form. This is a good checkpoint to confirm that our contraints have been properly set.
lpmark
## Model name:
## C1 C2
## Maximize 275.691 48.341
## R1 1 1 <= 350000
## R2 1 0 >= 15000
## R3 0 1 >= 75000
## R4 2 -1 = 0
## R5 1 0 >= 0
## R6 0 1 >= 0
## Kind Std Std
## Type Real Real
## Upper Inf Inf
## Lower 0 0
# solve
solve(lpmark)
## [1] 0
Next we get the optimum results.
# display the objective function optimum value
get.objective(lpmark)
## [1] 43443517
# display the decision variables optimum values
get.variables(lpmark)
## [1] 116666.7 233333.3
For the sensitivity part we will add two new code sections to obtain the sensitivity results.
# display sensitivity to coefficients of objective function.
get.sensitivity.obj(lpmark)
## $objfrom
## [1] -96.6820 -137.8455
##
## $objtill
## [1] 1e+30 1e+30
objfrom. Explain in concise manner what the sensitivity results represent in reference to the marketing model.# display sensitivity to right hand side constraints.
# There will be a total of m+n values where m is the number of contraints and n is the number of decision variables
get.sensitivity.rhs(lpmark)
## $duals
## [1] 124.12433 0.00000 0.00000 75.78333 0.00000 0.00000 0.00000
## [8] 0.00000
##
## $dualsfrom
## [1] 1.125e+05 -1.000e+30 -1.000e+30 -3.050e+05 -1.000e+30 -1.000e+30
## [7] -1.000e+30 -1.000e+30
##
## $dualstill
## [1] 1.00e+30 1.00e+30 1.00e+30 4.75e+05 1.00e+30 1.00e+30 1.00e+30 1.00e+30
Answer 1A) The sensitivity results in reference to the marketing model represents how much we can change the coefficients of tv and radio in the model and still retain the optimum value for sales. So we can change the coefficient of radio to -96.682 and still maintain the optimum solution for the decision variable radio, and conversely, we can change the coefficient of tv to -136.8455 and maintain the optimum solution for the decision variable.
duals. Explain in concise manner what the two non-zero sensitivity results represent. Distinguish the binding/non-binding constraints, the surplus/slack, and marginal values.To acquire a better understanding of the sensitivity results, and to confirm integrity of the calculations, independent tests can be conducted.
Answer 1B) The two non-zero results represent represent the marginal change in the optimum value by changing a binding constraint by one dollar. If we change the first constraint by 1 dollar, we change the optimum solution by about 124 dollars. If we change the fourth constraint by 1 dollar, then our optimum sales changes by about 76 dollars. The binding constraints are all of the non-zero values where there is no surplus, and any change in them will impact our optimal solution. The non-binding constraints are the values that are zero, meaning that there is a surplus, or slack in resource, and do not have any effect on the optimum value if changed.
To check the integrity of the other marginal value, you would run the same model as I did previously, except instead of changing the first constraint, I would change the fourth constraint, which is the other binding constraint. This constraint refers to the relationship of the units of tv and radio. I would change the value to the right of the “=” sign from zero to one, meaning you change the constraint by 1 unit because you are trying to calculate its marginal value. Then, you would look at the calculations and look at the difference in the optimum value calculated for the objective (sales). If done correctly, the difference should be 75.783, the same number calculated in the sensitivity model.
For this task we will be running a Monte Carlo simulation to calculate the probability that the daily return from S&P will be > 5%. We will assume that the historical S&P daily return follows a normal distribution with an average daily return of 0.03 (%) and a standard deviation of 0.97 (%).
To begin we will generate 100 random samples from the normal distribution. For the generated samples we will calculate the mean, standard deviation, and probability of occurrence where the simulation result is greater than 5%.
To generate random samples from a normal distribution we will use the rnorm() function in R. In the example below we set the number of runs (or samples) to 100.
# number of simulations/samples
runs = 100
# random number generator per defined normal distribution with given mean and standard deviation
sims = rnorm(runs,mean=0.03,sd=0.97)
# Mean calculated from the random distribution of samples
average = mean(sims)
average
## [1] -0.009794164
# STD calculated from the random distribution of samples
std = sd(sims)
std
## [1] 0.9822252
# probability of occurrence on any given day based on samples will be equal to count (or sum) where sample result is greater than 5% divided by total number of samples.
prob = sum(sims >=0.05)/runs
prob
## [1] 0.43
# Repeat calculations here
runs1 = 1000
sims1 = rnorm(runs1, mean=0.03, sd = 0.97)
average1 = mean(sims1)
average1
## [1] 0.01455443
std1 = sd(sims1)
std1
## [1] 0.9734561
prob1 = sum(sims1 >=0.05)/runs1
prob1
## [1] 0.475
runs2 = 10000
sims2 = rnorm(runs2, mean=0.03, sd = 0.97)
average2 = mean(sims2)
average2
## [1] 0.03445112
std2 = sd(sims2)
std2
## [1] 0.974756
prob2 = sum(sims2 >=0.05)/runs2
prob2
## [1] 0.4945
pi that was presented in the introductory paragraph?Case1 = 100 simulations Case2 = 1000 simulations Case3 = 10000 simulations
Case 1: Mean:-0.03215 Std. Dev:1.1011 Probability:0.4 Case 2: Mean:0.02177 Std. Dev:0.9359 Probability:0.476 Case 3: Mean:0.02113 Std. Dev:0.9735 Probability:0.4889
As the number of simulations increase, the values seem to get closer and closer to the normal distribution model that we set up, which is a standard deviation of about 0.97, and an average of 0.03. The best bet on the probability of an occurrence greater than 5% is about 47% it seems like, just based on the one scenario that I ran randomly. This is similar to the image in the beginning because the more simulations that we run, the closer and more accurate our probability value gets.
The last 2C) exercise is optional for those interested in further enhancing their subject matter learning, and refining their skills in R. Your work will be assessed but you will not be graded for this exercise. You can follow the instructions presented in the video Excel equivalent example at [https://www.youtube.com/watch?v=wKdmEXCvo9s]
runs3 = 10000
sim3 = rnorm(runs3, mean=0.03, sd = 0.97)
mean(sim3)
## [1] 0.02771242
prob3 = sum((sim3)^7 >= 0.05)/runs3
prob3
## [1] 0.2508
#probability of cumulative weekly return > 5% is ~ 26%