Kickoff day

[Sperkowsky]

Just wondering we usually go to kickoff at a college but if we decided to just stay at our school how would we get the KOP.

[KrazyCarl92]

Originally Posted by Sperkowsky

Just wondering we usually go to kickoff at a college but if we decided to just stay at our school how would we get the KOP.

You could send a small group of a couple people to pick up the KOP at the local kickoff and then do your thing at your school while those few people drive back to join you with your KOP.

[ahartnet]

Pearadox did a kickoff at our school last year with a visiting team as well. We had a parent that was kind enough to drive the 60+ minutes to the local kickoff and pick up our kit and bring it back. Alternatively you can have it shipped - but if you're within a reasonable driving distance you should definitely just go pick it up. Additionally it's too late this year to have it shipped instead of being picked up. Another option is to have a team be a surrogate and pick it up for you, there's some paperwork that will be available if you have another team pick up your kit for you.

Last year a veteran team joined us and we had a guest speaker, did some interteam ice breakers, and did a quick analysis of what we saw in the kickoff video before the other team went back to their school.

This year we're inviting a few more local teams (one veteran that we're friends with and two rookies). We'll do something similar - guest speaker, what did we see in the kickoff video, etc. We're inviting the rookies to stay for a lunch that we're trying to get a local grocery store to sponsor, and talk through the game a little more in depth with the rookies and answer any questions they may have.

Unrelated to that, we'll probably have a mentor or two look through the team drawings Saturday morning to get a BOM together and go purchase wood for building major field elements. Around 3 or so we'll probably start building the field with the intent being to visually look at the field so we can get an idea of how big/far certain things are before we make any major decisions on our game play strategy.

[logank013]

We head over to our sister school for kickoff (like 5 minutes away). Once we get done with that, we usually break for lunch and come back to our lab at like 1 pm and spend the whole day there breaking down the rules and coming up with design ideas. It feels like we spend the whole day there. I going to try my hardest to read the whole rule book that day if possible. I always find the rules interesting.

[Knufire]

I recently gave a talk on this at the Minnesota SPLASH event. I'm not sure if the presentation was recorded, but the slides can be found here: https://drive.google.com/file/d/0Bx6...ew?usp=sharing.

To quickly summerize

Saturday, game release to around 1-2PM - Lunch + Going through the manual in small groups. Come back together as a team and highlight all critical rules. Answer any questions or clarifications. Brainstorm any Q&A questions, if any
Saturday, 2PM to close - Robot task list. Highlight every single function a robot can perform in the game. Careful attention to word these such that it doesn't shoehorn you into a single design (e.g. score ball instead of shoot ball).
Sunday, Monday, Part of Tuesday - Game simulation
Rest of Tuesday - Robot function priority list
Wednesday, Thursday, Friday - Conceptual work, base level prototypes (just answering if concepts are possible, not finding specific details).
Saturday, Meeting together, debate various concepts, find final overall robot concept, split into subsystems and start more detailed prototyping and design

[feverittm]

Great Timing.

