Download
2012 judging guidelines for exhibition robofashion dance n.
Skip this Video
Loading SlideShow in 5 Seconds..
2012 Judging Guidelines for Exhibition & RoboFashion Dance PowerPoint Presentation
Download Presentation
2012 Judging Guidelines for Exhibition & RoboFashion Dance

2012 Judging Guidelines for Exhibition & RoboFashion Dance

123 Vues Download Presentation
Télécharger la présentation

2012 Judging Guidelines for Exhibition & RoboFashion Dance

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. 2012Judging Guidelines for Exhibition & RoboFashion Dance Go to www.robofest.net and click on [Robofest 2012] button. This PowerPoint file and related materials will be available under “Judging” section. Updated Feb 20, 2012 This presentation is for all volunteers, coaches, mentors, site hosts, and team members

  2. Judging Philosophy • Maximize Students’ STEM learning • Objective and Fair • Simple and efficient – Judges do not have enough time before the closing ceremony for long discussion

  3. Judge Types and Roles Chief Judge Judges Qualify for Regional and World Championships About 20% of teams

  4. Exhibition Judging (RFD judging also uses similar concept) An example of science related autonomous robotics project Sr. Division First Place 2007: Farmington Harrison High School, Michigan GPS guided robotic boat monitoring and  measuring ecological data

  5. ExhibitionCompetitionCategory • Complete freedom to show off any type of creative autonomous robotics project • Must employ sensors • Human to Robot, Robot to Robot interaction strongly encouraged (see next slides) • Math and Science components – No. 1 criteria (25%) • Sharing online video (such as YouTube or SchoolTube) is highly recommended

  6. Possible Interactions Allowed for RFD and Exhibition (Not for Game) • Human <-> Robot • Robot <-> Robot(s) • Student programmed Host Computer <-> Robot(s) • Student programmed devices such as smart phones or another controller operated by human player <-> Robot(s). But note that sensors must be used. • RC (or Joystick) is not allowed. May be used only to start.

  7. Examples of Human <-> Robot Interactions • Claps/Knocks – Sound Sensor • Flash Light – Light Sensor • Color Cards – Color Sensor • Waving Hands – Sonar Sensor • Gesture – On-board camera • …

  8. Examples ofRobot <-> Robot Interactions • IR communication (For example, Lego RCX) • Touch sensors • Light/Color sensor; special color jersey • RFID • Bluetooth or ZigBee • On-board camera – Robot gesture / visible signal • ...

  9. Exhibition Competition • Teams are supposed to demonstrate the project whenever they have visitors • Silent Judgesmay visit team tables individually, as if they are spectators • Official presentation when a group of Judges visits the team table: Teams will have maximum 4 minutes for their team introduction, robot presentation, and demonstration • Michigan Regional and World Championship will have People’s Choice award, decided by spectators

  10. If a team is continuing a prior year’s project… • They must inform judges that this is a “continued” project • They must add new feature(s), or significantly improve or change a feature

  11. Roles of Exhibition Judges (1) • Before the competition date: • Visit team web pages • Watch team videos, if any are submitted • Before the Opening Ceremony: Visit each team table to be familiar with the exhibitions

  12. Roles of Exhibition Judges (2) • Score the official presentation & demo • Any time up to one hour before the closing: • Visit team tables to interview teams • Read their posters • Ask for re-demonstrations, if needed • Inspect program code and robot(s) • Select top 50% teams and submit ranks of them to the Chief Judge using the score sheet • Submit comments on ALL teams to the Chief Judge using the Judging worksheet

  13. Exhibition Competition Team Score is based on:

  14. Possible Problems of this suggested Judging method and How to solve the problem • When a Judge is not a technical expert of a field, for example, program code inspection • Ask other Judges about their opinions before you make final selections and ranking them

  15. Responsibilities of Chief Exhibition Judge • One hour before the closing • Meet with all Exhibition Judges • Collect score sheets with ranks & comments • Calculate total rank for each team using Excel with help from Scorekeeper • Write comments for each team using Excel or paper • During the closing ceremony • Briefly talk about strength and weakness of each team • Announce award winners as well as qualified teams to advance • After the event, submit all the comments, sheets, and the Excel file to the scorekeeper

  16. Exhibition Judging Worksheet • A sample worksheet can be found on the web: • http://www.robofest.net/2012/ExhJudgeForm.pdf • http://www.robofest.net/2012/ExhJudgeForm.xls • Note that Robofest will *not* post these worksheets from Judges • Only final Excel file from Chief Judge and Chief Judge’s comments will be posted

  17. An example: 5 Sr. Exhibition teams, 3 Judges, and a chief Judge • Chief Judge will decide if there is a tie. • No. of teams to advance will be given

  18. Example of Judges’ Comments – Should be read before announcing winners • http://www.robofest.net/2012/ChiefJudgeCommentForm.doc • http://www.robofest.net/2012/ChiefJudgeCommentForm.pdf

  19. RoboFashion & Dance Judging Team SWATT, Kosciuszko Middle School, Hamtramck, MI Synchronization by Bluetooth communication

  20. RoboFashion & Dance Show • Two+ robots are recommended • Human to Robot, Robot to Robot interaction / communication strongly encouraged (See previous slides) • Stage • Two 6ft plastic (folding leg) tables should be used • Team decides orientation • Team will have freedom to design their landmarks by themselves • Bring the tables to the competition site! (or let us know if you need tables)

  21. Note on Interactions • Human to robot, Robot to robot interaction / communication / synchronization is important. • Human players just dancing to the music with robots is *NOT* human to robot interaction

  22. RoboFashion Judging Criteria • Team Intro and Presentation delivery (10%) • Wow! factor and Demo reliability (15%) • Artistic Choreography, Performance, whole stage usage (15%) • Creativity and Innovation (10%) • Applying math & science concepts (15%) • Robot <-> Robot Interactions & synchronization and Human <-> Robot Interactions (15%) • Code inspection (10%) • Robot mechanical design (10%)

  23. Fashion & Dance Judging Worksheet • A sample worksheet sheet can be found on the web: • http://www.robofest.net/2011/Fashion11JudgeForm.pdf • http://www.robofest.net/2011/Fashion11JudgeForm.xls • Note that Robofest will *not* post these worksheets from Judges • Only final Excel file from Chief Judge will be posted

  24. Roles of Chief Judge and Judges • Basically each Judge selects best “n” teams and give their ranks to the Chief judge • Chief Judge calculate total ranks • Please refer to Exhibition Judging guidelines

  25. Little Robots, Big Missions • www.robofest.net • Rule Updates • Clarifications • FAQs • Warm Up Video Questions? Contact: Dr. Chris Cartwright, Robofest Program Manager, ccartwrig@ltu.edu Dr. CJ Chung, Robofest Director, chung@ltu.edu