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
Describe the bug
Some teams' recent OPR calculated as 0 for lower amounts of days than 30.
To Reproduce
Steps to reproduce the behavior:
Run statistics calculations on a team that hasn't played within NUMBER_OF_DAYS_FOR_RECENT_OPR days
Push to Sheets or otherwise export OPR data
See that recent OPR calculations are 0
Expected behavior
Recent OPR calculation
Keeps increasing recent number of days until an event is found, or
Uses last event.
It should also log a warning to errors.log.
Actual behavior
Since the team hasn't played within the constant NUMBER_OF_DAYS_FOR_RECENT_OPR amount of days, the script runs into an error and sets all statistics for that team to be 0.
System:
All OS platforms
All browsers
Main v49.0 Alpha
Additional context
Pulled from todos.md on 12/23/2024
Targeted for first major post-release update.
Note that NUMBER_OF_DAYS_FOR_RECENT_OPR is set in common_resources.py and is called in loadMatchesByRecent in OPR.py.
The text was updated successfully, but these errors were encountered:
Describe the bug
Some teams' recent OPR calculated as 0 for lower amounts of days than 30.
To Reproduce
Steps to reproduce the behavior:
NUMBER_OF_DAYS_FOR_RECENT_OPR
daysExpected behavior
Recent OPR calculation
It should also log a warning to
errors.log
.Actual behavior
Since the team hasn't played within the constant
NUMBER_OF_DAYS_FOR_RECENT_OPR
amount of days, the script runs into an error and sets all statistics for that team to be 0.System:
Additional context
Pulled from todos.md on 12/23/2024
Targeted for first major post-release update.
Note that
NUMBER_OF_DAYS_FOR_RECENT_OPR
is set incommon_resources.py
and is called inloadMatchesByRecent
inOPR.py
.The text was updated successfully, but these errors were encountered: