In a previous post, we built an R Notebook that pulled in data on sector ETFs and allowed us to calculate the rolling correlation between a sector ETF and the S&P 500 ETF, whose ticker is SPY. Today, we’ll wrap that into a Shiny app that allows the user to choose a sector, a returns time period such as ‘daily’ or ‘weekly’, and a rolling window. For example, if a user wants to explore the 60-day rolling correlation between the S&P 500 and an energy ETF, our app will show that. As is customary, we will use the flexdashboard format and reuse as much as possible from our Notebook.
The final app is here:
The first code chunk is where we do the heavy lifting in this app. We will build a function that takes as parameters an ETF ticker, a returns period, and a window of time, and then calculates the desired rolling correlation between that ETF ticker and SPY.
library(flexdashboard)
library(tidyverse)
library(tidyquant)
library(highcharter)
# A function to build an xts object to hold both sector and index returns.
sector_correlations <- function(sector, period = "weeks", window = 10) {
symbols <- c(sector, "SPY")
prices <-
getSymbols(symbols, src = 'yahoo',
auto.assign = TRUE, warnings = FALSE) %>%
map(~Cl(get(.))) %>%
reduce(merge) %>%
`colnames<-`(symbols)
prices_period <- to.period(prices, period = period, OHLC = FALSE)
# get monthly log returns
returns <-na.omit(ROC(prices_period, 1, type = "continuous"))
# change date format
index(returns) <- as.Date(as.yearmon(index(returns), format = '%Y%m'))
returns$rolling_cor <- rollapply(returns, window,
function(x)
cor(x[, 1], x[, 2], use = "pairwise.complete.obs"),
by.column = FALSE)
# We care about the name because it will be displayed in the dygraph when a user hovers.
names(returns) <- c(paste(sector, "Returns", sep = ""), "SPY Returns", paste(sector, "/SPY Correlation", sep = ""))
assign("sector_correlations", returns, .GlobalEnv)
}That function uses getSymbols() to pull in prices and periodReturns() to convert to log returns, either daily, weekly or monthly. Then we merge into one xts object and calculate rolling correlations, depending on the window parameter. It should look familiar from the Notebook, but honestly, the transition from the previous Notebook to this code chunk wasn’t as smooth as would be ideal. I broke this into two functions in the Notebook, but thought it flowed more smoothly as one function in the app since I don’t need the intermediate results stored in a persistent way. Combining the two functions wasn’t difficult, but it did break the reproducible chain in a way that I don’t love. In the real world, I would (and, in my IDE, I did) refactor the Notebook to line up with the app better. Enough self-shaming, back to it.
Next, we need to create a sidebar where our users can select a sector, a returns period and a rolling window. Nothing fancy here, but one thing to note is how we use selectInput to translate from the sector to the ETF ticker symbol. This means our users don’t have to remember those three-letter codes; they just choose the name of the desired sector from a drop-down menu.
helpText("Choose a sector")
# Don't make the user memorize the ETF ticker symbols!
# Let them choose the intuitive sector name and then translate to the
# ticker symbol in the background.
fluidRow(
column(9,
selectInput("sector", "Sector ETF",
c(
"Energy" = "XLE",
"Financials" = "XLF",
"Health Care" = "XLV",
"Industrials" = "XLI",
"Materials" = "XLB",
"Technology" = "XLK",
"Utilities" = "XLU",
"Cons Discretionary" = "XLY",
"Cons Staples" = "XLP")))
)
helpText("Choose a returns time period and a rolling window")
fluidRow(
column(7,
selectInput("period", "Time Period", c("days", "weeks", "months"))),
column(7,
numericInput("window", " Rolling Window", 10, min = 5, max = 50, step = 5))
)Have a close look at the last three lines of code in that chunk. These are a new addition that let the user determine if the mean, max and/or min rolling correlation should be included in the dygraph. We haven’t built any way of calculating those values yet, but we will shortly. This is the UI component.
Those three lines of code create checkboxes and are set to default as FALSE, meaning they won’t be plotted unless the user chooses to do so. I wanted to force the user to actively click a control to include these, but that’s a purely stylistic choice. Perhaps you don’t want to give them a choice at all here?
Next, we create our reactive values that will form the substance of this app. First, we need to calculate and store an object of rolling correlations, and we’ll use a reactive that passes user inputs to our sector_correlations function.
Then, we build reactive objects to store mean, minimum and maximum rolling correlations. These values will help contextualize our final dygraph.
# Build our correlation time series object here
# so we can access it throughout the rest of the app.
sector_correlation <- reactive({
sector_corr <- sector_correlations(input$sector, input$period, input$window)
sector_corr[, 3]
})
# Let's calculate mean, minimum and maximum rolling correlations.
# We'll use these in the value boxes.
avg <- reactive({
avg <- round(mean(sector_correlation(), na.rm=T), 2)
})
mini <- reactive({
mini <- round(min(sector_correlation(), na.rm=T), 2)
})
maxi <- reactive({
maxi <- round(max(sector_correlation(), na.rm=T), 2)
})At this point, we have done some good work: built a function to calculate rolling correlations based on user input, built a sidebar to take that user input, and coded reactives to hold the values and some helpful statistics. The hard work is done, and really we did most of the hard work in the Notebook, where we toiled over the logic of arriving at this point. All that’s left now is to display this work in a compelling way.
renderHighchart({
# The output of this is an xts
sector_correlation <- sector_correlation()
highchart(type = "stock") %>%
hc_title(text = "Rolling Correlation") %>%
hc_add_series(sector_correlation, name = names(sector_correlation[, 1]), color = "green") %>%
hc_add_theme(hc_theme_flat()) %>%
hc_navigator(enabled = FALSE) %>%
hc_scrollbar(enabled = FALSE)
})That dygraph code should look familiar from the Notebook and previous posts, except we have added a little interactive feature. By including if(input$mean == TRUE) {avg()}, we allow the user to change the graph by checking or unchecking the ‘mean’ input box in the sidebar. We are going to display this same information numerically in a value box, but the lines make this graph a bit more compelling.
Speaking of those value boxes, they rely on the reactives we built above, but, unlike the graph lines, they are always going to be displayed. The user doesn’t have a choice here.
valueBoxOutput("approvalBox1")
output$approvalBox1<-renderValueBox({
# Display the mean we calculated in 'avg' reactive function above.
valueBox(value = avg(), icon = "fa-line-chart", color = "primary")
})This a simple but powerful app: the user can choose to see the 60-day rolling correlations between the S&P 500 and an energy ETF, or the 10-month rolling correlations between the S&P 500 and a utility ETF, etc. I played around with this a little bit and was surprised that the 10-week rolling correlation between the S&P 500 and health care stocks plunged in April of 2016. Someone smarter than I can probably explain, or at least hypothesize, as to why that happened.
A closing thought about how this app might have been different: we are severely limiting what the user can do here, and intentionally so. The user can choose only from the sector ETFs that we are offering in the selectInput dropdown. This is a sector correlations app, so I included only a few sector ETFs. But, we could just as easily have made this a textInput and allowed the users to enter whatever ticker symbol struck their fancy. In that case, this would not longer be a sector correlations app; it would be a general stock correlations app. We could go even further and make this a general asset correlations app, in which case we would allow the user to select things like commodity, currency and housing returns and see how they correlate with stock market returns. Think about how that might change our data import logic and time series alignment.