Debugging a Behavior
You have created a Behavior . It is not yet operational.
Here is how you can fix the bugs.
To test a Behavior :
Make sure the Autonomous Life is off.
If not, click the Turn autonomous life off button.
||Click the Play button.|
If your Behavior runs well, see: Debugging an Activity .
Otherwise, try the following tips and tricks:
Flow diagrams ¶
Testing the boxes one by one ¶
To control a Behavior :
||Click the Play button to load it on the robot.|
||Double-click on an input or output to stimulate it.|
Following the flow execution ¶
Each time a link between 2 boxes is simulated, the color of the link changes. It is a good way to check the execution.
Checking the output value ¶
When a box has a value as output:
The value is displayed, for a short time, near the output.
The value is displayed in black if only one value arrives, or in red if several values arrives.
The last value is displayed in the Tooltip of the output.
Understand why a box becomes red ¶
It becomes red during the execution:
An exception raised. It can be because a module cannot be loaded (virtual robot), does not exist, etc.
It becomes red before the execution (just after clicking the Play button):
The box code contains an error. It can be a typing problem in a Python script.
Muting a layer ¶
The small eye next to each layer allows you to “mute” a layer: it will be ignored when the Behavior is played.
This can be useful when you want to debug your Behavior .
Python scripts ¶
Using self.logger ¶
self.logger is standard Python logger created with the Python module Logging.
The log information can be categorized by level of severity (each level has its associated font color in the debug window):
- debug (grey)
- info (black)
- warning (orange)
- error (red)
- critical (purple)
In your Python script, we recommend you to add warning, error and critical logs to inform when you Behavior dangerous or erroneous state.
You can also use info and debug to trace execution flow of your Behavior .
||Open the script of a box.|
Add the self.logger line in a function as below:
||In the Debug window, select the minimum level of information you want, Debug in our case.|
||Execute the box.|
All debug message display in the debug window to let you understand what is going on. The potential debug, info, warning, error and critical messages of other functions also display as the minimum level asked is debug.
If you choose error, you see only error and critical messages.