The title implies that there are collision check systems that don’t use point clouds (or that robotics has moved onto something else)? Is that true or did the author just mean personally?
Posts like these really highlight how much there to think about in robotics. Below the surface of what immediately comes to mind there is just an abundance of topics to address to get an actually well working robot.
Yep. And when you get to an actual robot, you find it’s a distributed system with all the attendant challenges, so you build yourself up for that, and then your time, attention, and maybe your soul are crushed by connectors, cables and batteries.
So naturally the funnest work is multi-robot systems…
The title implies that there are collision check systems that don’t use point clouds (or that robotics has moved onto something else)? Is that true or did the author just mean personally?
I think they meant it in the sense of coming back to the topic yet again after talking about it fairly exhaustively in an earlier blog post.
Why don’t they marry the visual categorisation of objects with a sparse predefined model to simplify?
Point clouds seem like a noisy layer to use and better as verification.
Posts like these really highlight how much there to think about in robotics. Below the surface of what immediately comes to mind there is just an abundance of topics to address to get an actually well working robot.
Yep. And when you get to an actual robot, you find it’s a distributed system with all the attendant challenges, so you build yourself up for that, and then your time, attention, and maybe your soul are crushed by connectors, cables and batteries.
So naturally the funnest work is multi-robot systems…
This reminds me of writing physics in game engines.