Hello,
I would see state machines and behavior trees as typical examples for such design patterns, yes.
The reason why there isn't a standard is probably the lack of standardization in robotics.
What is a reasonable approach with software X may be completely different in software Y - e.g. the geometry-heavy, visual programming based approach of Grasshopper versus how ROS is used.
Same applies to robot brand X versus robot brand Y.
So unfortunately I cannot offer any good advice here...!
Best,
Johannes
I would see state machines and behavior trees as typical examples for such design patterns, yes.
The reason why there isn't a standard is probably the lack of standardization in robotics.
What is a reasonable approach with software X may be completely different in software Y - e.g. the geometry-heavy, visual programming based approach of Grasshopper versus how ROS is used.
Same applies to robot brand X versus robot brand Y.
So unfortunately I cannot offer any good advice here...!
Best,
Johannes