Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| doc:logging:beliefstate [2014/02/18 12:47] – created winkler | doc:logging:beliefstate [2015/04/22 07:10] (current) – [Running the belief state software] bbrieber | ||
|---|---|---|---|
| Line 48: | Line 48: | ||
| In order to install the belief state logging software, you need the following entries in your '' | In order to install the belief state logging software, you need the following entries in your '' | ||
| < | < | ||
| - | - git: {local-name: | + | - git: {local-name: | 
| - git: {local-name: | - git: {local-name: | ||
| - git: {local-name: | - git: {local-name: | ||
| Line 56: | Line 56: | ||
| < | < | ||
| - git: {local-name: | - git: {local-name: | ||
| + | - git: {local-name: | ||
| - git: {local-name: | - git: {local-name: | ||
| + | </ | ||
| + | |||
| + | For compiling the package beliefstate with catkin you need the package libconfig++8-dev installed. | ||
| + | < | ||
| + | sudo apt-get install libconfig++8-dev | ||
| </ | </ | ||
| ===== Running the belief state software ===== | ===== Running the belief state software ===== | ||
| - | TODO | + | When installed and compiled through '' | 
| + | <code bash> | ||
| + | $ rosrun semrec semrec | ||
| + | </ | ||
| + | The software automatically looks for plugins in your '' | ||
| + | So, pratically, you don't need to configure anything. If you want a configuration different from the default one, look into the file '' | ||
| + | Log files are by default saved into the directory structure in '' | ||
| + | |||
| + | Typical startup messages look like this: | ||
| + | < | ||
| + | [ core ] Starting beliefstate system. | ||
| + | [ plugin-instance ] Loaded plugin ' | ||
| + | [ plugin-instance ] Initialized plugin ' | ||
| + | [ plugin-instance ] Loaded plugin ' | ||
| + | [ros/1] Starting ROS node ' | ||
| + | [ros/1] ROS node started. Starting to spin (4 threads). | ||
| + | [ plugin-instance ] Initialized plugin ' | ||
| + | [ plugin-instance ] Loaded plugin ' | ||
| + | [ plugin-instance ] Initialized plugin ' | ||
| + | [ plugin-instance ] Loaded plugin ' | ||
| + | [ plugin-instance ] Initialized plugin ' | ||
| + | [ plugin-instance ] Loaded plugin ' | ||
| + | [ plugin-instance ] Initialized plugin ' | ||
| + | [ plugin-instance ] Loaded plugin ' | ||
| + | [ plugin-instance ] Initialized plugin ' | ||
| + | [ plugin-instance ] Loaded plugin ' | ||
| + | [ plugins ] Not loading development plugin: ' | ||
| + | [ plugin-instance ] Unloaded plugin ' | ||
| + | [ plugins ] Failed to load plugin ' | ||
| + | [ plugin-instance ] Loaded plugin ' | ||
| + | [ plugin-instance ] Initialized plugin ' | ||
| + | [ plugin-instance ] Loaded plugin ' | ||
| + | [ plugins ] Not loading development plugin: ' | ||
| + | [ plugin-instance ] Unloaded plugin ' | ||
| + | [ plugins ] Failed to load plugin ' | ||
| + | [ plugin-instance ] Loaded plugin ' | ||
| + | [ plugin-instance ] Initialized plugin ' | ||
| + | [supervisor/ | ||
| + | [supervisor/ | ||
| + | </ | ||
| + | |||
| + | Messages like '' | ||
| + | |||
| + | After startup, the '' | ||
| ===== Running the belief state CRAM interface ===== | ===== Running the belief state CRAM interface ===== | ||
| - | TODO | + | In order to get log support in your CRAM applications, | 
| + | |||
| + | To set metadata about the plan you are executing (to correctly identify your experiment), | ||
| + | <code lisp> | ||
| + | > (beliefstate: | ||
| + | :robot "My robot' | ||
| + | :creator "The experimenter" | ||
| + | :experiment "Pick and Place" | ||
| + | : | ||
| + | </ | ||
| + | The data is then sent to the belief state software and will be extracted as '' | ||
| + | |||
| + | If you want to extract the current state of the experiment (after collecting experiment data from plan execution), do this: | ||
| + | <code lisp> | ||
| + | > (beliefstate: | ||
| + | </ | ||
| + | This effectively extracts the collected information into files preceeded with '' | ||
| + | |||
| + | ===== Capabilities ===== | ||
| + | The belief state logging software itself has no abilities itself except for message transportation and plugin loading. The capabilities available for logging are introduced by plugins, described in more detail [[doc: | ||
| + | |||
| + | ===== Tutorials ===== | ||
| + | In order to interface with the logging infrastructure, | ||
| + | |||
| + | * [[doc: | ||

 
 
 

 
