Difference between revisions of "MRT: Development of a multi-purpose debugger for MRT-based robots"

From AIRWiki
Jump to: navigation, search
(Dates)
(Project short description)
Line 6: Line 6:
 
The software should be able to track down all the messages normally exchanged between MRT-based robots as well as debug ones. Since the Tool's main goal is to provide a simple, yet powerful, GUI to the every MRT robot/module developer, everything should be implemented as much module/robot/purpose independent as possible.
 
The software should be able to track down all the messages normally exchanged between MRT-based robots as well as debug ones. Since the Tool's main goal is to provide a simple, yet powerful, GUI to the every MRT robot/module developer, everything should be implemented as much module/robot/purpose independent as possible.
  
Mandatory parts of the debugger are the following (updated as needed):
+
Key features of the debugger are the following:
* Real time and Simulation mode (with time shifting)
+
* Modes: Real time, Replay, Record
 
* Robot/Team 2D spatial position tracking
 
* Robot/Team 2D spatial position tracking
* Message log
+
* Robot orientation tracking
* Currently active fuzzy rules highlighting
+
* Perceptions debugging
 +
* Behaviours debugging
 
* Customizable GUI
 
* Customizable GUI
* Software extendibility (ability to add new MRT modules and such)
+
* Easy extendibility
 
   
 
   
 
The project deadline, ideally, should be enough weeks before the 2009 Robocup competition in order to have a working debugger for the Robocup Team.
 
The project deadline, ideally, should be enough weeks before the 2009 Robocup competition in order to have a working debugger for the Robocup Team.

Revision as of 13:30, 21 July 2009

Project name

MRT: Development of a multi-purpose debugger for MRT-based robots.

Project short description

The goal of this project is to develop a multi-purpose highly customizable robotics team debugger, the "Monitor". The software should be able to track down all the messages normally exchanged between MRT-based robots as well as debug ones. Since the Tool's main goal is to provide a simple, yet powerful, GUI to the every MRT robot/module developer, everything should be implemented as much module/robot/purpose independent as possible.

Key features of the debugger are the following:

  • Modes: Real time, Replay, Record
  • Robot/Team 2D spatial position tracking
  • Robot orientation tracking
  • Perceptions debugging
  • Behaviours debugging
  • Customizable GUI
  • Easy extendibility

The project deadline, ideally, should be enough weeks before the 2009 Robocup competition in order to have a working debugger for the Robocup Team.

Dates

Start date: 2008/10

End date: 2009/07

People involved

Project head(s)
  • A. Bonarini - [[User:AndreaBonarini]
  • M. Restelli
Other Politecnico di Milano people
Students currently working on the project

Laboratory work and risk analysis

Laboratory work for this project will be probably performed at both AIRLab/Lambrate and AIRLab/Bovisa. It will include significant amounts of testing on real robots. Potentially risky activities are the following:

  • Transportation of heavy loads (e.g. robots). Standard safety measures described in Safety norms will be followed.
  • Robot testing. Standard safety measures described in Safety norms will be followed.