Difference between revisions of "MVWT Meeting 2004 08 12"

From MurrayWiki
Jump to: navigation, search
 
(=Goals and Agenda=)
Line 3: Line 3:
 
Goals  
 
Goals  
 
* Review team activities, using status charts  
 
* Review team activities, using status charts  
* Review plans for SURF competition
+
* Review plans for Roboflag competition
  
 
Agenda:  
 
Agenda:  
Line 13: Line 13:
 
Notes from Meeting
 
Notes from Meeting
  
* project review:
+
1 week left for competition (next Friday)
Joe: It's good to get feedback. 
+
there was no AFOSR demo,
Richard: Get inputs from experts, to save time and energy. Schedule the time slots according to the demands of each team. Also make the assigned time slots shorter than actually it should be to avoid running over time.
+
make sure that the vehicles are in good shape for the competition
Chung: Need to go through the notation before the review and make sure they can follow these talks.
+
methods of documentation for the competition
Alex: Reviewers cannot follow the Status chart easily.
+
taking video -- Zhipu: camcorder is ok w/ enough tapes for the whole day
 +
logging data -- Mike: there is a method, but we need to look into it
 +
battery issues of Roboflag, play for 30 mins, charge for an hour?  some sort of rotation scheme
  
* team updates:
+
Team reviews:
 +
1. Vehicle --
 +
Ling: can we get RF competition on the new bats? 
 +
Zhipu: we need to get the SysID running before we can, maybe not but definately before the summer is over.  Redesign the hats since they are larger than the vehicle themselves
 +
2. Positioning --
 +
Demetri: GPS board have been ordered w/ the devel kits, and they can be programmed out of the box (says Superstar)
 +
Zhipu: Vision system is very relible in the past few days, but sometimes it crashes
 +
3. C2 --
 +
Mike: Kelly controller is up, but the vehicles don't hit the waypoints exactly
 +
Brin: Logger is working, it can be possible to replay the game in the simulator with pause/play capabilities
 +
Mike: if you're planning to play RF, try to use the CIT version in SVN and test your code beforehand.  In theory the new version works.
  
(1). vehicle team
+
Rajiv: the vision system handles 16 vehicles, but 8 a team is too many for the testbed.
 +
Demetri: for the people playing RF be sure to plan the number of vehicles you are planning to use.  Also plan to use same number of vehicles a team.
 +
Ling: 3 SB and 3 Kellys a side?
  
Zhipu: changes in the GOTChA chart. see web file for details.
+
Zhipu: should we have a scheduled time for RF players to test out their code?
Richard: is the traj module consistent with C2 team?  
+
Demetri: send out email to list offering time slots where teh vehicle team is available to assist players (Monday or Teusday next week)
Chung: point - to - point controller is not suitable for Kellys or Bats as the dynamics are second order and controller should make use of the dynamics.
+
Zhipu: also have Mike there to be able to debug any problems
Richard: path based traj preferred, position based traj, velocity based traj
+
Zhipu: documentations / send emails to ROCO group member such as Alcherio Martinoli at alcherio.martinoli@epfl.ch or Adam Hayes at athayes@cds.caltech.edu. for Steelebots' documentations.
+
 
+
(2) Positioning Team
+
 
+
Demetri: Need to upload the GOTChA to wiki.
+
Test compass on the roof.  Cost of GPS: $500.00 / 3 boards. 
+
Compasses are functional on Bats.
+
Test 16 hats simultaneously in the lab.
+
 
+
(3) C2 Team
+
Joe: Updates Arbiter, data logger, MVServer needs a new "Makefile".
+
Needs enough Windows machines to run Roboflag SW.
+
 
+
 
+
* ROBOFLAG Competition
+
 
+
Richard: two teams (Jing, Andrew) vs. (Brian, Joe). make decisions on Vehicles picking and strategy design.
+
 
+
Data_taking day in next two week. Playing RoboFlag and anyother projects. Recording all the data by camcorder and computers.
+
 
+
Everybody should try out his/her own codes on Vehicles in next week.
+
Each team test their code and softwares on the real vehicles.
+

Revision as of 23:41, 12 August 2004

Goals and Agenda

Goals

  • Review team activities, using status charts
  • Review plans for Roboflag competition

Agenda:

  1. Review goals and agenda; select notetaker
  2. Discussion of project review
  3. Team updates: vehicle, positioning, C2
  4. RoboFlag competition

Notes from Meeting

1 week left for competition (next Friday) there was no AFOSR demo, make sure that the vehicles are in good shape for the competition methods of documentation for the competition taking video -- Zhipu: camcorder is ok w/ enough tapes for the whole day logging data -- Mike: there is a method, but we need to look into it battery issues of Roboflag, play for 30 mins, charge for an hour? some sort of rotation scheme

Team reviews: 1. Vehicle -- Ling: can we get RF competition on the new bats? Zhipu: we need to get the SysID running before we can, maybe not but definately before the summer is over. Redesign the hats since they are larger than the vehicle themselves 2. Positioning -- Demetri: GPS board have been ordered w/ the devel kits, and they can be programmed out of the box (says Superstar) Zhipu: Vision system is very relible in the past few days, but sometimes it crashes 3. C2 -- Mike: Kelly controller is up, but the vehicles don't hit the waypoints exactly Brin: Logger is working, it can be possible to replay the game in the simulator with pause/play capabilities Mike: if you're planning to play RF, try to use the CIT version in SVN and test your code beforehand. In theory the new version works.

Rajiv: the vision system handles 16 vehicles, but 8 a team is too many for the testbed. Demetri: for the people playing RF be sure to plan the number of vehicles you are planning to use. Also plan to use same number of vehicles a team. Ling: 3 SB and 3 Kellys a side?

Zhipu: should we have a scheduled time for RF players to test out their code? Demetri: send out email to list offering time slots where teh vehicle team is available to assist players (Monday or Teusday next week) Zhipu: also have Mike there to be able to debug any problems