Nate Silver explains FiveThirtyEight's Senate forecasting model (user search)
       |           

Welcome, Guest. Please login or register.
Did you miss your activation email?
June 02, 2024, 08:52:15 PM
News: Election Simulator 2.0 Released. Senate/Gubernatorial maps, proportional electoral votes, and more - Read more

  Talk Elections
  Other Elections - Analysis and Discussion
  Congressional Elections (Moderators: Brittain33, GeorgiaModerate, Gass3268, Virginiá, Gracile)
  Nate Silver explains FiveThirtyEight's Senate forecasting model (search mode)
Pages: [1]
Author Topic: Nate Silver explains FiveThirtyEight's Senate forecasting model  (Read 2202 times)
The Ex-Factor
xfactor99
Jr. Member
***
Posts: 1,241
Viet Nam


Political Matrix
E: -5.42, S: -6.43

« on: September 17, 2014, 01:38:23 PM »

So he's calling out a guy for making his error bars too narrow??

Silver seems to have a fair point. At least in 2010, Wang apparently structured his model in a way that almost completely ruled out results that actually happened, and it wasn't even a partisan bias on Wang's part from what I can tell, since he overestimated Angle, a Republican, while underestimating the GOP's chances in the House in the same year.

For what it's worth, Wang's rebuttal is:
Quote
You must be logged in to read this quote.

And his riposte is that he predicted all the 2012 Senate races accurately, including North Dakota.:
http://election.princeton.edu/2012/11/06/senate-prediction-final-election-eve/

Personally I'm sympathetic to the argument we can improve on models of merely polling averages but Silver's state fundamentals model strikes me as absurdly complex (10 parameters?!) and very susceptible to overfitting. This comment on his latest blog entry explains it very well:

Quote
You must be logged in to read this quote.
Logged
Pages: [1]  
Jump to:  


Login with username, password and session length

Terms of Service - DMCA Agent and Policy - Privacy Policy and Cookies

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines

Page created in 0.017 seconds with 10 queries.