Actually 3D bounding box might be the most important thing in object detection. A 2d bounding box (which includes shapes) doesn't include important information which you need. For example the precise orientation of a car, with that you can predict its actions. This is
That's debatable. Cars have this tendency of backing out too, and then have you never seen cars moving sideways?
vital in a dense environment, during parking, in a parking lot. Is this car trying to pull out or not. What precise direction is he pulling to, With just the information necessary to produce 2d bounding box, you don't see it. But the information is reflected in the information necessary to produce a 3d bounding box. Information like, is this the left side of a car, the door might pop out, is the door currently open? is this car trying to complete a turn.
You might have noticed different colors at edges of driving spaces around objects. They seem to mean different things (1 color per different value, but we do not know what the values mean. perhaps some means "this is a car front/side/whatever"?)
is this car coming at me or... the list goes on. As Mobileye Amon says. 2d bounding box is irrelevant.
2d bouding box might just be a debug aid for a different team for al we know and not used by the actual driving algorithm that uses interpreted data in the drivable space, though? That's why I say 3D bounding box while neat eyecandy, might have the same data expressed in other ways.
There's radar return to tell you things and then of course there's relative speed.
While its impressive that distances and speed are done by visual. Mobileye has been doing this since eyeq3. There's no tangible difference between atleast the firmware you have unraveled versus what eyeq3 has been doing since 2014 production date.
There is a huge difference on hilly roads. HUGE. Also I have no way of extracting data like this from eyeq3
I'm just laying out that the lack of 3d boxes and the instability of the detection shows their weakness compared to mobileye.
Well, instability is definitely there, no argument about it.
3d bounding box whether you are using lider or camera gives you the precise orientation of an object with which you can deduce its precise moment to moment decision. This is very important in dense traffic or parking lot.
Imagine if you painted inside of the 2d boxes with solid color and then look at it in the perspective as a human. Notice how you lose all indication of what's going on in the scene, only that there are objects in front of you but no idea the scenario, orientation or state they are in.
oh wait, you already did that.
Like I said in the comment, more information is availble, just did not want to update the old tool. there's still speed and direction and lane and overlap information and all that.
Notice how you don't know if the car infront of you is turning and where they are turning to or not. Or even if they are going the same direction as you. you're basically driving blind.
The relative speed tells us if it's going in the same direction or not. Other ways to tell if the car is turning, like it stays withing turning lane bounding lines?
This is even now more evident when you are driving on dense surface streets. A car could be in-front of you at a intersection in the adjacent turning lane, preparing to turn into the parallel lane next to you. With a 2d bounding box info, you won't know if that car is driving forward parallel to you or driving forward adjacent to you or making a turn.
Just forget about the 2D bounding box, ok? Let's assume all the really useful info is reflected via the driving space border around the obstacle.
Ask yourself, can you drive in dense traffic with the above view superimposed to your view? Answer is absolutely not. You need to know the orientation of cars.
Nah, not really. I need to know the direction of their movement, though.
If only driving were just about not hitting things and not prediction, knowing and planning around the actions or perceived actions of another driver.
There's little indication any such planning is actually going on in this mostly current firmware, though, so this point is kind of moot.
