Management

Milestones

Milestone Deadline Progress
Robot can perform a legal penalty kick Wednesday 27th Jan 2010 Done
Robot can navigate up to a static ball on an otherwise empty pitch from
any location.
Wednesday 10th Feb 2010 In progress
Robot can navigate up to a static ball on an otherwise empty pitch from
any location, dribble the ball toward the goal while maintaining control
of the ball, and kick it in to the goal.
Wednesday 24th Feb 2010 Not Started
Robot can navigate up to a rolling ball, intercepting it on its path Wednesday 10th Mar 2010 Not started
When set on a path towards a wall, the robot can either avoid the wall
reliably or recover reliably from a collision to continue moving down the
pitch.
Wednesday 17th Mar 2010 Not Started
Robot can dribble around a static opponent in midfield without losing
control of the ball.
Wednesday 24th Mar 2010 Not Started
Robot can defend against an opponent by blocking or by stealing the ball. Friday 26th Mar 2010 Not Started

Overall Plan for achieving the milestones

  • Mon 25th Jan – Robot Design capable of performing kick with imputations towards long term design techniques. Every team placed some milestones and initial design ideas on the wiki. Demonstration of robot kicking to Garry using lego programming.
  • Wed 27th Jan – Proper class demonstration of robot with one-way Bluetooth link set up. Submission of group report and individual reports. Tsveta will have the group report available for Tuesday so everybody can read and submit their comments before we submit it. At group meeting we discuss various robot design ideas along with any issues we may be having. Each team update the whole group on what stage we are at (this will generally be the theme to all group meetings). Discuss Feasibility of two way Bluetooth and other innovative ideas for making our robot the very best! Decide on stage each individual team until has to be at to meet the next milestone of navigating to the ball.
  • On the week starting the 1st Feb I will meet each individual team to discuss any problems and needs they may have. We need to have nice fully functional website completed by this week as well. We should also have each group member write a small biography and at the week’s team meeting we will take photos of each group member for this biography web page.
  • Mon 1st Feb – Individual meeting and maybe attempt to have group meeting where we will all discuss what stage we have now reached on development and communication. At this point we will have to have a fairly functional vision systems and it would be useful if we could have some sort of a simulation in place. Any changes to the group’s structure and everyone’s jobs can also be discussed.
  • Wed 3rd Feb – Group meeting with the usual discussion and progress reports. Individual team development is of crucial importance at this stage as the next task is quite a challenge in terms of coding and system design/ coherency. Also at this stage I would like to have finalised and successful robot design that we feel satisfies all the criteria of our design specification. We will then make the documentation and design instructions for our robot. Refinements of our communication protocols and website will also be discussed here.
  • Mon 8th Feb – Group meeting where we will conduct a group demonstration of the robot moving to the ball. All points about refinement will take place at this point. Each individual team will also have submitted updated documentation and analysis to the wiki. Group report will be available to view on Tuesday
  • Wed 10th Feb – Final date to perform group demonstration to judges and we will also have our regular meeting. Group report and individual reports will be submitted. Regular things will be discussed at meeting. Along with discussion about the success google wave has been as an instant messenger for the group.
  • Wed 17th Fed – Regular group meeting where will make sure we are on course to meet next deadline by Monday the 22nd. Any issues will be discussed along with group restructuring if we feel it is necessary. The next deadline should not be that much more difficult than the last one as we can already kick the ball and can navigate to it. We will only have to discuss where shooting should take place and when we should move with the ball. At this point we will be more aware of the shortcomings of our robot design and any changes can be recommend and adapted at the team meeting.
  • Mon 22nd feb – As before we will meet now and review the robot and make sure it scores a goal. We will also demonstrate to Garry for extra marks if we can. Each team should again update the wiki with new analysis and design ideas for Tseveta to compile into a group report.
  • Wed 24th Feb – Perform demonstration of our robot scoring a goal to the judges and then have meeting to discuss team progress. Make note of website changes we feel should happen and get videos of our robot scoring goals and moving etc. We will discuss what improvement we feel are needed to make an impact at the first friendly!
  • Wed 3rd March – Regular group meeting with progress reports. Suitable GUI’s will be discussed for our machine as well and this is the last stage I feel we should be deciding on system design changes. After this everything will be about testing, enhancements and refinements to the overall system. If it is decided a part of the system should be ported to another language it should be decided now. System integration should be a major topic at this meeting.
  • Mon 8th March – At this point updated information should have been submitted to the wiki for Tsveta to compile into the group report. It is imperative that this information is complete and concise to help make Tsveta’s job easier! Group report will be sent to everyone on Tuesday and after refinement will be submitted on Wednesday. We will also discuss how we feel our robot and system will hold up in combat and make sure we feel our strategy is ok for Wednesday.

** Guys after this point we will continue to meet on the Wednesday as a group and I would like to have a wholly completed system by WEDNESDAY 17TH MARCH. I know this is very tight but I am sure with our talented and hardworking team we are capable. Obliviously changes to this schedule are going to happen and delays will happen and certain jobs will be done quicker. This is definitely a learning curve for us all. If anybody has any amendments or advisements they would like to make for this plan please let me know, it is by no means final. **

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License