He/She/they won't be here.Tell you what, let's talk Spring 2027
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
He/She/they won't be here.Tell you what, let's talk Spring 2027
how much did that roof cost you? I was quoted $185k (lol) last year for a roof in the panhandle.
The term disengagement is really only useful when there is a safety driver. A driverless car doesn't disengage itself, it might pull over and call for assistance but it stays in autonomous mode. Roadside assistance can manually disengage it when they arrive, that's what your spreadsheet reports . In theory a remote operator could notice an unsafe action and order the car to pull over, but that's really not how Waymo set up their system and I'm not aware of it ever happening.Really? Did you bother looking at what you linked to? 2023 data:
View attachment 1042871
Every disengagement for a driverless Waymo was for an "In-field retrieval". i.e. exactly what @2daMoon said. (No amount of remote assistance being required is reported.)
Waymo loses massive amounts of money overall, of course. They don't disclose unit economics, but looking at their utilization rate, vehicle cost and operating infrastructure I think it's pretty clear they lose money on an operating basis in Phoenix and recently-started LA. I'd guess they also lose in San Francisco, but it's a closer call.Arguably both Waymo and Tesla make money from their autonomous driving systems,
Remote monitors don't "intervene" (though I think in theory they can). They respond to requests from the car. In most cases they simply approve the car's planned action, e.g. go around a parked UPS truck. Sometimes the overrule the car. Sometimes they overrule the car and are wrong. Conegate is the most famous example, but this January a remote monitor mistakenly told a car to go through a red light. A moped also entered the intersection. The Waymo braked and avoided a collision, but the moped fell and slid.Are the Remote Operators considered "safety drivers" in that data?
If not, how are their interventions counted?
No, they have the full system. Waymo tests new areas, new code drops, etc. with safety drivers before they roll out to the driverless fleet. They put "no" in that column because that particular vehicle running those particular tests in that particular area is not approved for driverless.That report isn't for driverless Waymos... Notice the column that says "vehicle is capable of operating without a driver"? It says no for all of those. Apparently, those vehicles only have an ADAS system installed, not fully-autonomous.
No, they don't disengage when remote assistance is called. Safety drivers only disengage when needed for safety (thus the name) or when the vehicle is becoming a nuisance by blocking traffic or whatever. Or if they really need a taco.Which begs to question, if a driver was in all of the driverless rides, how often would they disengage? Probably a lot more often than the "in-field retrievals". At a minimum likely every time remote assistance is required. This is where it seems like Waymo is "cheating".
Devil's Advocate... and hear me out, but how far could Waymo (or any company) advance the solution by driving their vehicles (manually) around the country in order to collect a rough data sample from Cameras? It would be tiny in comparison (and very very late). This eventually becomes a quality vs quantity learning question to me.I wouldn't call it cheating, per se. There has been no standard definition for "disengagement" assigned for assessing this.
It could very well be that Waymo has a very narrow classification they use for this term, and, it does not include remote drivers "helping" by correcting the vehicle's path while in operation. They may call that an "intervention" rather than a disengagement. Or, some other classification of their choosing.
It makes a kind of sense for them to do it this way.
Tesla, on the other hand, apply the term "disengagement" to any time an FSD Supervisor intervenes, as well as when FSD might have to disengage on its own. When the supervisor does intervene, FSD is no longer engaged, by design. The supervisor must re-engage FSD.
If Waymo are not counting remote intervention as a "disengagement" the numbers associated with these terms cannot be compared between Waymo and Tesla.
Remote monitors don't "intervene" (though I think in theory they can). They respond to requests from the car. In most cases they simply approve the car's planned action, e.g. go around a parked UPS truck. Sometimes the overrule the car. Sometimes they overrule the car and are wrong. Conegate is the most famous example, but this January a remote monitor mistakenly told a car to go through a red light. A moped also entered the intersection. The Waymo braked and avoided a collision, but the moped fell and slid.
Agreed that as an investor of any significant amount, you should try FSD v12 firsthand (any end-to-end NN version will do). I made myself let it take over a few times during this free trial month, and was blown away. NOT that it is "robotaxi ready" right now, cause our version ain't yet, but that it is so far along that the light at the end of the tunnel is visible, and growing rapidly enough that, for the shortzes, it might well be the headlight on an oncoming freight train.Is everyone (as well as the lurkers) who do not have FSD watching every vid from Whole Mars Catalog? Well ya should! I only watch his commentary ones though, as it gives me a better understanding of v11 to now since I've never had FSD. These vids have made me bullish and allowed me to accept Elon's "balls to walls" direction. And in about two weeks I'm going to upgrade my 2018 M3 to HW3 so I can help the company gain real world data. My wife doesn't want me to spend the money, but I feel as an investor I must.
It was physically painful to rip up the couch and get into leap calls @144. Wish I had more furniture....Well, Ron Baron sure looks like a genius. He called "bottom" at the bottom.
Forward Observerhow much did that roof cost you? I was quoted $185k (lol) last year for a roof in the panhandle.
That's conviction! I debated this but it burned a couple times. Now watching one remaining call grow finally... one lol. My only leap too. So leaps might just be the trick. I'm not convinced this isn't some dream though without the car driving itself somewhere soon. But then it's clearly game over.It was physically painful to rip up the couch and get into leap calls @144. Wish I had more furniture....
I am also skillful at catching falling knifes, as I started @180. It felt meh. Doubling down at 144 felt viscerally painful, as if someone punched me in the stomach. That's my clue to double down... The palms have healed today, and look very green : )That's conviction! I debated this but it burned a couple times. Now watching one remaining call grow finally... one lol. My only leap too. So leaps might just be the trick. I'm not convinced this isn't some dream though without the car driving itself somewhere soon. But then it's clearly game over.
What took them so long I wonder? Trying to maintain earnings? Or just a lack of H100 Supply? Or Dojo delays, who knows.2. Elon said they spent $1B on compute in Q1 and they expect to spend $10B this year.
There are numerous types of risk for which loss severity and loss frequency are directly correlated. Examples include most classes of storm risk, where high frequency and high severity are directly correlated. hence, just try to buy storm risk in South Florida.I was unaware that loss severity statistics for automated systems were higher. That would be interesting to learn more about.
Would there be a balance point where the excess of costs due to severity could be outweighed by the reduced frequency of less severe incidents?
Explained in another post. it is not that accident severity will go up. NOT! it is that when an accident happens everyone involved wants to sue the deepest pockets. That means loss severity increase even while accident severity decrease.Why would FSD cause loss severity go up for car crashes? I don't understand that logic at all.
Yeah, one thing I've learned about Tesla is that you can't be scared of the falling knife. You have to keep buying on the way down because there is never much time to buy on the way up. It just happens so fast!I am also skillful at catching falling knifes,
Capex doesn't directly affect earnings, of course. Lack of compute supply is likely a factor, but I think they have seen something in the progress of the FSD model that gives them the confidence to floor it. I know how much better current version is and can only imagine where they have come in the alpha ver.What took them so long I wonder? Trying to maintain earnings? Or just a lack of H100 Supply? Or Dojo delays, who knows.
And who beat them to it, Meta?
OK, I see your point about suing someone with deep pockets.Explained in another post. it is not that accident severity will go up. NOT! it is that when an accident happens everyone involved wants to sue the deepest pockets. That means loss severity increase even while accident severity decrease.
In other words, the rarer the accident is the higher the claim when it does. Think Boeing 737Max, Exxon Valdez etc. This is not arcane, but raw economic reality when a rare accident actually happens.