The teams did very well in their documentation scores - Team A got 24 out of 27 and Team B got 26 out of 27.
Team A | Team B |
Mechanical Design: 2 Source Code: 3 Team Strategy: 2 Game Strategy: 3 Testing Procedures: 3 Robot Names: 3 Team Assignments: 3 Schedule: 3 Weekly Status Reports: 2 Comment: Glad to see you are doing Botball again this year Lockheed Martin Exploring Club (Team A)! You have an interesting approach to weekly updates - please also make sure that you make new update entries on a weekly basis rather than all in one post. Good luck this year! Note: Supplemental Website and Lessons Learned will be automatically marked 0 for Periods 1 and 2. They are only scored on Period 3. |
Mechanical Design: 3 Source Code: 3 Team Strategy: 2 Game Strategy: 3 Testing Procedures: 3 Robot Names: 3 Team Assignments: 3 Schedule: 3 Weekly Status Reports: 3 Comment: Glad to see you are doing Botball again this year Lockheed Martin Exploring Club (Team B)! As I mentioned to Team A, you both have a good approach to Weekly Status Reports. It would be a good idea if the language was not exactly the same for both your teams in a couple categories. Good luck this year! Note: Supplemental Website and Lessons Learned will be automatically marked 0 for Periods 1 and 2. They are only scored on Period 3. |
We moved into a small room where we can leave things up all week. This is Spring Break in Montgomery county and maybe we can really make progress.
Testing or Resting? |
Documentation, can we beat our score? |
Grabber 1 | Grabber 2 |
Got you, you little bugger! | I'm building a ramp to the orange
ball. |