6 Comments
User's avatar
Shravan Gulvadi's avatar

Loved this post, thanks a lot for writing it!

Expand full comment
Onur's avatar

Wish I know this before my robotic master. It was pain in the ass to learn every part of this blog post by experience... Thank you for the post.

Expand full comment
Alejandro's avatar

The logging looks kinda awesome. Maybe you could do some implementation examples in a future post!

Expand full comment
Benjie Holson's avatar

Not sure if you saw this, but the logging implementation is open source here: https://github.com/robobenjie/methodlogger/tree/main. Is that what you are asking?

Expand full comment
Alejandro's avatar

yes! That may come handy. thank you

Expand full comment
User's avatar
Comment deleted
Mar 22, 2023
Comment deleted
Expand full comment
Benjie Holson's avatar

This high level logic is unlikely to run on an embedded board, though code is code you can run it anywhere you want, as long as you have cycles. Most robot I've worked on had a lower level "embedded" layer that did things like realtime motor control and a beefier computer for computationally expensive things like ML, planning and collision checking, and app code usually runs on that machine. I've never worked at a company that uses Ros2 (I believe it was created after we picked the tech stack for Everyday Robots) but I think it's a common choice for robotics companies.

Expand full comment