-
Notifications
You must be signed in to change notification settings - Fork 53
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
2024_19_GB_PHI
has different drive result with what on ESPN.com
#506
Comments
This is intentional (https://github.com/nflverse/nflfastR/blob/master/R/helper_add_fixed_drives.R#L17) but don't feel strongly here To me it feels weird to call what the Packers had a drive if they never had the ball. If it were a recovered onsides kick would ESPN give them a drive? |
I would like to keep the logic as is since it's not really different from an onside kick. However, I understand that starting with drive no. 2 is weird. I see 51 games since 2001 that start with drive no. 2 after a fumbled kickoff or recovered onside kick to start the game. Maybe we can handle this specific situation and decrement fixed drive @guga31bb ? |
Fine with me! |
I think we could use this logic with row == 2 nflfastR/R/helper_add_fixed_drives.R Lines 90 to 91 in 7d53e07
Something along new_drive = dplyr::if_else(.data$row == 2, 0, .data$new_drive) |
Actually if we do that, we end up with changing posteams and non changing fixed drive? |
while in ESPN play_by_play
I think the 1st drive which result was FUMBLE is missing in PBP data.
Is it on purpose or a bug?
The text was updated successfully, but these errors were encountered: