HuskieRobotics / HuskieRobotics/SPOT

Timing does not account for the few seconds between autos and teleop periods

Open
#298 2 comments 0 reactions 1 assignee Claimed by @adamkuc9 View on GitHub
bug
Dominant language
JavaScript
Stars
27
Forks
29
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
SPOT's timing does not account for the about 3 second period when the match timer is paused in between the autos and teleop periods. During this period, the match timer is paused and every robot has about 3 seconds (I'm not sure of the exact timing, I'll have to find that out while fixing) while they switch from autos to teleop.

This causes issues for users who try to line up the start of the match in the app with the real-life start of the match as everything after autos is shown to them ~3 seconds early (for example during Rebuilt the screen where the scouter must select if their assigned team's first shift is active or inactive, in addition to other things like the end of the match).

**To Reproduce**
Steps to reproduce the behavior:

1. Pull up a video of any match to offline scout (though Rebuilt applies here because that's the most recent game)
2. Start the match in SPOT at the same time it starts on video
3. SPOT will not account for the ~3 second period while robots and the match timer are paused, causing everything afterwards to happen early

**Expected behavior**
SPOT's match timer is paused during this period as well so that scouters who line up their scouting with a real-time match may do so more effectively.

**Versions: (please complete the following information):**

- Server
- OS: Unknown (any)
- Node Version: Unknown (any)
- SPOT Version: v5.1.0
- Client
- OS: Any
- Browser: Any

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.