Skip to main content

Update to Partisan Bias in Fed Inflation Forecasts

Since I'm in the depths of PhD thesis revisions I haven't had much time to do much other than update previous posts (see my Stata Country Standardizer Update).

Here is an update of an earlier post about possible partisan biases in US Federal Reserve staff inflation forecasts (these influence Federal Open Market Committee meetings where US monetary policy is largely made). The new graph below allows us to see even more of what has been going on over time.

The partisan effect is less obvious than in the earlier graph, but is is clear that during this time period the big over estimations are during Democratic presidencies and the big (actually almost all) underestimations are during Republican ones. The effect would be even stronger if we took out the end of Reagan's first term and his second one, where Fed staff may not have fully adjusted their forecasting to reflect the Volker-Greenspan era of moderate inflation.

For more details about the graph (sources, how 'error' is defined, etc.) see the earlier post.

Greenbook Inflation Forecast Errors, by Presidential Party
Note, the shaded area indicates minimal error.

The R Code:



Labels:

Comments

Rob said…
Are no data more recent than 2005 available?
23:31
Unknown said…
There are a few more recent quarters that the Fed has released that I haven't added to the data set yet.

But, like FOMC minutes, there is a couple year lag on the release of the forecasts.
06:26
Unknown said…
Sorry, I meant transcripts.
23:45
Post a Comment

Popular posts from this blog

Dropbox & R Data

I'm always looking for ways to download data from the internet into R. Though I prefer to host and access plain-text data sets (CSV is my personal favourite) from GitHub (see my short paper on the topic) sometimes it's convenient to get data stored on Dropbox . There has been a change in the way Dropbox URLs work and I just added some functionality to the repmis R package. So I though that I'ld write a quick post on how to directly download data from Dropbox into R. The download method is different depending on whether or not your plain-text data is in a Dropbox Public folder or not. Dropbox Public Folder Dropbox is trying to do away with its public folders. New users need to actively create a Public folder. Regardless, sometimes you may want to download data from one. It used to be that files in Public folders were accessible through non-secure (http) URLs. It's easy to download these into R, just use the read.table command, where the URL is the file name
52 comments
Read more

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
46 comments
Read more

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
22 comments
Read more