Last year, settings for FGC 2022 were added directly to the main Settings component, and had to be deleted after the event. This has multiple downsides:

• It puts the repo in a weird state for usage with non-FGC events
• After the FGC event concludes, it reduces the amount of testing you can do on how new changes affect FGC

It looks like we should be able to implement a per-season settings tab by adding a SettingsTab entry to the SeasonComponents interface.

Or move "field prep" button to before "prestart" button and rename it.

Match preview should just post the teams playing next onto the audience display. Maybe even set the field lights to green since post the green lights from "post results" won't be available for the very first match.

And the stack lights go blinky blinky and are confusing

Run the motors backwards on "commit" button press

I choose match 12 and then the next match it wanted to go to was match 1 when match 12 ended.

Steps to reproduce:

1. Open head ref page and side ref page on 2 tablets/devices separate from the machine EMS is running on
2. Start a match
3. On side ref tablet, increase foul count
4. Confirm head ref tablet sees the change
5. Repeat step 3 like 20 times or so
6. See that the head ref tablet will no longer match what is on the side ref tablet
7. Update something else like storage level on side ref and the fouls will finally update

@kyle-flynn

Much of this feedback comes from Greg and David

Referee app feedback

• Referee pages often use team IDs instead of names. We definitely should use the team name instead (maybe even the long name), and ideally we'd also like to include the flag.
  • I have found the team identifier setting. We'd still like to include the flag though.
• The referee app should fit on the tablets we're using without scrolling
  • A simple way to do this is to make the referee app enter fullscreen mode. Calling document.querySelector("body").requestFullscreen() from the console makes it fit nicely.
  • To test that it continues to fit as you make changes, use Chrome's Device Mode
    • Set the viewport size to 600x1000
    • Set the device type to Desktop (touch)
• Scores should not be allowed to be set lower than 0 or higher than the max possible value. There are only 144 hydrogen balls, and 72 oxygen balls.
• A thin line between each score/card/foul selection would be helpful for visual separation

Miscellaneous

• The match detail editor is not implemented
• The scoring app does not display the score breakdown
  • Side note, what are the zeros next to the red/yellow card selectors?
• The non-functional notification bell icon should be hidden

If there are specific items here that you don't have time for and would like me to help with, let me know.

There were a few other issues that I'll just submit PRs for.

(Double action button like the prestart)

First action should be an all clear button that sets the lights to green.
Second button should be commit which will "lock in the scores" or whatever it does right now minus the green lights.

This would be useful if there is ever the case that referees are still talking about the score, but the field is ready to be reset. Also doesn't ruin your precious 12 column 6 buttons

• Create Socket Room
• Broadcast Events from PLC
• Broadcast Switch Prestart Events
• Broadcast Driverstation Prestart Events
• Broadcast AP Prestart Events
• Build GUI

The three servers (API, realtime, and web frontend) should use the same mechanism to configure this. This is a low priority.

I believe we fixed this during our last meeting (at least for storage level, not card status or fouls), but we never changed it on main

Reproduce:

1. Open Scoring App and Scorekeeper page (carbon) on a computer
2. Open any Referee page on tablet
3. Start match on computer
4. Increment score so its not 0
5. Select a storage level on tablet
6. See that score resets to 0

MatchTimer works be decrementing the time remaining in a setInterval() callback. This is sub-optimal, because according to MDN, the delay parameter specifies the time in between each execution of the callback, meaning that the time that it takes to run the callback will not be counted. Additionally, since this is not a real-time system (potentially made worse by the fact that JS is single-threaded), the callback is not guaranteed to be called immediately once the specified delay has elapsed.

There should be a source-of-truth start time (set via performance.now(), which is a monotonic clock) that gets used to determine the amount of time left / state of the match.

If it can't be fixed, maybe just keep the telnet connection open?

As a part of #37 , Each FMS service should register its self for "capture" and "assignment" to a field within EMS, here is the proposed flow

• User logs into FMS local standalone service
• FMS Service registers itself as an available field set to EMS user on their acct
• User can select field set and assign it to a field within EMS
• FMS Service can be further configured from there

I keep seeing after post results the red and blue do not update with the next matches teams and score of being zero.

It covers the 3rd team and the total score covers the penalty row

(1920x1080 full screen)

Steps to reproduce:

1. Start match
2. Increment carbon level to non-zero
3. On referee tablet, refresh the referee app
4. Change storage level or foul count
5. See that the score on scoring app will reset to 0

Expected: Refreshing or navigating back to a page should not lose track of the current match

Right now, the frontend is built using Vite during development, which uses esbuild to compile the Typescript files, but does not do any type checking. We should to set up vite-plugin-checker to check for Typescript errors. There is old code from previous seasons that currently has errors.

Under the status quo, you can break things without realizing it until you actually visit a broken page, since developers are unlikely to manually run the build script when vite handles auto-building for you.

EMS will one day be in the cloud, so offer EMS as a separate service

related to #6

I think the expected behavior is to reset the cards? At least in quals

This could be an issue within Kettering's PLC, but more investigation will need to be done

• DB Table
• API Routes
• Frontend GUI in settings

It's far too easy to lose changes that you've put a lot of time into, especially when the save button is so non-obvious.

If you leave the scoring app mid match it will return on match not selected.

• Bypass
• Robot Status
• Prevent Match Start when robots aren't connected

For example, if head referee wants to edit the carbon level on their page by clearing the current carbon level, it will add a 0 to the input box and move the cursor before the 0, and typing something like 125 will end up as 1250 which will get capped at 165 which is not right.