Mobileye Driving Experience Platform: Architecture, Abstractions, and APIs

Поделиться
HTML-код
  • Опубликовано: 15 окт 2024

Комментарии • 8

  • @Scott-sm9nm
    @Scott-sm9nm 9 месяцев назад +2

    Really an excellent presentation that gave an overview of the complication and what was taken into account for a more generic implementation.

  • @heyalchang
    @heyalchang 9 месяцев назад +3

    There's a certain amount of (understandable) cope in this presentation. Differentiation is a secondary requirement to having a working solution that's competitive in the marketplace.

  • @andrewsteinhaus8267
    @andrewsteinhaus8267 9 месяцев назад

    Over time, all of this differentiation will converge as users will have preferences. Most cars in the future will have some setting between sport and comfort. All OEMs will be offering these for users to setup the mode. For Robot taxis, it will likely baised to comfort mode

  • @noisypl
    @noisypl 8 месяцев назад

    This makes no sense to me, to work on making the final solution different for different OEMs, before solving autonomy first. It is like at the stage of planning, making sure that each space elevator will be different and unique. This doesn't matter. Big LOL.

    • @blanamaxima
      @blanamaxima 8 месяцев назад +1

      Automated features exist today, this applies to them as well , not only for robotaxi.

  • @blanamaxima
    @blanamaxima 8 месяцев назад

    So Shai argues for OEMs to stop doing SW and tune the Mobileye SW 😂 I am sure they love it.

  • @Ban00
    @Ban00 Месяц назад

    Aged like milk