Emma Wai; Strategy; Joy

Owned by Joy He (Deactivated)
Jul 18, 2021
2 min read

  • Scope out what’s happening, unblock people

  • Member pretty casually most of 2019, and then last summer became lead

  • Not sure how much they’ll use telemetry 

  • Mostly comparing comparing stats, sensors with what’s actually happening 

  • Use case: go to telemetry directly, that’s how she’s sorting the cards

  • Don’t look at the faults directly, just look at how they affect the car

  • Respond to faults as they see it affect the vehicle performance? — ask her to walk through scenario

  • Solar studd would be looked at after the race (as retro), not during, and not through telemetry

  • Telemtetry connected? Important, tells them if connection is breaking

  • Motor controller votlage/cuurent — interesting to inform driver actions/technique

  • Care more about speed that the car is going, as opposed to drilling into stats

    • Sometimes interesting, but rarely looked at

  • Lots of this stuff, she’d look at through the strategy dashboard, not through telemetry

  • What would you look at through telemetry?

  • Can you walk us through a scenario 

  • Priority is real time data

  • If data doesn’t match up between telemetry and strategy, it’s a red flag

  • If the data changes too quickly (need smoothing) ie 15-20-15-20-15

  • Would like a highlighting feature, pin certain things, darken certain cells, that would be nice

  • If lots of scrolling, would like search/jump to feature

  • Don’t know who’s going to the races

  • Only expect one or two people using telemetry

  • All the models we designed are good, making sure no bugs

  • Access to route information

  • Based on weather for tomorrow, elevation, etc given performance of the day befoer

  • Understand how the car’s performance, optimize the score based on the regs

  • Most of it is not super relevant to strategy

  • Formula that says how many points you get depending on how you did during the race

  • Energy usage during the race

  • Need to stay above a certain speed or point deduction

  • how can you get that best score?

  • how can we correct predictions about battery stuff, etc

  • find info: super quick, couple of seconds, know where to find it

    • expects to practice with the dashboard

  • expect project itself to last a couple of months, dependent on technologies they use

  • anything that adds complexity that doesn’t add lots of value, avoid

  • we give them design, they will come back to us and tell us feasibility 

  • accessing the connection will the biggest issue

  • if can fails, something fails, that would be the biggest most worrying failure

  • python is their main language

  • driver display failed bc it used dart, ppl didn’t know dart 

  • if there’s a connection error, should absolutely be an error message telling the user what’s happening, if something’s slow, etc

  • if bandwidth of transmitting data goes over, would want to see that, but not that big of an issue

  • Likely python. past may have been grafana