Skip to main content

Partisan Inflation Forecast Errors & Hurricanes

Soon to be Hurricane Isaac has thrown off mine and my coauthor Cassie Grafström's plans to present a paper at the APSA Annual Conference. The paper is on whether or not US Federal Reserve staff bias their inflation forecasts based on the president's party. In lieu of the actual presentation I thought that I would at least post our slides (below).

In a couple earlier posts I showed some graphs indicating that there might be a presidential partisan bias to Fed inflation forecasts. The bias would look like this:

  • Democratic Presidents: Inflation is over-estimated.
  • Republican Presidents: Inflation is under-estimated.

In our paper we try to find out if this is just a coincidence or if inflation forecasts are really biased by the president's party identification. After running many different models we find that, yes Fed staff predict inflation will be higher than it actually is during Democratic presidencies and lower than it is during Republican presidencies.

This figure from the paper gives you a sense of how big we predict the inflation forecast errors will be under Republican and Democratic presidents.

Simulated Inflation Forecast Errors
Simulated Expected Inflation Forecast Error (Gandrud & Grafström)
0 = no forecasting error

Inflation is expected to be about 10% higher than it actually is during Democratic presidencies. It is expected to be about 20% lower than it actually is during Republican presidencies. I'll write another post describing how we made this graph and a few others in the paper.

Now for the slides from our ill-fated APSA presentation (you can find the full paper here):


Popular posts from this blog

A Link Between topicmodels LDA and LDAvis

Carson Sievert and Kenny Shirley have put together the really nice LDAvis R package. It provides a Shiny-based interactive interface for exploring the output from Latent Dirichlet Allocation topic models. If you've never used it, I highly recommend checking out their XKCD example (this paper also has some nice background). LDAvis doesn't fit topic models, it just visualises the output. As such it is agnostic about what package you use to fit your LDA topic model. They have a useful example of how to use output from the lda package. I wanted to use LDAvis with output from the topicmodels package. It works really nicely with texts preprocessed using the tm package. The trick is extracting the information LDAvis requires from the model and placing it into a specifically structured JSON formatted object. To make the conversion from topicmodels output to LDAvis JSON input easier, I created a linking function called topicmodels_json_ldavis . The full function is below. To

Set up R/Stan on Amazon EC2

A few months ago I posted the script that I use to set up my R/JAGS working environment on an Amazon EC2 instance. Since then I've largely transitioned to using R/ Stan to estimate my models. So, I've updated my setup script (see below). There are a few other changes: I don't install/use RStudio on Amazon EC2. Instead, I just use R from the terminal. Don't get me wrong, I love RStudio. But since what I'm doing on EC2 is just running simulations (I handle the results on my local machine), RStudio is overkill. I don't install git anymore. Instead I use source_url (from devtools) and source_data (from repmis) to source scripts from GitHub. Again all of the manipulation I'm doing to these scripts is on my local machine.

Slide: one function for lag/lead variables in data frames, including time-series cross-sectional data

I often want to quickly create a lag or lead variable in an R data frame. Sometimes I also want to create the lag or lead variable for different groups in a data frame, for example, if I want to lag GDP for each country in a data frame. I've found the various R methods for doing this hard to remember and usually need to look at old blog posts . Any time we find ourselves using the same series of codes over and over, it's probably time to put them into a function. So, I added a new command– slide –to the DataCombine R package (v0.1.5). Building on the shift function TszKin Julian posted on his blog , slide allows you to slide a variable up by any time unit to create a lead or down to create a lag. It returns the lag/lead variable to a new column in your data frame. It works with both data that has one observed unit and with time-series cross-sectional data. Note: your data needs to be in ascending time order with equally spaced time increments. For example 1995, 1996