Emma Wai; Strategy; Catherine

Owned by Catherine Burns
Jul 20, 2021
2 min read

Why use the telemetry dashboard:

  • Interested in projecting what's happening and how is this going to happen so they won’t have too much interest in the current information

  • Curious about feeding information and how the information is being accessed



Card Sorting exercise:

  • Strategy dashboard (will mainly be using information from their own dashboard) and telemetry dashboard

  • The information sorted does not necessarily mean they don’t care about it, they will be able to grab this information on their own and have no need for telemetry

  • When encountering a fault, they react to it with respects to how it impacts the rest of the vehicle (they don’t react like “this fault → this fix”)

  • Pedal outputs could be interesting

  • Care more about the speed at which the car is going instead of the left and right motor velocity cards

  • Mech brake - nice to see and not something their team will check regularly for in the dash

  • Monitoring the speed in general, accurately, is important to them



Do they care about historical data:

  • Real time data including average speed (which encompasses historical speed)

  • In general won’t look at the telemetry dashboard



Why use telemetry instead of strategy dash:

  • Only look at telemetry if it isn’t available through strategy

  • Ensure that the sensors are accurate by comparing the data



At what point does the information become overwhelming:

  • When the data is moving too quickly and is flickering → doesn't imply what the actual value is

  • Highlighting feature could be useful

    • Darkening certain cells to focus on one piece of data or perhaps pinning items

 

Make it easier?:

  • Perhaps a search feature or jump-to feature (if there is a lot of information)

 

Who on the team would be using it:

  • Probably only 1 or 2 strategy people there

  • Their roles will be to ensure that everything works, data is still flowing, etc. 

  • They will ensure they have access to the route information, weather, elevation, etc. 

  • Telemetry will probably notify them of any issues

 

Strategy end-goal:

  • Understand how the car is performing and modify based on the score

  • Based on ASC regulations, there is a formula for gaining points, what is the highest score they can get based on their predictions



Time expectations:

  • Should be able to access information almost instantly

  • Keep things simple, they would like to do some user testing



Obstacles during the race:

  • INTERNET!! Losing CAN signals or access to the servers is the biggest concern during the race

    • With proper error states and error handling, the disappearance of handling won’t be on the telemetry dashboard

    • Connection errors should be indicated to users

    • If things go wrong, any sort of problems with receiving signals etc. communicate that to users!!

  • Worried about the bandwidth? Shouldn’t be too much of a problem



Programming languages:

  • Python

  • Dash will likely be programmed in python, grafana (go)