You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It sounds like a big task but it's not that bad. As long as you understand how a state machine works, you can write your own and add a bunch of features like time-out. Smach is solid but way too simple and limiting. The State Machine could be a class; the states and transitions could be a dict or smt; and adding a new feature would mean just adding a new method, which is sick. Great task for a few new members to plan and design smt together - just make sure it is well designed because everything else in planner depends on it
The text was updated successfully, but these errors were encountered:
Look into our current state machine setup for each mission and understand what is going on (maybe do a state diagram drawing for the individual missions too) catkin_ws/src/planner/src/missions.py
Look into smach and smach alternatives (talk to William about this too). Identify which features are good and which features would be nice to add...
Plan out our own state machine implementation --> review this with everyone
Implement state machine!!! Beware of ROS1/2 syntax and the ongoing conversion
Make sure planner doesn't die with out own state machine
It sounds like a big task but it's not that bad. As long as you understand how a state machine works, you can write your own and add a bunch of features like time-out. Smach is solid but way too simple and limiting. The State Machine could be a class; the states and transitions could be a dict or smt; and adding a new feature would mean just adding a new method, which is sick. Great task for a few new members to plan and design smt together - just make sure it is well designed because everything else in planner depends on it
The text was updated successfully, but these errors were encountered: