-
Notifications
You must be signed in to change notification settings - Fork 100
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
Verify Schedule.json accuracy #125
Comments
Hey, I'm happy to help take a look at this. Is there a specific ground truth source you want to compare it to? |
I will likely fold anything you contribute into the |
Okay, I've run through all the data and found the following:
As for folding it into a script, I'm happy to help out with that and share the (somewhat messy) code I've used to check the games and edit it as needed; as you know I've just started contributing to this project so am willing to follow your guidance and do whatever you think is best. |
My role was always more on the support side, but this was one of the only bits of code I actually contributed...ooof - gut punch. Any idea where the logic is wrong? https://github.com/derek-adair/nflgame/blob/master/nflgame/update_sched.py#L80-L109 |
Okay, I've found two main things, and lost a bit of my sanity in the process: 1a) Quite often the games
In this example, game 55459 actually occurs 30 minutes before 55470 (and an hour and a half before 55469, for that matter), yet is numbered after both of them. This also has the secondary effect of incorrectly marking all games before it on that day as AM as well. Not sure what we can do about this if the NFL insists on numbering them incorrectly. 1b) Occasionally (7 times), the same occurs in the postseason. For example:
This could probably be fixed by moving the logic on lines 108 and 109 up to before the rest of the logic, as to my knowledge, games in the postseason are always in the afternoon, at least in Eastern Time. 1c) This also occurred in the regular season for games 57302 and 55023, the former I think when a game was flexed to Sunday night, and the latter some weirdness when there were two Monday night games that kicked off an hour apart, for which I have no idea why. These are probably small enough edge cases to not worry about.
So overall, one of the bugs is easily fixable, but the other one is more inherent to using |
Thanks for your hard work! Any of the scripts you used to verify this would be great! Definitely start a PR draft.
Again thanks for your detective work. If @andrew-shackelford or @ochawkeye wanna toss a PR against the dev branch pulling from the new api w/ the 24 hour clock I'd be happy to get it in. Otherwise I can probably do this some time in the next week. Also @andrew-shackelford definitely submit a PR w/ your scripts and we'll figure out how to get you some contribution credit. |
Also a gist w/ the different eid's w/ improper data for me to investigate may help. Something like...
|
Okay, I just sent in PR #131 . I wasn't entirely sure how you wanted it added to the library, so please let me know if there are any changes you want made and I'm happy to make them. I had to include the feeds-rs files in the commit as it looks like the NFL has revoked access to them. Also, I caught one error I had made which is that by using a lazy try/except loop I had marked some games as missing when it was actually just that their meridiem was missing. It turns out all games are present except for the pro bowl games, so that's good. |
This is correct, the NFL has yanked all of the feeds. This will be on hold until I can make some adjustments to how this whole thing works without that feed. |
Literally just comb over schedule.json and make sure it reflects the games that have happened so far.
The text was updated successfully, but these errors were encountered: