-
Notifications
You must be signed in to change notification settings - Fork 3
3.3.3 Debugging mode
Debugging mode can be started by running the test script with the following command:
- ./run.py -t
This will run all of the generation scripts without launching ros, the world or the robots. This allows for each robot to be run individually using the Run_Robot.py scripts. These scripts include the debugger functionality, allowing you to enter commands specified in the debugger class at command line, assisting in the easy of testing.
The debugger class is an object added in each robot run script. This object starts a new thread on initialisation. This thread listens for input, executing the corresponding command in the debugger class. With this functionality, robot state can easily be inspected at certain points of the run time, and robot state can be altered to test certain functionality.
The following commands are available at present:
- ps - Prints the current action stack to the terminal.
- stop - Prints whether the stopCurrentAction variable has been set.
- unload - Set's the pickers/carriers current load to 0.
- load - Set's the pickers/carriers current load to 100.
- pickers - Prints the array of picker positions.
- state - Prints the current state of the entity.
Pictured below is an example of the use of the debugger from terminal. After the robot has been started using it's respective run script, the 'ps' command is entered through the terminal. The current action stack of the running robot is then printed to terminal.
##1.0 Introduction
##2.0 User Manual
##2.5 Testing
3.1 Launch Infrastructure
3.2 Entities and behaviours (Robots, humans, animals)
- 3.2.1 Entity Superclass
- 3.2.1.1 Entity Movement
- 3.2.2 Robot Entity
- 3.2.2.1 Robot Entity Detection
- 3.2.2.2 Robot Path Finding
- 3.2.3 Robot Pickers
- 3.2.4 Robot Carriers
- 3.2.4.1 Carrier Queue
- 3.2.5 Humans
- 3.2.6 Animals
- 3.2.7 Entity Topics
3.3 Special services and features
##4.0 Project Planning and management
- 4.1 Project plan
- 4.2 Git Branching and Merging Etiquette
- 4.3 Design Requirements, System requirements and Technical specifications
- 4.4 Key Factors and Constraints
- 4.5 System Design
- 4.6 Time spent
- 4.7 Testing and integration overview
- 4.8 Meeting minutes
##Miscellaneous resources