oregon robotics tournament and outreach program ii. coaching/mentoring techniques workshop for...

Post on 13-Dec-2015

219 Views

Category:

Documents

4 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Oregon Robotics Tournament and Outreach Program

II. Coaching/Mentoring II. Coaching/Mentoring Techniques Workshop Techniques Workshop for Mindstorms NXTfor Mindstorms NXT

20072007

Opening doors to the worlds of Opening doors to the worlds of science and technology for science and technology for

Oregon’s youthOregon’s youth

Instructor Contacts

Ken ConeKen Cone

ken_cone@ous.eduken_cone@ous.edu

503-725-2918503-725-2918

Roger SwansonRoger Swanson

swanson@hevanet.cswanson@hevanet.comom

503-297-1824503-297-1824

Jim RyanJim Ryan

james.r.ryan@intel.cjames.r.ryan@intel.comom

971-215-6087971-215-6087

Scott StankoScott Stanko

scott.stanko@intel.cscott.stanko@intel.comom

(971) 215-9677(971) 215-9677

Today’s Goals Focus on being a coach or mentor

using Mindstorm NXT robotics kits I hope you leave:

Feeling more comfortable about your role

Having some more tools in your bag of tricks

Understanding better what it takes to solve a challenge.

Having gotten your questions answered Have some fun!!

Agenda Review our Mission Forming your team Registering your team Equipping your team Managing your team NanoQuest Challenge kit Use NXT Robots from last week to

program more with the Mindstorms NXT Software

Our Mission Program not just about building robots and

competing in tournaments Teach skills

Specific technical skills General life skills

Show that technical problem solving can be fun The youngsters do the work – Coaches’ Honor

Code and Team Promise Open up the possibility of technical careers One secret opportunity

We’re We’re asking you asking you to help us!to help us!

Forming Your Team

Where Teams Come From School Based

In class: Perhaps 45 minutes a day After school: Perhaps 1.5 hours; 2 to 4 times a

week Special block: Several hours once a week

Club Based Probably after school or evening

Independent team After school, evenings, or weekends

We encourage you to find and include youngsters that normally would not have this exposure

Where to Meet Large enough space to handle the

number of youngsters on the team Space for challenge field setup –

4’x8’ Access to a computer Storage space between meetings

Challenge table Partially built robot Lego parts

Team size High initial interest may fade Sub-teams of 2-3 can work in parallel

Experiment with prototypes Learn programming techniques Work on the presentation

Eventually team should stabilize at 10 or less

5 to 7 team members is probably ideal

You Need Adults, Too! Coach – The person in charge

Organizes the team Does not need to be a techie

Mentor – The technical guru Provides technical advice Provides the technical basics

One person can play both roles But, don’t go it alone Recruit other adults to supervise sub-

teams

Coach – The Person in Charge Single point of contact for team Understands the FLL and ORTOP

programs Management expertise more important

than technical expertise Recruits the team Registers the team Arranges for equipment Schedules meetings Sets the philosophy and instills team spirit Is a good role model

Mentor – The Technical Guru Technical Advisor to assist the coach Teaches both robot design and

programming Helps set achievable goals Encourages structured problem

solving Follow typical engineering project models Experiment with one variable at a time

Graduates of FLL can work as mentors

General Advice to All Adults This is the kids’ project, not yours Be a good role model Keep a positive attitude Encourage teamwork and insist on

mutual respect Don’t over emphasize “winning” –

demonstrating a solution at a tournament is success

Have fun

FLL Team Promise We are a team. We do the work to find the solutions with

guidance from our coaches and mentors. We honor the spirit of friendly competition. What we discover is more important than what

we win. We share our experiences with others. We display gracious professionalism in

everything we do. We have fun.

Registering Your Team

Team Registration National registration through FLL:

http://register4fll.com/ May through end of September or when

max reached $200 FLL registration fee Receive Coaches Handbook, web forum

access, DVDs on FIRST and FLL, and support

Optional ordering of kits First-Come-First-Served, so REGISTER

EARLY!!

Purchases at FLL Registration Registration fee: $200 FLL Robot Set (NXT) $325 Field set-up kit: $65 Extra parts: motors and sensors

(rotation, light, and touch) They don’t ship until they are paid

ORTOP State Registration Takes place in October 2007 $50 fee for ORTOP We notify all coaches that have

registered with FLL in Oregon and SW Washington Provide list of local tournaments Ask for 3 local tournament choices in

priority order We assign teams to local tournaments Register early!!

Equipping Your Team

Minimum Resources to Start

A robotics kit A computer A place to meet and practice

Classroom Family room Garage

Additional Resources 2007 FLL “Power Puzzle” Field Setup kit

(only from FLL) Mission Model Set Field Mat

Practice table (design on FLL website) http://www.firstlegoleague.org/default.aspx?

pid=11330 4’x8’ bottom Railing around the sides Overhead light

Robotics Kit Info RCX-based kits

LEGO kit used by FLL in past years Can still be used in tournament in 2007 They will be phased out eventually

NXT-based kits Brand new last year $325 if ordered during FLL registration Ship to registered teams starting in mid-May

Robotics Kit Info – NXT-Based FLL NXT -- $325

Complete kit with two tubs and sorting trays NXT software

LEGO Education NXT Base Set -- $250 Fewer parts with one tub and sorting trays No software

LEGO Retail -- $250 Fewer parts with no sorting trays Includes NXT software

See NXT Kit Details handout for details

