1 / 19

Welcome to our presentation

Aibo field localisation ( http://www.science.uva.nl/~baslamet ) Woiyl Hammoumi Vladimir Nedovic Bayu Slamet Roberto Valenti February 4 th , 2005. Welcome to our presentation. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems

kris
Download Presentation

Welcome to our presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Aibo field localisation (http://www.science.uva.nl/~baslamet) Woiyl Hammoumi Vladimir Nedovic Bayu Slamet Roberto Valenti February 4th, 2005 Welcome to our presentation

  2. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future International robot soccer World Championship July 2005 - Osaka ‘By the year 2050, develop a team of fully autonomous humanoid robots that can win against the human world soccer champion team’ Teams have to publish their code after each RoboCup RoboCup

  3. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Played with Aibo’s 4 vs 4: Goalie Defensive supporter Offensive supporter Striker The Dutch Aibo Team Joint effort of various Dutch universities First participated in 2004 Aims for victory in 2005 4-Legged League

  4. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Code Overview

  5. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Increasingly natural soccer playing Changes for 2005: Bigger playing field White borders are removed Colored marker poles change location Introduction of out-ball concept Robot’s should stay inside the field Our project: Determine problems that will arise Analyze and document possible solutions Implement solutions for DT2005 code New Rules 2005

  6. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Playing Field 2004

  7. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Playing Field 2005

  8. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Localisation becomes inaccurate Old field size is hard-programmed in Marker poles are moved Extensive usage of white border Behavior is based on closed-border field Bounce effect of borders is used No awareness of out-ball situations Robots don’t know they should stay in the field Problems

  9. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future What we knew: Field dimensions are hard-coded in C++ Field positions and distances are hard-coded in the behaviour specifications What we guessed: Field dimensions may be hard-coded or implicitly assumed elsewhere Problem Analysis

  10. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Based on particle distribution on field Each particle is a hypothetical pose Coordinates and orientation Particles generated on old field size Monte Carlo Localization

  11. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Defined using finite state machines Internal coordination with decision trees Based on hard-coded field positions Behaviour Control (1)

  12. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future If robot.pose.x > 300 then …. Ambiguous interpretation Common sense / intuition Behaviour Control (2)

  13. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future GT2004 Aibo does fine Especially goalie and striker Robust behaviour But: with old flag positions Observations GT2004

  14. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future DT2005 Aibo has some trouble Does fine until kick-off After kick-off positioning is incorrect Observations DT2005

  15. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Initial positioning is purely based on perception With the GT2004 Aibo, all modules are based on the same (old) field dimensions The DT2005 Aibo still recieves wrong input from perception modules There remain unsolved hard-coded dependencies in the DT2005 Aibo Analysis (1)

  16. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Changes in C++ have been checked Changes in behaviour as well We can observe the correctness in RobotControl The problem is elsewhere Hard-coded dependencies in Perception modules Then we ran out of time … Analysis (2)

  17. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Check Perception modules and their configuration files Merge this with our changes in the C++ and behaviour specifications Improve behaviour to take out-ball situations into account as well And you just might win …! Recommendations

  18. RoboCup 4-Legged League Code Overview New Rules 2005 Playing Field 2004 Playing Field 2005 Problems Problem Analysis Monte Carlo Localization Behaviour Control Observations Analysis Recommendations Future Field specifications are likely to change more often Develop a single source for field dimensions Extend FieldDimensions class to make it provide all necessary points and distances Use this in all Perception modules Use this in Behaviour module Future

  19. Do you have any questions? Questions

More Related