• Dave@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    1 year 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
    
  • bhmnscmm@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    1 year 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.

    • Photographer@lemmy.worldM
      link
      fedilink
      arrow-up
      2
      ·
      1 year 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@kbin.social
        link
        fedilink
        arrow-up
        2
        ·
        1 year 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.

    • cx0der@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year 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?