Meeting 1 - understanding the game
On January 8th, Pearadox had it's first day back after an offseason of rookie training and outreach events. Kickoff is the day where FRC teams all over the world watch the game animation for this years' challenge.
After the game animation ends, our team broke up into groups to go through the rules, discuss different strategies, all the things we think a robot can do, and start figuring out what we want our robot to accomplish in a match. There's a lot of interest and intrigue in a very challenging climbing aspect of the new game, where there are 2 rungs that are higher than you can reach from the ground. The best way for us to try to rank high at a competition and win it is by winning matches (of course) but also earning other "Ranking Points" by scoring 20 game pieces or by having our alliance of 3 robots earn 16 hanging points. If we can get to the high or traversal rung, then we only need to rely on 1 other robot on our alliance to climb. At the end of the day Saturday, we determined that we need to do some prototyping and absorb the game some more before we make any commitments to what our robot should do. We're also fortunate to have had several alumni come back for kickoff. They share a little bit about their experience on the team, what they're doing now, and then help with building the new field with some parent volunteers so our current team members can focus on the robot. Meeting 2 - prototyping begins
Students began sketching out and prototyping ideas they have. We quickly realized that if we want to be able to complete the Cargo Bonus by ourselves, we not only need a good way to score the cargo balls, but collect them as well.
We also started making some progress on building field elements. meeting 3 - Design review
On Tuesdays, we do a design review to keep all the students on our large team updated as to the other things going on on the team. As this was only our 3rd meeting of the season, it was more focused on setting what the requirements are for subsystems and priorities for the team. We determined our priority order should be:
Meetings 4-6
We continued prototyping and got to a good stopping point on our field build. We have team members busy on numerous things - from prototypes of subsystems, to preparing awards submissions, and teaching new team members how to build a robot while keeping our parts and tools organized. On Monday we had a meeting to discuss how we might fit our subsystems together. By the end of the day Monday, we had accomplished the following:
0 Comments
Your comment will be posted after it is approved.
Leave a Reply. |
|