What does your team do for Kickoff?

[sanddrag]

Would you think I was nuts if I told you we spend a portion of the afternoon preparing parts and material ordering lists?

We do the same as many teams. It starts off rather casually, as we wait for the kit in line, and joke about large fans, springs, and curtains in the robot design. Then as soon as we get the kit loaded into the back of my truck, we ferociously rip it open screaming "How many CIMs!?" Then it's off to breakfast at a local diner, and then to the school. The students watch the recording of the kickoff many times over, and we make sure everyone understands the game. Then we scrounge for a whiteboard marker, usually come up with only dead ones, and give up and go home. (j/k!). Then the usual bit, brainstorming, how to handle the game piece, how to do it faster/better, how to fit it all, etc. We try to continue this to the point where we don't leave for the day until there aren't any major flaws in our plans.

[ttldomination]

It seems that my team's kick-off plans change from year to year.

This year, the county school board is much more "involved" than they were last year, which is never bad. They have highly encouraged that we attend kick-off at a county location along with other teams from the county/region. (We have like 6 teams in our county alone )

So we have accepted and we will be meeting there to watch the kick-off. We will be sending representatives down to the Georgia Tech Kick-Off to pick up the kit of parts.

Usually after the kick-off, we give things a little time to simmer and we go to lunch. This gives people a chance to work the rust off some ideas that they immediately thought of, and we wait for the reps that went to the official kick-off.

After lunch break, we usually take about an hour to go over the game, make sure everyone is clear on how it's played and some of the ins and outs of more complex rules.

And then we dive into brainstorming. We generally spend about 2-3 meetings (each is about 3 hours long) thinking of ideas, and from there we generally break into prototyping, building chassis, gearboxes, etc.

[qhsscience]

Providing we have the satellite link, our team meets for a team breakfast (the works cooked by one of our mentors), then we sit around a few screens and watch the kickoff. Generally, when the kickoff is over, we mull around for a few minutes and then tell everyone to go start reading the rules (no really...read the rules!) in preparation for brainstorming the following Monday. Our adult mentors then get together on Sunday for the purpose of ordering field parts, doing our own brainstorming, eating (again!) and generally making sure that we are ready for Monday. I have found that getting the team together for that first day is not critical, but very worth doing...in fact, we are installing DirectTV this year in our facility so that we CAN meet as a team on that Saturday.

[RoseJ]

Team 1322 usually meets up at Kettering where the kickoff takes place for our area. The different teams go to the auditorium where we all watch the videos for that season. The G.R.A.Y.T. Leviathons then snag a classroom in the general area and go over the rules and how the game works. We talk about different ideas while eating food and drinking beverages that someone from our team brings for us. Some people go get the kit for the year and meets up with the rest of us to check out the game field parts. Not everything happens in that exact order, but that’s just the general idea of what goes on at Kettering.

[maltz1881]

Well I am taking off from where my above me Rosie left off!! I usually ask the kids to keep a journal from Saturday-Monday night when we will meet again. From there EVERYBODY presents there ideas on how the game should be played. We have some creative people who will come in with cardboard models. I love it. We then discuss all the ideas and usually take a little bit of everybodys ideas, and design around that.

On the Saturday following the Kickoff we meet with approx. 15-20 other teams to discuss how they interpet the rules and how they see it being played. This can be a real eye opener. Everybody can interpet the rules their own way so this can really turn into quite the debate. This is just meant to be be nothing more than a help session to all the area teams. I always learn something new as well. Some teams will bring drawings or they simply discuss what they are building. Our area has a group called MMRA and all but 1 team are members. Our job is to aide each other as much as possible.

I am seeing a lot of pizza eating in my future!!

[Samheartsrobots]

Originally Posted by TNT101

Team 1507 watches kickoff which is patched through our local TV station and spends the rest of the day figuring out the rules and what the game actually is. After if we feel comfortable we start to write possible strategies but the bulk of that isn't until Sunday.

To add to what my teammate Taylor wrote:
We spend much of the rest of the day reading, and deciphering the manual as to avoid the "READ THE MANUAL!" problem (mostly). Then after everyone's notes are attached, we basically have a second, easier-to-read manual. Then everyone goes home and is supposed to come back to school on Sunday with 5 designs concerning any part of the robot. Also on Sunday, we choose exactly what we NEED our robot to do, and what we WANT our robot to do (eg.: are we playing offense, do we NEED to get super cells). Then we sort all designs into categories and number them, and then we have a vote on which ideas are the best. Once we pick what we need to do and what we want to do during a match, we keep these ideas throughout build season so we don't end up having to rebuild our robot.

And we also ingest tons of pizza and pop.

[TNT101]

Originally Posted by Samheartsrobots

To add to what my teammate Taylor wrote:
We spend much of the rest of the day reading, and deciphering the manual as to avoid the "READ THE MANUAL!" problem (mostly). Then after everyone's notes are attached, we basically have a second, easier-to-read manual. Then everyone goes home and is supposed to come back to school on Sunday with 5 designs concerning any part of the robot. Also on Sunday, we choose exactly what we NEED our robot to do, and what we WANT our robot to do (eg.: are we playing offense, do we NEED to get super cells). Then we sort all designs into categories and number them, and then we have a vote on which ideas are the best. Once we pick what we need to do and what we want to do during a match, we keep these ideas throughout build season so we don't end up having to rebuild our robot.

And we also ingest tons of pizza and pop.

Lol she definately says it better than I do, esentially we have a lot of fun while breaking down the game

