-
Notifications
You must be signed in to change notification settings - Fork 61
Description
Is there an existing issue for this?
- I have searched the existing issues
Have you installed the latest development version of the package(s) in question?
- I have installed the latest development version of the package.
If this is a data issue, have you tried clearing your nflverse cache?
I have cleared my nflverse cache and the issue persists.
What version of the package do you have?
nfl_data_py-0.3.3
Describe the bug
Targets and receptions are nearly equal for 2003 - 2008:
2000 - Targets 15653 - Receptions 9312
2001 - Targets 15824 - Receptions 9542
2002 - Targets 16854 - Receptions 10314
2003 - Targets 9700 - Receptions 9697
2004 - Targets 9773 - Receptions 9773
2005 - Targets 9793 - Receptions 9793
2006 - Targets 9826 - Receptions 9801
2007 - Targets 10443 - Receptions 10429
2008 - Targets 10105 - Receptions 10089
2009 - Targets 16803 - Receptions 10375
Reprex
# Load season-level data (e.g., from 1999 to 2023)
seasons = list(range(2000, 2010))
df = nfl.import_seasonal_data(seasons)
df.sort_values('season', inplace = True)
for s in df.season.unique():
print('{} - Targets {} - Receptions {}'.format(s, df[df.season == s].targets.sum(), df[df.season == s].receptions.sum()))Expected Behavior
I'm expecting the ratio to look more like 2000-2002 or 2009.
2000 - Targets 15653 - Receptions 9312
2001 - Targets 15824 - Receptions 9542
2002 - Targets 16854 - Receptions 10314
2003 - Targets 9700 - Receptions 9697
2004 - Targets 9773 - Receptions 9773
2005 - Targets 9793 - Receptions 9793
2006 - Targets 9826 - Receptions 9801
2007 - Targets 10443 - Receptions 10429
2008 - Targets 10105 - Receptions 10089
2009 - Targets 16803 - Receptions 10375
nflverse_sitrep
NAScreenshots
Additional context
No response