AlanSubie4Life
Efficiency Obsessed Member
The plot thickens. I’d like to restrict the bet to just this left turn (not the other UPL which it has no problem with typically anyway). Haha.
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.
I guess I’ll see you in the Delaware Court of Chancery with the way you’re trying to alter the deal.The plot thickens. I’d like to restrict the bet to just this left turn (not the other UPL which it has no problem with typically anyway). Haha.
I think I am reasonably safe on this one as he seems to limit the videos to one turn recently. But ok, I see you are not confident. Can keep that part of the deal as is.I guess I’ll see you in the Delaware Court of Chancery with the way you’re trying to alter the deal.
If you subtract 200 posts about a .75 cent beer bet with 50 rules of compliance analytics It’s not that bad.This thread is 2 months and one week old, with 34 pages.
That has to be a record of some kind, especially seeing that there is a chance that there will never be a 10.13 release.
This is San Diego. $8 at the craft breweries. Now you understand how serious this is.If you subtract 200 posts about a .75 cent beer bet with 50 rules of compliance analytics It’s not that bad.
Yeah, with all the specific rule categories for compliance you should have negotiated that detail. My bet is that you are playing for a PBR or Old Style can. LolThis is San Diego. $8 at the craft breweries. Now you understand how serious this is.
We could let the general audience here vote who wins the bet, that would be a more balanced subjective decision.Yeah, with all the specific rule categories for compliance you should have negotiated that detail. My bet is that you are playing for a PBR or Old Style can. Lol
In addition to the exorbitant cost of the beer, you have to remember this will literally be the first time on TMC when someone admits they were wrong about their FSD prediction.If you subtract 200 posts about a .75 cent beer bet with 50 rules of compliance analytics It’s not that bad.
P.S. There will be a picture of the beer.My bet is that you are playing for a PBR or Old Style can. Lol
unless unless you are at Petco, that $8 beer is $16This is San Diego. $8 at the craft breweries. Now you understand how serious this is.
The word "see" is not specific enough. Being able to detect that something is present isn't enough to say it "sees" something. It has to be able to calculate its velocity as well. If it can detect the object's velocity within reasonable error bars, as well as detect it, then I would say it could "see" the object. We don't have data on the velocity information as far as I can tell.Looking good for me: it appears to be requiring a gap in excess of 6-7 seconds at the moment. This shows the importance of that metric! On the upside, it also implies that the car can see about 150m or more (assuming 50mph).
It was actually a ten second gap it didn't take (32s-42s) which is actually larger than the gap it did take (1:02-1:09).Looking good for me: it appears to be requiring a gap in excess of 6-7 seconds at the moment. This shows the importance of that metric! On the upside, it also implies that the car can see about 150m or more (assuming 50mph).
Necessary but not sufficient is how I would describe it I guess. I was only addressing what appeared to be its ability to detect that a vehicle was present. It looks like it waits for there to be no vehicles to be detected within >150m, regardless of velocity. This range may depend on assumptions about the speeds on the road.The word "see" is not specific enough. Being able to detect that something is present isn't enough to say it "sees" something. It has to be able to calculate its velocity as well. If it can detect the object's velocity within reasonable error bars, as well as detect it, then I would say it could "see" the object. We don't have data on the velocity information as far as I can tell.
With a single test, you cannot conclude how far the car can see by the time gap when it entered the intersection. It's possible that the car cannot see that far and assumed there was nothing coming.Looking good for me: it appears to be requiring a gap in excess of 6-7 seconds at the moment. This shows the importance of that metric! On the upside, it also implies that the car can see about 150m or more (assuming 50mph).
Yes, I was just looking for theminimum value that I noticed was missed. And that larger gap was right after getting to appropriate pose, so gave it a pass.It was actually a ten second gap it didn't take (32s-42s) which is actually larger than the gap it did take (1:02-1:09).
The advantage that FSD has on this turn is that people behind you can't see if the path is clear and honk at you.
Of course not, that would imply a different problem.Had there been no cars for 60 seconds, you could hardly conclude that the car can see nearly a mile away.
Yes, it was my assumption that the car would not sit at the turn for no reason. That is possible of course. The distance estimates were made with that underlying assumption, anyway.It's possible that the car cannot see that far and assumed there was nothing coming.