1 Oregon Robotics Tournament and Outreach Program II. Coaching/Mentoring Techniques Workshop for...
-
Upload
gabriel-harper -
Category
Documents
-
view
216 -
download
0
Transcript of 1 Oregon Robotics Tournament and Outreach Program II. Coaching/Mentoring Techniques Workshop for...
1
Oregon Robotics Tournament and Outreach Program
II. Coaching/Mentoring II. Coaching/Mentoring Techniques Workshop Techniques Workshop for Mindstormsfor Mindstorms NXT NXT
20112011
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
2
Instructor Contacts
Roger SwansonRoger [email protected]@hevanet.com
503-297-1824503-297-1824
Jim RyanJim [email protected]@intel.com
971-215-6087971-215-6087
Ken ConeKen [email protected][email protected]
503-725-2918503-725-2918
Dale JordanDale [email protected][email protected]
3
ORTOP Project Administrator
Cathy SwiderCathy Swider
[email protected][email protected](503) 725-2920
4
Today’s Goals Focus on being a coach or mentor
using Mindstorms 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!!
5
Agenda Review our Mission Forming your team Registering your team Equipping your team Managing your team Body Forward Challenge kit from 2010 Use NXT Robots from last week to
program more with the Mindstorms NXT Software
6
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 asking you to you to
help us!help us!
8
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
9
Not a Drop-In Program This is a project oriented program Parents and team members need to
understand the commitment required
Team members need to be available on a consistent basis to move their parts of the project forward from the first meetings through the season-end tournaments
10
FIRST® TeamUp Program A program at FIRST® to help teams
find team members or place extra youngsters on teams in their area.
Pay attention to the caveats and disclaimers noted at the site.
https://my.usfirst.org/FIRSTPortal/login/fc_Login.aspx
11
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
12
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 project
Maximum team size allowed is 10 5 to 7 team members is probably
ideal
13
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
14
Coach – The Person in Charge Single point of contact for team Understands the FLL and ORTOP programs Management expertise more important
than technical expertise Point of contact for FIRST® and ORTOP info Recruits the team Registers the team Arranges for equipment Schedules meetings Sets the philosophy and instills team spirit Is a good role model
15
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
16
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
17
FLL Core Values 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.
18
FLL Core Values Team Observations Tournament officials observe
teams during tournaments Looking for exceptional positive or
negative demonstrations of FLL Core Values
Observations can impact a team’s score either positively or negatively
19
No-Touch Rule Youngsters design, build, and program
their robots Youngsters are responsible for project
work During tournament, no adult may touch
the computer keyboard, mouse, robot, robot attachments, or project materials.
Giving verbal directives on programming and building or during table competition is a violation.
Same guidelines apply for team meetings
21
Team Registration National registration through FLL:
https://gofll.usfirst.org/ May through end of September or when max
reached $225 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!!
22
Purchases at FLL Registration Registration fee: $225 FLL Robot Set (NXT): $420 Field set-up kit: $65 Extra parts: rechargeable battery
and charger, motors, and sensors (light and touch)
They don’t ship until they are paid
23
ORTOP State Registration Takes place early October 2011 ORTOP Tournament fees
$75 for a Qualifying Tournament $50 for a Championship Tournament
We notify all coaches that have registered with FLL in Oregon and SW Washington Provide list of Qualifying Tournaments Ask for 3 Qualifying Tournament choices in
priority order We assign teams to Qualifying
Tournaments Register early!!
25
Minimum Resources to Start
A robotics kit A computer with Windows XP, Vista, or
Windows 7 (with Windows 7 use the latest NXT software V2.1)
A place to meet and practice Classroom Family room Garage Community Room
26
Additional Resources 2011 FLL “Food Factor” Field Setup kit (only
from FLL) Mission Model Set Field Mat
Practice table (design on FLL website) http://www.firstlegoleague.org/media/twocol.aspx?id=247
Click on Field Setup link 4’x8’ bottom 2x4 railing around the sides (extra 2x4 thickness
on one side for some Field Setup kit models) Overhead light is no longer required
27
Robotics Kit Info RCX-based kits
LEGO kit used by FLL in past years Can still be used in tournament in 2011 They will be phased out eventually
NXT-based kits Brand new in 2006 $420 if ordered during FLL registration Ship to registered teams starting in mid-May
28
Robotics Kit Info – NXT-Based FLL NXT -- $420
Only from FIRST® Complete kit with two tubs and sorting trays NXT software
LEGO Education NXT Base Set -- $279.95 http://www.legoeducation.us/store/detail.aspx?
ID=1263&c=0&t=0&l=0 Fewer parts with one tub and sorting trays No software
LEGO Retail -- $279.99 http://shop.lego.com/Product/?p=8547 Fewer parts with no sorting trays Includes NXT software
29
Allowed NXT Robot Parts NXT controller (1) Motors (3) Touch sensors (2) Light sensors (3) (FLL kit comes with
only 1! See next slide for more details) Lamp (1) Rotation sensors (3 minus the number
of NXT motors present) Ultrasonic sensor (1)
Be sure to consult the final FLL rules when they are released in Sept.
30
Allowed NXT Robot PartsLight Sensors The LEGO manufactured color sensor
is allowed The HiTechnic color sensor not allowed A color sensor comes in the retail kit
but not in the other two Any combination of color sensors and
regular light sensors totally 3 is allowed
Be sure to consult the final FLL rules when they are released in Sept.
31
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
32
Example Team Budget 2010 National Registration Fee: $225 2010 State Registration Fee: $75-125 2010 Robotics Kit: $420 2010 Field Setup Kit: $65 Materials for table: around $50 Misc. including batteries, shipping: $50-
$100 Total: $885-985
33
Possible Sources ofTeam 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
34
ORTOP Scholarships Funding should not be an obstacle
to a team’s participation Cover up to $800 in team costs Accepting applications now Awards made at least monthly Last date is September 15, 2011 http://ortop.org/fll/res.htm#schol
35
Scholarship Expectations Financial need based awards Coach/Mentor must attend all 3 ORTOP Workshops. Commit to holding at least one 90 minute meeting
a week to work on the FIRST® LEGO League Challenge from September until the Qualifying Tournament.
Team provides location to practice. Team provides computer with Windows XP or Vista Coach must bring team to Qualifying Tournament Coach must have an email address & phone and
promise to communicate with ORTOP. If coach does not continue past one year, robot kit
must be returned to ORTOP.
37
Meeting Organization How often and how long to meet
Most teams meet 1-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 ??
38
Team Kick-off Meeting Every child brings parent/guardian Set expectations with both Send kids off to build with LEGO parts
Get assistant to help Build with instructions, like the
Constructopedia or ORTOP assembly booklet
Something they can all do at once Explain the real situation to the
parents
39
Parent Involvement Explain program/FLL philosophy
Success = Participation Explain team rules (attendance,
respect, ...) Discuss participation commitment
for kids Review costs and funding sources Communicate about tournaments Solicit help
40
You Have A Team, Now What?
(Time Management) Divide the season
Build A Foundation Address the Challenge Get It Done Practice like the Tournament
41
(Approx) Field Challenge Timeline
Assume 12 week season (24 meetings) 4 weeks: Build Foundation 6 weeks: Complete Challenge 2 weeks: Practice / Minor changes You may need to adjust these
suggestions based on the time you have available to meet with your team
42
(Approx) ResearchProject Timeline
1 wk: Basic Research 2 wks: Narrow and Select Project Topic 1 wk: Focused Research 6 wks: Conduct Project / Prepare
Presentation 2 wks: Practice and Present to Others These tasks run concurrently with the
Field Challenge Timeline on the previous slide
43
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 One approach: use 5-10 minutes at start of
each meeting to introduce concepts Pick 1-2 subjects per session Can be more for first meetings / new teams May stop about ½ way thru season –
a bit late to incorporate new concepts unless they are stuck
44
Foundation: 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
45
Foundation: Mechanics Robot basics: have team build 2-3
different robots with instructions e.g. one per meeting Discuss “+”, “-” of designs Team decides/combines for challenge robot Gives team general robot building and
design tradeoff experience Build Field Kit
Dedicate 1 meeting, divide up elements Ad hoc extra meeting for leftovers
46
Foundation: Divide and conquer Three basic robot functions:
Locomotion: how the robot moves Concepts: motors, gears/pulleys, wheels/tracks,
friction, steering Navigation: how it knows where to go
Concepts: time, sensors (rotation, touch, light, ultrasonic)
Robotic Action: function it performs Concepts: pushing, grabbing, lifting , dumping
47
Foundation: Programming Introduce basic programming
Can use Workshop handouts Introduce sensors
If meetings start before Challenge is announced, can use mini-challenges to introduce concepts
Calibration of light sensor
48
Foundation: StructuredProblem Solving
Teach them elements of structured approach to solving large problems
Defining problem Brainstorming Evaluating alternatives Choosing alternative Implementing Evaluating & testing
49
Address the Challenge Pick up all information about the
challenge from FIRST® website when details announced in September Missions Rules Field setup Game Rulings (grows during the
season) Project
50
Address the Challenge Team must learn mission and rules:
Send home copy and learn missions and rules
Discuss and test understanding at later team meetings
Can overlap with ‘build foundation’ meetings
You might want to find a “rules expert” among your team members
51
Address the Challenge Have team group missions
Members brainstorm/generate prioritized list:
Can prioritize group by ease, location, or points
Can group by program or trips out of base Individuals present and team selects
which to start with Refer to team goals for how many to try Can add more if finish 1st set and still have
time
52
Address the Challenge Team decides how to divide
responsibilities A) Builders / Programmers B) Mission based (build/program by mission) C) ?? Need duplicate coverage for illness/absences
Probably want area specialists (build, program, research, etc.) BUT
Recommended ground rule: Everyone contributes to all aspects of team’s work
53
Get It DoneConsiderations: Introduce “design rule” concept
Shared, agreed upon design constants e.g. Motors B/C drive and motor C is on right Which end is ‘forward’ Light sensor is always in port ‘3’
Programs need to share inputs/outputs Attachments need to go together
Base robot with quickly interchangeable attachments, or Attachments can’t interfere with those for other missions
Target being done early (time for debug/rebuild)
54
Practice Like the Tournament Field Competition Runs (tournament rules)
Start with individual missions/groups, then all together
2 ½ min, 2 members at the table at once
Practice working under time pressure Switching between missions, programs
Try to limit big last minute changes to missions/robot
55
Practice Like the Tournament Judging Panels (Robot Design, Project, Core
Values)
Use Coach Handbook rubrics Parents as judges Work on smooth, clear delivery Ask a variety of questions Practice teamwork exercises
56
Budgeting Resources Physical resource effectiveness limits:
No more than 2 (3 max) at one keyboard No more than 2-3 building one item Can’t research presentation and program
robot on same computer at same time Consider time sharing
2 computers, one robot kit; divide team 1/3 building, 1/3 programming, 1/3 researching Rotate during meeting
57
1st Team Meeting: Getting Started
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, practice
58
Sample Team Goals Scale to experience level of team Samples
Learn to program (...learn to use subroutines)
Learn about (topic of year) Participate in tournament Complete at least 1 mission (more for
experienced teams) Everyone participates HAVE FUN!
59
Set Expectations For a Positive Tone
Encourage risk taking It’s OK to fail – they are learning
opportunities 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
60
Final Advice Keep Meetings Fun
Usually means hands on LEGO building every meeting Be flexible
Help keep them on task, but ultimately it is their project
The journey is as important as the result Watch for teaching moments
Engineers need ‘hard skills’ Mechanical Design, Programming, Analysis, Problem
Solving, Experimentation, and Documentation AND ‘soft skills’
Timeliness, Teamwork, Tact and Compromise, Confidence, Courtesy, Perseverance, and Planning
62
Robot Design Judging 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
63
Project Judging Another good learning opportunity
Research skills and presentation skills (remember the marketing kid? )
Good engineering requires research and communication
Must be a live presentation Format – includes setup time
5 minute presentation, 5 minute interview Posterboards, skits, models, Powerpoint (not
the best format, can waste time with setup), . . .
64
Core Values Judging A separate 10 minute judging
session No presentation is expected Teams will do a surprise teamwork
activity Judges interact with teams to
evaluate how the teams meet the FLL Core Values
65
Sources of ideas Constructopedias/Manuals/Guides NXT Software Tutorial –
http://www.ortop.org/NXT_Tutorial/ Books – http://ortop.org/fll/res.htm#books Web – http://www.ortop.org/fll/res.htm#links
LEGO website FIRST®
INSciTE -- Minnesota FLL Tufts University – Inventor of Robolab
Not all resources are NXT specific – still useful for general techniques
Art of LEGO CMU (Carnegie
Mellon University)
66
Names of Parts Google: lego part names guide.lugnet.com/partsref shop.lego.com/pab (Pick a Brick)
6704/18/23 NXT Robotics Techniques - 2009 67
CanDo Challenge Discussion Simple project, but good learning tool Unexpected things happen – cans get caught
under the wheel, it goes the “wrong” direction
Take it in smaller steps – “Let’s see what happens before it hits a can”
Mechanical problems may do you in Clarify the “rules” – know the requirements Experiment – “Just go try it. We can rework
it.” Keep it simple