You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The source of the data which populates the individuals on the 53-man roster for a given week is not clear.
Describe the solution you'd like
Add 1-2 lines in load_rosters() or a dependency that indicates the source for this data.
Describe alternatives you've considered
A field in the dataframe that explicitly references the datasource that was used to determine the player was on the 53-man for this week and year.
Additional context
Had a friend ask me about source in a sports analytics chat I belong to, I did not have a satisfying answer for him.
The text was updated successfully, but these errors were encountered:
Desire is to understand veracity of roster data in the package at kickoff for relevant week and year, especially for the past 1-2 year's data. Goal is to use it for an anti-points league, to validate whether a rostered player could have accumulated fantasy points.
Closing this as not planned. fwiw in an anti-points league I'd probably award positive points for every snap and negative points for every stat accumulated, that would up the challenge to finding the really irrelevant players on the field
Is your feature request related to a problem? Please describe.
The source of the data which populates the individuals on the 53-man roster for a given week is not clear.
Describe the solution you'd like
Add 1-2 lines in load_rosters() or a dependency that indicates the source for this data.
Describe alternatives you've considered
A field in the dataframe that explicitly references the datasource that was used to determine the player was on the 53-man for this week and year.
Additional context
Had a friend ask me about source in a sports analytics chat I belong to, I did not have a satisfying answer for him.
The text was updated successfully, but these errors were encountered: