Skip to content

Statistics

Jump to bottom
David Smith edited this page Mar 20, 2024 · 1 revision

MoSCoW Requirements

  • Must

    • M01: The commentator must have access to a Statistics page
    • M02: The commentator statistics page must automatically update when the next racer is selected for timekeeping
    • M03: The commentator must have a ranking of the fastest lap's from that event and from the actual racer.
    • M04: The commentator must have a ranking of the slowest lap's from that event and from the actual racer.

  • Should

    • S01: The commentator should have the actual racinfo (Name, currentLapTime, remeiningRaceTime, restesCurrentLap)

  • Cloud

    • C01: The commentator cloud have a ranking of the fastest lap's on that track from previous summits/events.
    • C02: The commentator could have information about the amount of off-track's/wall hits for the racer

  • Will not

    • W01: We will not gather additional User information besides the name, email and country of origin because of PII concerns.
External Input (Click to expand)

Additional input

Great idea indeed to want to provide more data during the event to make the commentary more informative/entertaining and also enhance the audience’s experience.

There are many things to talk about. Here are a few:

1) a fastest lap time performance ranking (which is essentially what we use to rank the contestants)

**2) a slowest lap time performance ranking **

3) a ranking featuring the number of resets: highest amount, lowest amount / some developers cannot do a lap without 5/6/7 resets. But how many is a lot? What’s the most amount of resets recorded? The least amount? These all make for fine talking points.

  1. the bends that are the hardest to clear. I remember on last year’s track, bend number three seemed to often times be a tricky curve to manage. / this year’s track looks even fancier - so undoubtedly there will be sections which are harder than others. If we have stats on them, it would help the storytelling. Imagine after a few summits “Brussels had issues with turn 2. 189 resets were initiated on that particular bend, but Paris was a different game. The French developers only leaving the track on 112 instances but had more of a problem with turn 3. D-Bro, you’ve studied the 2023 track closely, what’s your take on this? Why are some having issues with 2 and others with 3?” etc… that gives opportunities to discuss facts.

  2. If we had the stats on how many drivers went off track it would be a fun talking point.

If you recall every time a driver goes off track and hits the wall, i say something along the lines of “AND BANG INTO THE WALL.” If we had a counter of how many cars banged the wall, we’d also have a fun bit of commentary. “oh it’s the 10th, 25th, 50th and 100th time a developer goes “STRAIGHT INTO THE WALL!” Adds more fluff.

Maybe even a “HEADBANGER CLASSIFICATION” with developers who hit the wall the most. “Ohhh FatAlbert hitting the wall 8 times during his three minute run. He is the new leader of the HEADBANGER classification, well done FatAlbert!”

Those are a few random ideas. Do you need more? How many were you thinking implementing?

The next challenge would be: how do you get the info to the announcer. It’s one thing to have the data - but I would have to be able to access it and to know it’s updated. Would you assign a floor manager or someone at a computer I could check with every so often?

As for the driver/developer information I see this as a more challenging part. As you’ve noted I’ve been able to get people to try DeepRacer out by promising a “lightning-fast signup experience” 30 seconds from onlooker to track racer. If you start adding questions, you might get some people who just can’t be bothered with the process.

That being said, if you decide to go through with the idea, a good starting point would be:

  • where they are from
  • favorite food
  • favorite sports team
  • favorite holiday destination

Anything that would allow for fun ad-libbing. There could be many more, but lengthening the signup process should, in my opinion, be handled delicately.

Another element to factor in is repetition. Yes, for us who spend all day 9-6 trackside it feels like it’s always the same thing with few variations. But our audience isn’t made of people who stay there all day. They come up, watch 5-10-15 minutes and get on with their day. So it might feel as an eternal repetition for us, but is much less so for the spectators.

It’s crucial to keep the energy high, so that someone who shows up at 4:15 PM for the first time gets the same commentary experience as someone who comes in at 10:00 AM. I really try to be as high octane as possible, all day. And when I see a “game-changing performance” I rev it up even more.

Clone this wiki locally