2010 Illinois 4-H Robotics Challenge Robo-Ball: April 24, 2010 TEAM AND LEADER PACKET
Event Overview This statewide event is an opportunity for youth enrolled in 4-H robotics to demonstrate their learning, celebrate their accomplishments, and interact with others who share an interest in robotics. The judges will engage team members with questions and will endeavor to make this a positive experience for all. The most important thing of all is to bring a good sense of appreciation for what the youth have accomplished and have fun. This tournament is put on entirely by volunteers, so show them your support and appreciation for what they have put together for you. Check your worries at the door and enjoy the day and the kids achievements! Event Location The event will be held at the University of Illinois Activities and Recreation Center (ARC), Multipurpose Room #6, 201 E. Peabody Drive, Champaign, IL. This facility is just north of Memorial Stadium. See campus map at http://illinois.edu/ricker/campusmap?target=search&building=118 Parking lots on campus are free on Saturdays. Metered parking is also available. Find specific locations on this UIUC parking map http://www.parking.uiuc.edu/campus_map/2008%20cpm3.pdf Event Date and Times Saturday, April 24, 2010 Registration Judging Awards Ceremony 12:00 1:00pm (Lunch on your own) 1:00 3:30pm 3:30-4:00pm Specific competition times will be confirmed after registrations are received and emailed to participants. Eligibility 1. Counties may send as many teams to this event as they would like. 2. All team members must be enrolled 4-H members in robotics. 3. This is a team competition and has two age divisions (Junior and Senior). Each junior division team must be comprised of at least three youth who are ages 9-14. Members must be 9 years of age by 12/1/10. Each senior division team must be comprised of at least three youth who are ages 14-18. Members must be 14 by 1/1/10. Content Teams will compete in three events: 1) Performance Judging (see attached Robo-Ball Challenge), 2) Technical Judging, and 3) Teamwork Judging. I. Performance Judging, Two Rounds (5 minutes each) Teams will have until April 24, 2010 to design and program a robot that is able to complete the attached Robo-Ball Challenge. This challenge covers information contained in 4-H Robotics project manuals: Robotics I: Explorer, and Robotics II: Probe. It is not expected that teams will achieve perfect scores in the Performance Judging (maximum of 200 points), but rather that team members design a robot and program that reflects their current level of learning. The challenge is designed to be open-ended and includes a lot of room for creativity. The rules for the performance judging are as follows: 1. Team members at the Robo-Ball table will have a brief time to position their mat and prepare their robot for tournament play. 2. One team member from the team should raise his or her hand to alert the referee and timekeeper that you are ready. The team member s hand should remain raised until the round begins.
3. While the robot is in action, the team members must not touch the performance table. 4. Touching the robot is not allowed after the timer has started. If the robot is touched by a team member, the timer will be stopped and no points will be assigned. Each team will be allowed only one re-start opportunity during the competition. Make sure team members understand this rule. 5. Each team will have two rounds of performance judging, with time in between to make adjustments. The best score of the two rounds will be used. A note on variability: Remember that lighting and sound may differ at the competition from the conditions in which you tested your Robo- Ball program. Consider covering your light sensors from surrounding light, and be prepared to make on-site adjustments as needed. II. Technical Judging, 10 minutes A competition track will be in the Technical Judges room. A team may provide a short demonstration of a software program of which they are exceptionally proud. It is not required, just optional. If you decide to do a presentation, it should be at the beginning of the session. The judges will wish to view your team s robot and ask you about its design. YOUR TEAM SHOULD BRING CODE DOCUMENTATION FOR YOUR ROBO-BALL PROGRAM. The team members should answer the judges questions. Points will be awarded based on assessment of the teams technical understanding and not on the performance of their robot. Adult leaders are asked to take a step back and allow the kids to do the talking. III. Teamwork Judging, 10 minutes Teams will be given a problem solving task that requires use of everyday materials. This will not be a robotics challenge. Teams will be judge on their ability to work together in solving the problem and not on their successful completion of the task. Team members will be asked for examples of how they worked together and helped each other in preparation for the robotics challenge. Adult leaders are asked to take a step back and allow the kids to do the talking. Scoring Overview The best of two scores from the Performance Judging, together with the scores from the Technical and Teamwork stations, determine the master score. All teams will be awarded ribbons based on their master score. Funds are currently being sought in hopes of awarding 1 st and 2 nd highest overall scoring teams from the Jr. Division with scholarships to attend the 2010 First Lego League Regional Tournament in December 2010. The team from the Sr. Division with the top master score will have the opportunity to represent the state of Illinois at the 2010 National 4-H Engineering Competition hosted at Purdue University (date not yet announced, but usually early September). Don t Forget Your Team s Stuff! Required Items Your pre-programmed robot Your plastic ball A mat with the Robo-Ball course designed by your team (must fit within dimensions of the performance table) A printed copy of your robotics program (to show to the Technical Judges). Suggested Items Extra batteries or a recharger with a USB cable. Your parts kit. A powerstrip A laptop with the robotics software
Power outlets will be available in this area but are limited. COACHES ARE ENCOURAGED TO BRING THEIR OWN LAPTOP FOR LAST MINUTE PROGRAM CHANGES. BE SURE TO BRING BLACK ELECTRICAL TAPE TO COVER THE RCX INFARED WINDOW TO PREVENT ACCIDENTAL ERASURE OF YOUR PROGRAMS. Practice Tables Each team has two opportunities for Performance Judging. A practice table will be available for teams to use before and between their Performance Judging times. This area is for testing robots and making last minute changes. Teams need to limit their time and respect the needs of others. Transporting Robot during Event It will happen... someone will drop their robot and watch the parts explode in a million directions. It s not pretty. BRING A PLASTIC CONTAINER OR THE BOX INCLUDED IN YOUR KIT FOR CARRYING YOUR ROBOT DURING THE EVENT. If it drops, you have a better chance of collecting all of the parts and reassembling it. How to Treat your Refs and Judges Our referees and judges have been trained and are professional in their attitudes and behaviors. They are, however, human and participating in this tournament as volunteers. The ruling of a judge or referee in this tournament is final and will not be up for debate (no matter the circumstance). Please discuss beforehand with your team and with parents that arguing with referees or judges is unacceptable behavior. This tournament is about the achievement of the kids, teamwork, and sportsmanship. No Cameras with Infrared Flash or Lighting while the robots are in operation during performance rounds! It interferes with robot programs! Learn how to protect your programs and use them. There will be many computers with infrared transmitters in the building. All infrared transmitters are required to be on low power, but if your robot is too close to other transmitters and turned on it could be a tragedy! Turn the sensitivity of your RCX down to short range and protect your programs! USE CAUTION IN WALKING AROUND THE ROOM CARRYING YOUR ROBOT WHILE IT IS TURNED ON! You should used BLACK ELECTRICAL TAPE OVER THE RCX INFRARED WINDOW TO PREVENT ACCIDENTAL ERASURE OF YOUR PROGRAMS. Some teams bring a small cardboard box and are careful to place the box over the robot and infrared transmitter before turning on the robot. In this way, they can reprogram their robot without worry of other transmitters. FIRST TIME TEAMS, if you have been working with a single RCX and computer for programming during the season, you may not realize the significance of the statements above. Other computers nearby CAN reprogram or hinder the ability of your own computer to program your robot. Take the precautions mentioned above. Safety We expect everything will go safely. No injuries, no accidents, nothing that a hug or a bandage couldn t remedy. However, as a coach you have to be aware of your responsibilities for the care and safety of your team members, your belongings, those around you, and the facilities. It starts when you get behind the wheel and doesn t end until the last team member gets safely home. Personally, we wouldn t want these responsibilities alone and would expect at least some of the parents of the students to make the trip as well. There will be a lot of valuables sitting on tables around this event. If even one person lost something to theft, it would be felt by all. Use common sense. Don t leave valuables unattended. If something is expensive and a likely target of theft, leave it at home. Encourage Establish rules for your team before you arrive. Keep your team members safe. If an emergency arrives, there are two hospitals in Champaign-Urbana: Provena Covenant Medical Center: 1400 W. Park, Urbana, IL, Emergency Dept. 337-2131 Carle Foundation Hospital, 602 E. University Ave, Champaign, IL, Emergency Dept. 383-3313
Contact Information Before the Tournament Dr. Lisa Bouillion Diaz SET Youth Development Extension Specialist University of Illinois Extension State 4-H Office lisabou@illinois.edu Day of the Tournament: 217-722-1725 (cell # Diaz) Anything Else? Good luck to you and your team. If you see something missing here, or want clarification, please let us know!