Allowed NXT Robot Parts NXT controller (1) Motors (3) Touch sensors (2) Light sensors (2) Lamp (1) Rotation sensors (3 minus the

number of NXT motors present) Ultrasonic sensor (1)      

Team Uniforms?? Many teams do something for the

tournaments Team shirts, hats, etc Theme clothing

Team sponsor advertising on a T-shirt, etc. is OK

Example Team Budget National Registration Fee: $200 State Registration Fee: $50 2007 Robotics Kit: $325 2007 Field Setup Kit: $65 Materials for table: $50-$100 Misc. including batteries, shipping: $50-

$100 Total: $740-$840

Possible Sources of team funding

Fundraising Activities

ORTOP Scholarship

Team Member Dues

Team Sponsors

Having some portion Having some portion of costs picked up by of costs picked up by team members gives team members gives a sense of a sense of commitmentcommitment

ORTOP Scholarships Funding should not be an obstacle to

a team’s participation Cover up to $760 in team costs Accepting applications now Awards made at least monthly Last date is September 16, 2007 http://www.ortop.org/

res.htm#scholar

Managing Your Team

Meeting Organization How often and how long to meet

Most teams meet 2-3 times per week After school, evenings, weekends as team

desires Some add extras as get closer to end > 1 hr (set up and take down) < 3 hrs (attention span)

At least 2 adults present during meetings – can use parents who take turns

Set ground rules -- E.g. don’t turn kids loose to walk home by themselves after dark

Refreshments / snacks

Team Kick-off Meeting Every child brings parent Set expectations with both Send kids off to build with LEGOs

Get assistant to help Build with instructions, like the

Constructopedia Something they can all do at once

Explain the real situation to the parents

Parent Involvement Explain program/FLL philosophy

Success = Participation Explain team rules Discuss participation commitment

for kids Review costs and funding sources Communicate about tournament Solicit help

Getting Started with the Kids

Set Team Goals Decide responsibilities

Can rotate, especially near beginning Usually will want to be fixed as near tournament Need backup roles due to absences

Set milestones – use project management analogy Set dates for each phase of project to keep on

track Include design, build, test, REWORK

Encourage participation in a team environment

Learning Opportunities Encourage risk taking

It’s OK to fail Key is to manage the risk

Encourage experimentation Expect failure – focus on what is

learned as a result Problem solving takes time –

Edison’s experience with light bulb filament

Facilitate Structured Problem Solving

Defining problem Brainstorming Evaluating alternatives Choosing alternative Implementing Evaluating & testing

Hard vs.. Soft Skills Hard Skills

Mechanical Design

Programming Analysis Problem Solving Experimentation Documentation

Turn these youth into little engineers

Soft Skills Timeliness Teamwork Tact and

Compromise Confidence Courtesy Perseverance Planning

Build a Foundation Introduce techniques and concepts

Build or bring demos Discuss advantages and disadvantages Let kids figure out how to apply concept to

Challenge If meetings start before Challenge is

announced, can use mini-challenges to introduce concepts

One approach: use 5-10 minutes at start of each meeting to introduce concepts

Sample Concepts Pick one or two new subjects per

session Structural strength: bracing vs. snapped

pieces Gear ratios: torque vs. speed Traction: tracks vs. wheels Friction: tires vs. skids Programming techniques: linear vs. loops

vs. subroutines

Divide and conquer Three basic robot functions:

Locomotion: how the robot moves Navigation: how it knows where to go Robotic Action: function it performs

Locomotion Motors Gears/pulleys Wheels/tracks Steering Friction

Navigation Time, but sensitive to battery charge Touch Sensors

Means of triggering Pressed vs. release

Light Sensors Light levels Darker/lighter Calibrating thresholds

Rotation sensor

Robotic Action Pushing Grabbing Lifting Dumping

With All the Focus on the Robot and the Challenge…

Don’t Forget the Judging

Technical Judging – 25% Panel of “experts” interviews teams

Robot design: Creativity and robustness Programming: Creativity and robustness

Prepare the team to: Explain their design of the robot and its

program Demonstrate at least one mission on the

challenge field Bring a printout of the program

Presentation Judging – 25%

Don’t ignore it Another good learning opportunity

Research skills and presentation skills (remember the marketing kid? )

Good engineering requires research and communication

Format 10 minutes including setup Posterboards, skits, models,

Powerpoint, . . .

Sources of ideas Constructopedias/Manuals/Guides NXT Software Tutorial on CD-ROM Books – http://www.ortop.org/res.htm#books Web links – http://www.ortop.org/res.htm#links

Lego FIRST INSciTE -- Minnesota FLL Tufts University – Inventor of

Robolab NXT is new so not all resources are NXT

specific – still usefull for general techniques

Art of Lego CMU Best Practices

Our Mailing Lists Totally voluntary, and you can opt out ortopvol

All volunteers One way from ORTOP to our volunteers We add you when you volunteer

ortopcm Coaches and mentors Communication among that group and with

ORTOP We add you when you complete a workshop

Next Steps Take Dale Yocum’s NXT Tutorial:

http://www.ortop.org/NXT_Tutorial/ Sign-up for another workshop

III. Robotics Techniques Workshop http://www.ortop.org/res.htm#REG

ESCO – “Robotics Mentorships as a Developmental Career Opportunity”

Contact Us

Web site: http://www.ortop.orgEmail: questions@ortop.orgPhone: 503-725-2920

top related