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
Before 2006, the WNBA played two 20-minute halves. Beginning in the 2006 season, they switched to 4 10-minute quarters. This impacts many of the assumptions that appear to be driving the timekeeping logic in the end_half_seconds_remaining and end_game_seconds_remaining columns. This also impacts the period_display_value column.
This occurs because the first and second half are tagged as "1st Quarter" and "2nd Quarter", OT as "3rd Quarter", and 2OT as "4th Quarter" (and 2005 did not have any games that reached 3OT).
Expected behavior
Before 2006, I expect the end of a game to be the end of the second period, and seconds remaining to be reflecting this clock difference.
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
Data bug, not usage or functionality.
The text was updated successfully, but these errors were encountered:
Describe the bug
Before 2006, the WNBA played two 20-minute halves. Beginning in the 2006 season, they switched to 4 10-minute quarters. This impacts many of the assumptions that appear to be driving the timekeeping logic in the
end_half_seconds_remaining
andend_game_seconds_remaining
columns. This also impacts theperiod_display_value
column.To Reproduce
This occurs because the first and second half are tagged as "1st Quarter" and "2nd Quarter", OT as "3rd Quarter", and 2OT as "4th Quarter" (and 2005 did not have any games that reached 3OT).
Expected behavior
Before 2006, I expect the end of a game to be the end of the second period, and seconds remaining to be reflecting this clock difference.
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
N/A
Additional context
Data bug, not usage or functionality.
The text was updated successfully, but these errors were encountered: