-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LeSean McCoy Yards in 2013 200 short #24
Comments
Ah wow! I was almost about to say, "Sorry, but the data is sometimes inaccurate." Instead, I dug a little bit. I'll share my process in case someone else finds it useful. First, I wanted to reproduce it, so I ran
Then I took a look at McCoy's game log, and indeed, weeks 16 and 17 are way off. The next step is to investigate whether nflgame has the same error: import nflgame
mccoy = nflgame.find('LeSean McCoy')[0]
stats = mccoy.stats(2013)
print stats.rushing_yds Output: Yikes! I'm not sure what happened, but maybe something happened while updating. (I keep it running while the games are playing for live updates.) Once the game is considered "finished", no more updates are made. So if the update failed while the game was playing---and only updated for the first quarter, for example---then nfldb would eventually consider that game finished. Therefore, Luckily, the fix is simple. Just blow away week 16 and week 17 from the database and rebuild it with
(N.B. This will automatically delete all drives, plays and stats associated with those games because of cascading foreign key constraints.) And now
|
I've updated the database dump so that future builds will have the correct data. Thank you! |
Thanks @BurntSushi ! |
Love the DB. Spotted an issue:
If I import the DB and run this query:
Rushing yards look accurate vs ESPN/NFL records:
http:https://espn.go.com/nfl/statistics/player/_/stat/rushing/sort/rushingYards
except for LeSean McCoy who is off by 200 yards.
The text was updated successfully, but these errors were encountered: