I don't think anyone is saying that the currently "should" work correctly
Dave has said exactly that a bunch of times...some example quotes from him earlier in this thread-
"40.50.7 still unnecessarily brakes for cross traffic"
" just pointing to the user manual that says "oh, that might happen" is not a good excuse for the system's behavior."
"I have to wonder when these guys will give up defending bad software?"
" Just because it operates a particular way now, doesn't mean that I accept it "
He clearly keeps thinking the
system is doing something wrong, when it's obvious to everyone else it's the
driver doing something not only wrong, but explicitly contradicted by the owners manual.
He even goes so far as to insist just because the owners manual told him it's not meant to work that way is "no excuse" for it... not working that way...just like the manual told him....
We get that Tesla says that the systems as designed have not been programmed to handle most of the situations involved on city streets.
Well, everyone but Dave anyway...
If you say that it is just a coincidence, then I will maintain that it is not. And again, unless you are a Tesla programmer, you don't know what they have baked in for reactions, despite what a hacker might think is happening.
I'm not talking about what a hacker "thinks" is happening.
I've talked about what one
has shown us is happening.
Including raw feeds of what the AP computer is seeing and doing.
Hence his
explicit advice to
not use it outside of freeways because it does not have code to handle those situations
One example: I have taken a certain two-lane road that widens to include a left turn lane (no right allowed). A few updates ago, the car would struggle to determine what to do as the middle yellow line curved left while the white shoulder line stayed straight. It handled it, but with a little zig. As of at least the last update, it handles it as best as I would. I've tried it at different speeds and traffic conditions.
That's the system simply being better at handling where to go when a lane widens.... same as happens on many freeways when a lane widens to add in a new lane... and as you'd expect many used to report that was handled poorly on freeways, and a recent update greatly improved it.
The fact it does the same thing when a lane widens (to add a new lane) outside freeways isn't surprising- but it's clearly NOT indicating they've added "understanding local turn lanes"
I maintain that while the disclaimer will not change until Tesla is willing to say that they are now officially covering those situations, we don't know what is being baked into AP or TACC.
Not every line of code certainly- but we do have direct observation of what it does in such situations thanks to folks with access to the AP computer who publish the data.
It shows what things it recognizes, what it labels them as, what places it considers "driveable", projected paths, etc...
It does not support your thinking on this stuff that there's anything doing anything active in the code today for city driving... though there's certainly code to RECOGNIZE some things that'll be relevant when they roll out some "actually does something" code... like lights, stop lines, etc...
This could be for a different thread, but I have been thinking about what they could implement to start. Certainly start/stop at stop lights while going straight.
That is probably the "easiest" but based on current level of correct reading/detection of lights they're not there yet.
Especially as this is one of those "get it wrong once and people can die pretty easily" kinda things.
In fact Green posted just yesterday after having upgraded his own system to HW3 that the current code doesn't appear to be any better TODAY than it was back in March 2019 running on HW2 at correctly IDing what color a light is.... (that is, it often gets it right, but not NEARLY close enough to 100% you'd want to trust it to actually take actions)