[viking]

Team 1777 holds a Pancake Feed / Silent Auction / Kickoff event in our school cafeteria. We have fun with previous years robots, raise some money and then watch the kickoff on NASA TV. Current team members and any other family members are invited to do brainstorming, with a pizza lunch and then inventory the KOP.

By the end of the day, we will decide on the chasis, study manipulation options and start talking about the game strategy.

Our local Kickoff Event only allows 2 persons per team, so we send a couple of our mentors to go to that, which will include a couple workshops before delivering the KOP.

[Nick Lawrence]

I think most teams learn what the game is.

-Nick

[charrisTTI]

Team 623 will attend kickoff in Washington, DC at McKinley Technology High School. We will be mentoring teams at the KitBot build session in the afternoon. We will have a team pot luck dinner for team members and their families that evening. After dinner we show the animation and selected other portions of the broadcast to get "everybody" on board. After that we hand out lots of markers and poster paper and have all the attendees help with the first brain storming session. Everyone (group or individual) who wants to gets to come up and has 60 seconds to explain their drawing (idea). Fathers, mothers, brothers, or sisters, any age is welcome to participate. We keep sticking the drawings on the wall around the cafeteria. We also signup parent volunteers for various upcoming tasks during the coming build season.

Lots of fun for all. It really gets everyone exicited and involved.

[Justin Montois]

Originally Posted by Nick Lawrence

I think most teams learn what the game is.

-Nick

Right on. We read the rules, then again, then again. Then talk strategy. Like many have stated, unless you know what the problem is, you can't solve it. We talk about what it takes to win a match and then in the following days we discuss how to build a robot that best executes that strategy.

[1986titans]

Originally Posted by viking

Team 1777 holds a Pancake Feed / Silent Auction / Kickoff event in our school cafeteria. We have fun with previous years robots, raise some money and then watch the kickoff on NASA TV. Current team members and any other family members are invited to do brainstorming, with a pizza lunch and then inventory the KOP.

By the end of the day, we will decide on the chasis, study manipulation options and start talking about the game strategy.

Our local Kickoff Event only allows 2 persons per team, so we send a couple of our mentors to go to that, which will include a couple workshops before delivering the KOP.

We do something very similar with the two other teams from our town.

[Kims Robot]

1511's schedule last year was:
Saturday
9am-12noon Kickoff at RIT
We had the locked pdf manuals waiting at a printing place nearby, and call them with the password to start printing as soon as it comes out.

12-1:30pm Lunch at PHS, reading the rulebooks in small groups. We generally do the reading out loud so that everyone is paying attention to details. Students are given a Subteam Selection sheet where they can think about which subteam they want to be a part of.

1:30-2:30pm Strategy discussion as a team (listed up on flipcharts)
List all Scoring & Penalty Options
List Robot Specific Rules
List Interesting Rules
List All Autonomous Strategies
List All Offensive Strategies
List All Defensive Strategies

2:30-3:30pm Small Group Strategy Work
Groups are tasked to select 2 Autonomous Strategies and 5 (TOTAL) offensive and/or defensive strategies (7 strategies in all). Students present their strategies & why they chose them and as they presented we tallied up the strategies that were selected.

3:30-4pm Strategy Discussion
We talk about anything specific that comes up (last year it was about collection strategies) and do any votes to get a feel for how everyone is leaning towards.

4pm Break - students submit their subteam selection sheets, indicating their top 5 subteams they want to be a part of. Lead Mentors of the subteams meet and select students for the subteams we do at least 1 new, 1 returning, 1 CAD (for all but programming), and try to balance out the groups so that students get near their first choice but are broken up enough so that they are on task and its not just a social group.

4:30-7pm - Strategy Subteam Meets. They review old games that are similar to this game, find robots from past years that might work for this game, discuss critical strategies, key concepts, try to find any specific lock down game strategies, crunch lots of numbers on scoring points/penalities, determine what really is important. They also develop the Weighted Objectives Table for the following day.

Sunday
9-11:30am - Field group goes and buys materials for the field.

12-1pm - All team lunch & Review of the strategy team findings, subteams are announced.

1-2pm - Drivetrain group breaks off to go finalize design, order parts, etc.
Team breaks into small groups for mechanism design. Each group must come up with 2 designs for 2 different types of mechanisms (last year was 2 collection, 2 scoring). At the end of the time, a student from each group presents their ideas.

2-2:30pm - Team Develops different "robot types" from the ideas, people select which idea they are most interested in, each type must have at least 4 people to move on (last year 5/8 types moved on).

2:30-4pm - Fleshing out the designs, they design up the full robot idea, select motors, sensors, come up with parts details, sizing, drivetrain orientation, etc. At the end, they all present the ideas with all of the details.

4-5pm - 1 rep for each design remained with the design and everyone was given Weighted Objectives Tables and asked to go around and rate each design on a handful of criteria. This ensures that everyone understands every design and is really rating them on what is important. All of the scores are tallied and numbers are averaged to see which robot designs ranked the highest.

Depending on how things go after that, either there is a clear decision, or mentors/strategy/leadership further discusses what design we need to select to meet our strategy goals.

Monday - day off (drivetrain group may meet/communicate to get things moving)

Tuesday - We finalize/announce the robot design selection and get to work.

This is a schedule that we have refined over the years, and tend to refine further each year. It seems to work well to get everyone on the same page, and we believe heavily in locking down a design by the end of the weekend, and having a drivetrain running by the end of week 1.