Changes between Version 38 and Version 39 of Old/Robot/robothandbook
- Timestamp:
- Aug 31, 2007, 5:51:38 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Old/Robot/robothandbook
v38 v39 12 12 * [wiki:robothandbook#C C++] 13 13 * [wiki:robothandbook#TrilaterationClassesacleanercversionofV3 Trilateration Classes] 14 * Behaviors14 * [wiki:Behaviors Behaviors] 15 15 16 16 * [wiki:robothandbook#UsingtheGrid Using the Grid] … … 40 40 41 41 The program will cause the robot to wander around the room and create a map using its camera. Much more information on navtool is in the Getting Started Guide. 42 43 The script that starts the server (run_slam_explore) is essentially a shell script which runs the command: 44 {{{ 45 behave /opt/evolution_robotics-3.1.3004-20060627030002/behavior_networks/slam_explore.xml 46 }}} 47 48 Theoretically, modifying the behavior network slam_explore.xml (using composer.sh) will modify the behavior of the navtool GUI application. 49 42 50 43 51 == Calibration == … … 195 203 }}} 196 204 197 198 199 200 201 202 203 204 205 205 = Behaviors = 206 207 Behaviors are xml files which control the robot. There are two types of xml files to consider: behavior networks and behavior schemes. 208 209 Behavior networks are completed behavior definitions. They are edited using the behavior composer, which is a java program that can be started using this command 210 {{{ 211 $ composer.sh 212 }}} 213 214 The behavior composer is a drag-and-drop interface which allows for easy manipulation of behaviors networks. 215 216 Behavior schemes are the building blocks of a behavior network. Behavior schemes must be located in one of the following directories: 217 {{{ 218 /opt/evolution_robotics/config/behaviors 219 /home/vamsi/samples/config/behaviors 220 }}} 221 (Note: Both of these are subdirectories of evolution's config directories. You can see which config directories are defined using $ echo $EVOLUTION_CONFIG)