The essential features of mock robot include :
- Battery
- LED Strip
- Docking Action Server
- Move Base Action Server
- Rotation Action Server
- Safety Sensors Pipeline
Behaviour - collect data data from a subscriber and stores result on blackboard Data Gatherers assemble under the parallel at or near the very root of the tree so they may always trigger their update() ad be processed before any decision making behaviours elsewhere in the tree
<node pkg="py_trees_ros" name="tree" type="tutorial_tree" args="one"/>
We cant simply change the topic name of /battery/state to get a topic ont he blackboard!
Tasks divided :
- Custom board implementation with blackboard
- Custom Action Server to rotate turtlesim
- Put pose to blackboard
- Use bt for actionclient to rotate turtlesim by 90 degrees
Sites I referred to implement this:
- https://github.com/splintered-reality/py_trees_ros/tree/release/0.5.x
- https://github.com/splintered-reality/py_trees_ros/tree/release/0.5.x/scripts
- https://github.com/splintered-reality/py_trees_msgs
- https://github.com/splintered-reality/py_trees_ros/blob/release/0.5.x/py_trees_ros/tutorials/five.py
- http://docs.ros.org/en/melodic/api/py_trees_ros/html/tutorials.html#module-py_trees_ros.tutorials.five
- http://docs.ros.org/en/melodic/api/py_trees_ros/html/terminology.html#term-guard