Our team is having our 'Week-in-a-Day' exercise -- A mock Kickoff and First Week activities -- this Saturday. We have done these in the past and they have been very useful especially for those who have never been involved with FRC before. I will pick a previous game and the team and mentors (I haven't told them which game either) will work though the process. I usually tweak the rules slightly in order to make them more relevant and to eliminate any issues seen before with this specific game.

On the actual Kickoff we normally meet very early (like 6:30AM -- our Kickoff starts at 7:00am with the broadcast at like 8:00) since we are on the West Coast (I always feel bad for those folks even further West of us). We meet with about 10 or so other teams in a auditorium at the local university to watch the broadcast.

After the broadcast the teams break apart to head back to their respective locations. A small group will then head off to pick up the KoP and bring it back with them. We do have a couple of teams that just send a couple of folks to the event just to pick up their KoP for their teams who are watching remotely.

After getting back to the school with the K0P we have a small group (3-4 folks) go to another small room to inventory the KoP and get the game piece(s) (if any) to the rest of the team for review. We also take over anything 'special' to review as well (like last year we took the control system stuff over).

In the meantime the remainder of the team is gathering together, eating breakfast, and then re-watching the game animation while the mentors are busy printing up the manuals. We usually print up like 5 copies of the manual so that all the small groups can have a copy.

The remainder of the day is usually spent in small groups going over the rules, dissecting the game, and making up some charts with high level game strategy details (like "how do you score and how many points", "what are the different sections of the game - autonomous, teleop, endgame" and how long are they?). These charts are left up around the room for the rest of the season for review at a glance. We also take the time to note any major changes in rules (like the 'travel perimeter' last year) for our veteran members.

As others have said, we focus first on the game itself - no robots! We look at the game play, strategy. We try to figure out what should happen when. Only when the we truly understand the parts of the game do we start to outline what things on a robot (systems) would be required to do them.

Our who process probably takes 3-4 days with strategic analysis usually taking the whole first day.

I hope this helps

[swaxman12345]

My team is hosting a kickoff stream at a local University. And then game analysis. And then design. And then it's already the next morning.

[BenGuy]

Originally Posted by swaxman12345

My team is hosting a kickoff stream at a local University. And then game analysis. And then design. And then it's already the next morning.

Personally we don't go near robot design for day, and before that, we prototype many ideas first. For example, 2014 year, there was an idea of a catapult and a 'pitching machine' design. We first prototypes these designs, a few days after kickoff, then we designed the robot off of the successful prototypes. And we NEVER design anything on the day of kickoff or even a few days after, only game evaluation for that time.

[TikiTech]

Since the kickoff location for the state of Hawaii is on Oahu. The teams from the outer islands must come up with a localized version.

Here on our island (the big island of “Hawaii”) we decided a few years ago to help our local teams by creating our own kickoff day.

We open our shop to all the local teams to come spend the day doing various workshops.

Actual kickoff video is shown at 5am here. Due to the very early nature many of us watch it from home prior to coming in to the workshop. Gives us mentors something to watch while having our cup of Kona coffee since we all know we gave up sleeping long ago.

Then we will spend the day working with everyone to help with game analysis and more.

We break down the day into various workshops with the attending schools.

Watch Kickoff – We show the video, which many student miss as sleep is still a thing.

Read Rules - Break out the participants into smaller groups and read the manuals. We like to mix up the groups as much as possible. A great time for students to meet and work with each other. During that time the mentors will meet up, read the rules, then create a game rules test.

Rules Review - The students and mentors will review the rules and discuss any concerns.

Rules Testing – Everyone tests on the recently read rules. Discussion to follow if needed.

Game Analysis Part 1 – Discussion on various scoring scenarios, choke points, etc.

Human Robot – Setup of mock fields for small groups to “play robots”. Participants will “be” a robot with one to two tool functions. Such as; hinged arm, pickup, shooter, object sorter… Once “designs” are picked the game will be played multiple times. Each time the players can and select or refine tool functions as the game play reveals.

Game Analysis Part 2 – More discussion on the game analysis after Human Robot. Surprising on the revelations after “playing robot”

Design Labs – We have been using Stanford Design Thinking for many years in our design process and have a trainer on staff. We will give a class on the SDT method and then break out to small groups again. We set up the groups into design stations. Each station will have a portion of design that will act as the point of design with lots of materials for crude prototyping if the design is better explained this way than the usual sticky note.
Some sample groups are: Drivetrain, object collection, object scoring, robot interaction, etc. These groups we (the mentors) will determine. Labs will run roughly 15 minutes before each group rotates to a different lab. Once everyone has gone through all the labs we will all return to vote on the 3 best solutions to each of the labs. This gives many of the smaller teams designs ideas to work directly from.

For more information on Stanford Design Thinking you can visit:
http://kealakeherobotics.org/student...sign-thinking/

or
http://dschool.stanford.edu/our-point-of-view/

Or if you would rather, you can contact me.

Aloha!

[GeeTwo]

Originally Posted by TikiTech

..
Design Labs[/b] – We have been using Stanford Design Thinking for many years in our design process ..
For more information on Stanford Design Thinking you can visit:
http://kealakeherobotics.org/student...sign-thinking/

The five steps of SDT are (from your web site):

1. The first step is empathy; we see how others feel towards a specific item. Interviews are used to gain insight to human nature.
2. The second step is to define. In this step, we use the information gathered from interviews to find the user’s real problem.
3. Ideate, the third step in design thinking, is where the group finds solutions to the problem.
4. The fourth step is to prototype. Once an idea is decided upon, groups work together using random materials to construct examples of their product and explain how their product works.
5. Testing is the final step. Groups rebuild their prototypes and create a working product. Once built, testing begins. Testing identifies problems with the item, so the product can be modified to better suit the user.

With the requirements already specified in the form of rule books, what to you do for step 1 on the first round? The other steps correspond roughly to our planned engineering process; not quite how we think about it, but it makes sense.
Edit: Our mnemonic of the engineering cycle is DRIPPER:

• Define the Problem
• Research known solutions
• Imagine possible solutions
• Plans (blueprints and schedule)
• Prototype/Build
• Evaluate/Test
• Repeat as necessary (meaning not always back to Define)

Looking this over makes me also wonder if and how you review known/previous solutions to similar problems in your process.

[DaveL]

Originally Posted by Knufire

I recently gave a talk on this at the Minnesota SPLASH event. I'm not sure if the presentation was recorded, but the slides can be found here: https://drive.google.com/file/d/0Bx6...ew?usp=sharing.

To quickly summerize

Saturday, game release to around 1-2PM - Lunch + Going through the manual in small groups. Come back together as a team and highlight all critical rules. Answer any questions or clarifications. Brainstorm any Q&A questions, if any
Saturday, 2PM to close - Robot task list. Highlight every single function a robot can perform in the game. Careful attention to word these such that it doesn't shoehorn you into a single design (e.g. score ball instead of shoot ball).
Sunday, Monday, Part of Tuesday - Game simulation
Rest of Tuesday - Robot function priority list
Wednesday, Thursday, Friday - Conceptual work, base level prototypes (just answering if concepts are possible, not finding specific details).
Saturday, Meeting together, debate various concepts, find final overall robot concept, split into subsystems and start more detailed prototyping and design

Great Presentation!

On Slide 9, you say:
"Six students, each student is a robot with 25 units of functionality

Use functionality units to purchase robot functions (value being the
previously assigned difficulty)"

Can you elaborate on your simulation process or provide an example?

Dave

[GeeTwo]

Here is our current draft of kickoff day events (we're in the U.S. central time zone). We're calling kickoff "Saturday 0". We're starting weeks on Sunday, so the next day is "Sunday 1".

Kickoff Day 2016 Schedule (9 Jan 2016, all times CST)
0830 - 0900: Continental Breakfast (Pastry/Donuts, Fruit, Coffee, Milk, Juice)
0900 - 0930: Gathering/Welcome/Organization

• Welcome, admin, & ground rules
• Review Agenda
• Collect e-mail addresses for “proceedings” mailing (esp. non-3946 members)
• If time remains, review game teaser, hints, standards, and such revealed so far.

0930 - 1030: Kickoff Video
1030 - 1130 Set up phase (Main bullets are simultaneous; sub bullets are sequential)

• Printing of Rules (~10 sets)
• Group of mentors begins getting parts and constructing field elements
• Main Group of students:
  • First Impressions
  • Initial list of Robot Tasks (pick up game piece, score game piece, climb, etc)
  • Brainstorm game strategies (one group or a few large groups)

1130 – 1200 Tweak list of rules sub-groups and assign members to these groups – initial list follows:

• Scoring: list/analyze all scoring, including penalties
• Field : e.g. obstructions, key dimensions, possible game flows
• Robot dimensions: e.g. Time varying? Relative to game pieces & field elements?
• Robot details: bumpers & “new” controls/construction rules
• Game Pieces & goals: how hard to pick up, throw, catch, score, whatever
• Non-game piece/auto/end game scoring activities
• Defense: defensive actions and limitations such as protective zones, time limits

1130 - 1230 CST: Lunch
1230 - 1400: Students break into groups, review assigned rules, prepare outbrief
1400 - 1500: Outbriefs from rule review groups (~5 minutes each group + questions)
1500 - 1600: Brainstorm additional strategies and top-level robot designs (one group or a few large groups)

We then plan to go home as a team. After a suitable break for dinner, key mentors and student leaders will meet to begin working on grand strategy (that is, tournament structure) and estimating the value of different functions based on scoring potential about 1800 or 1900 on Saturday 0.
On Monday 1, we shall accept additional robot concepts, then select a limited number of drive trains and robot concepts for further development. (Though anyone who really wants to promote a certain concept may volunteer at this point even if the team as a whole thinks it's not viable.) Tuesday 1's meeting shall be to do quick prototypes and for design groups to get together and develop their plans. At the Thursday 1 meeting, we will get down to one or two design concepts (by consensus, not vote). Preferably both of these concepts will have the same drive platform. Serious parts orders shall begin on Thursday 1 after the meeting. Saturday 1 shall be the first real "build" day, based on the two AM-14U2's and other parts we have on hand or can get from local hardware stores.

[221Sarahborg]

Our plans as a team has varied for the past four years I've been on my team with being on our own in our school's cafeteria and this year the media center. Last year a team on the other side of the KCMO border invited many others to have a breakfast and space to strategize in. This year we will be meeting in our media center like I said and following the broadcast we will be breaking into small groups to get an understanding of the rules but this year I have the honor of being able to pick up the KOP this year.