Him saying this always puts me off. Gives hard old sales-guy vibes. I really wonder who/which demographic is influenced in nvidias favor by this rethoric.
Have you tried reducing the register count in your FP32 FMA test by increasing the iteration count and reducing the number of values computed per loop?
Instead of computing 8 independent values, compute one with 8x more iterations:
for (int i = 0; i < count * 8; i++) {
v0 += acc * v0;
}
That plus inlining the iteration count so the compiler can unroll the loop might help get closer to SOL.
This happens to me just using the adaptive cruise control, no Autopilot or FSD enabled and it's super annoying. Can happen on a completely empty road driving in a straight line.
That's... appalling. My 2019 Leaf has absolutely zero problems maintaining distance with adaptive cruise control, using the ancient technology formerly known as radar. It can somehow even see stationary vehicles, something I thought wasn't feasible.
>It can somehow even see stationary vehicles, something I thought wasn't feasible.
Radar seeing stationary objects is trivial, it sees them just like it sees any other. The trick is seeing only the stationary objects which are actually relevant; e.g. not seeing a street sign suspended above the road, or a tree next to the road, but only the stationary objects in the path of the car. The radar configuration that Tesla use[s/d] apparently has awful angular resolution, making this differentiation difficult if not impossible. But this isn't inherent to all radar technology; some radars can have good angular resolution. For instance with SAR or ISAR, you can produce high resolution 2d images. But I don't know what kind of radar systems your Leaf has.
Doesn't it also have to handle things like windy roads and steep angle changes when going uphill? it seems you need both vision and radar to confirm things, eg:
- when on level ground approaching a steep hill, the radar might not know if the object directly in front of the car is just a continuation of the road or not
- when approaching a sharp curve in the road, is the object directly in front of the car actually in its path, or is it just on the side of the road
Are you sure about stationary? My 2018 leaf does not do that. I replaced the system with Open Pilot and never looked back. I also have a Tesla Model Y sometimes for testing. It is amazing how much better OpenPilot is. On the highway it is unbeatable and also able to recognize stationary objects like cars and motorbikes.
My Hyundai doesn’t seem to recognize stationary objects though. Also, the seconds after a car has merged into my lane in front of me are scary - my car doesn’t immediately recognize the new situation.
My 2019 Subaru Crosstrek has adaptive cruise control, and i've had it hit the brakes pretty hard when there's nothing in the way. Luckily it doesn't happen often.
I have a 2021 one and it never hit the breaks with nothing standing in the way. I don't have the manual in front of me but IIRC, it should only activate without an actual obstacle if the circumstances are such that something may be confused for an obstacle (e.g., driving down a steep enough hill that the end of it may be detected as a wall, never happened to me but I've never done more than 25 deg slopes).
I know you're not asking for advise but I'd recommend to have that checked, my recollection is that the manual spends far more pages listing the circumstances under which the system may fail to apply the brakes than those in which it may break when it didn't have to, so it seems odd enough for me that I'd get that checked if it happened to me.
I've never had this happen on my 2017 Forester either in ~30,000 miles of highway driving with the adaptive cruise (the Subaru system is fully vision-based with no radar).
The one issue I've noticed is that it sometimes hits the brakes for cars that are obviously exiting the highway because a tiny sliver of the car is still technically in the driving lane, so I've learned to keep my foot over the gas pedal to override it in that case. The amount of braking isn't scary though, it's just annoying because there's no need to slow down at all.
I have a 2021 Subaru Legacy and I've never had the phantom breaking as well. I've put about 10k miles on the car with at least 7k of it being on adaptive cruise. All of the miles have been on country roads with hills, sharp turns, traffic, inclement weather, etc.
My Outback has never done it in over 20k miles, but a prior Chrysler vehicle warned but seemed to correct itself before engaging the brakes when going around a curve on many occasions.
Sadly, Subarus don't make headlines though. A Tesla does just about anything and it's local news and Facebook fodder. I don't get people texting me about typical ICE cars on fire after accidents ~ for some reason people think Tesla's are noteworthy in that regard? Like other cars don't have sketchy LKAS/cruise control systems or crash?
>> My 2019 Subaru Crosstrek has adaptive cruise control, and i've had it hit the brakes pretty hard when there's nothing in the way. Luckily it doesn't happen often.
> Sadly, Subarus don't make headlines though. A Tesla does just about anything and it's local news and Facebook fodder.
Why sadly? Subaru hasn't been loudly making empty promises about self-driving capability and hasn't been aggressively pushing not-fully-cooked self-driving software onto the road.
I think people should know that EVs come with the same risks as ICE cars. It's old news that ICE cars catch on fire. They've been around 100+ years in one form or another, why would we report on it? I mean there's a tank full of volatile fuel in the car.
EVs are new still. They're hyped and covered like crazy by the media in a lot of positive ways, so why should they not get equal press coverage when there is negative news? Once EVs hit a certain mass, they won't be novel anymore, and nobody will care.
More anecdata: In over three years my Volvo has never phantom braked to the best of my knowledge. ACC is far and away my favorite and most used Pilot Assist feature too.
They are referring to the GPU part of the chip. There are two separate GPU complexes on the die but from the software point of view, it is a single large GPU.
Vega 20 seems to also refer to a discrete GPU. This has been later rebranded to Radeon VII (maybe because of this confusion). The number you are quoting is for the discrete GPU.
Same with 10 LOL. VEGA10 codename is for the original Vega Frontier Edition/RX Vega 56/RX Vega 64. But now there's also "Vega 10" used as a description for the 10 Vega compute units on Ryzen APUs.
The handling of bookmarks is terrible in the latest Firefox. So bad that I can only assume the developers don't actually use bookmarks and just search for websites by name?
