• Dave
    link
    fedilink
    113 months ago

    The above outputs are achieved by solving energy balance equations using the immense cloud computational power provided by AWS.

    if tail_light_last_on_secs_ago < 20:
        mode = recharge
    elif tail_light_last_on_secs_ago > 60:
        mode = deploying
    else:
        mode = neutral
    
    • @PhotographerM
      link
      fedilink
      63 months ago

      IMMENSE CLOUD COMPUTATIONS FROM AWS!!!

      ZHOU TO OVERTAKE MAX IN 7 LAPS!!!

  • @bhmnscmm
    link
    fedilink
    23 months ago

    The identification of the driver behaviours is obtained thanks to a correlation analysis of the driver’s demands and the characteristics of specific sections of the circuit.

    Sounds like the battery charge and mode isn’t actually being directly measured. Seems like they’re just inferring with a model.

    Either way, I’m not really a fan of this. It’s kinda cool for fans, but I think this is giving too much valuable information to other teams. There will be less uncertainty and risk in strategy.

    • @PhotographerM
      link
      fedilink
      23 months ago

      “immense calculations, cloud computations” yada yada

      Would rather see if the battery is being deployed or charged than some guess as to what happened last lap

      • bedrooms
        link
        fedilink
        23 months ago

        Yeah.

        Until now, broadcasters and fans have only been able to hazard a guess at a driver’s energy usage tactics.

        Now, broadcasters and fans are only able to hazard a guess at how that unexplained model works.

    • @cx0derOP
      link
      fedilink
      13 months ago

      Rival teams can already determine this too a large extent, based on sector times, blinking lights, etc.

      Wouldn’t something like this has to be approved by teams before broadcast?

    • @0000000nowhere
      link
      fedilink
      13 months ago

      Don’t worry, Christian and Toto will most likely lobby it into oblivion in no time