this post was submitted on 14 Feb 2024
481 points (98.6% liked)
Technology
59589 readers
3148 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You can't be driving behind that vehicles at 60mph with 2.5s WITHOUT knowing it's trajectory.
You keep trying to saying it doesn't need to know the trajectory of all objects around it, but that's not true.
Yes you can. It is a stopping distance. 2.5 seconds at 60 mph is 220 feet. A car can brake from 60 to 0 in less than 220 feet. It will take longer than 2.5 seconds to do, but it won't hit the object which originally was 2.5 seconds ahead.
Maybe a straight behind isn't as good an example, although it is calculating the likelihood of it continuing to go straight.
An oncoming car, drifting out of the lane towards your lane.
It's not going to hit you until it's in your path, but the trajectory of it coming towards you is in your path.
If you don't consider where it's going and how fast it's going, you won't know if it's going to enter your lane before you pass it.
If you're only trying to avoid hitting objects and its not in your path until the last quarter second, you won't take appropriate actions because you don't know it's coming at you.
All these measurements are taken as time between you and them and it uses that info to calculate the trajectories.
Yes I know and it should. What I am saying is that the trajectory calculations should never be allowed to override the basic collision calculations, like it did in this case.
It does not matter if the towed truck appeared to have a different trajectory than it actually had, because it was very obviously in the range of collision.
Do you have a reverse sensor in your car that beeps when you're close to stuff?
It was the self driving car that drove into the tow truck. All it's sensors must've been beeping, and it still decided to keep driving.