33
Robot Design Judge Preparation Pack All Tournaments
Robot Design Judge
Preparation Pack All Tournaments
Robot Design Judge Preparation Pack Table of Contents
FIRST® Core Values
10 Things to Know as a FIRST LEGO League Judge
Robot Design Judging Primer
Robot Design Rubric
What to Expect as a Judge: Day of the Event
Judging Process
FIRST LEGO League Awards
Robot Design Sample Questions
Comment Starters
The Challenge and Challenge Guide
Challenge Updates
FIRST Core Values
We express the FIRST philosophies of Gracious
Professionalism® and Coopertition® through our Core Values:
Discovery: We explore new skills and ideas.
Innovation: We use creativity and persistence to solve
problems.
Impact: We apply what we learn to improve our world.
Inclusion: We respect each other and embrace our
differences.
Teamwork: We are stronger when we work together.
Fun: We enjoy and celebrate what we do!
10 Things to Know as a FIRST® LEGO® League Judge Please be sure to check out www.firstlegoleague.org for additional information, including Judging Q & A from throughout the season: FIRST LEGO League Challenge: www.firstlegoleague.org/challenge
Judging Questions: [email protected]
Thank you for agreeing to be a judge with FIRST LEGO League. The information in this packet is designed to help you prepare as a judge this season. It is intended to offer background information that will be useful to review prior to your tournament. You should also participate in training sessions that may be offered through your local tournament organizer and/or FIRST LEGO League. We hope your experience as a judge is rewarding and enjoyable!
10. Have fun – you and the kids The most important thing to know about a FIRST LEGO League tournament is that it is supposed to be FUN. The mission of FIRST is to get kids excited about science and technology. A competition is a celebration of what the children have accomplished throughout the season. It should be serious and competitive, but not so much that the fun is lost.
9. Exhibit Gracious Professionalism and honor FIRST Core Values These are the basic foundations of FIRST LEGO League, and should always be at the forefront in everyone’s minds. We offer specific awards to recognize Core Values excellence, but a significant concern can impact team eligibility in any award category.
8. Be a good role model for technology and engineering careers Give the kids a chance to see what makes engineers, scientists, computer programmers and educators special. Share your experiences without sharing your agendas. Be professional – show the kids that what they have accomplished is appreciated and valuable. Show interest in their presentations and discussions, and be personable.
7. Respect the children Please keep negative comments to yourself, away from the ears of the kids, parents, and coaches. All teams should be given the benefit of the doubt when questions arise about adult involvement. If you suspect the kids did not do the work, it is your job to probe further to prove it, rather than assuming the kids did not do the work. Remember that these are kids who worked hard all season to make it to the tournament. Treat their accomplishments with respect, and be sure that other judges do so as well. One negative comment from a judge can have a devastating effect on teams. Make it your goal as a judge to ensure that the teams know what they did well, and that they have a positive experience showcasing their achievements.
6. Respect the judging process Stay on schedule. The kids have a more challenging schedule than you do. Remember the FIRST LEGO League
awards philosophy. Remember that the whole judging process is subjective. Concentrate on providing a great experience for the kids and try not to get caught up in the mechanics of the process. Do not share scores or awards discussions with the kids, coaches or parents.
5. Evaluate teams completely and fairly Each rubric is designed to evaluate many areas of a team’s performance, and gives equal weighting to several factors tied to specific awards. All Required Awards are of equal importance, except for our Champion’s Award that recognizes all-around excellence. Be objective, both on a team-by-team basis and a total rubric evaluation basis. Familiarize yourself with the levels of achievement. Identify any conflicts of interest you have before the competition, and refrain from involving yourself in discussions about any team when you have a conflict. 4. Consider age appropriateness and experience Consider age when evaluating teams. Certain skills, knowledge, and capabilities are more likely to be exhibited by the kids as they get older and more experienced in general and in FIRST LEGO League in particular. You may also see rookie teams that are more polished and understand FIRST LEGO League better than experienced teams. 3. Reward excellence and celebrate achievement For a team to be considered for an award, they should be evaluated at an Exemplary level of achievement in that category whenever possible. Award distribution is spread as equitably as possible among the teams, with the goal of no team winning more than one judged award. 2. Provide specific and constructive feedback
Please be specific when providing feedback comments to teams. This will also help when it comes to awards deliberations – specific examples are very helpful when differentiating between teams. “This team’s willingness to help other teams (by providing programming mentorship, for example) is exemplary” is more descriptive and helpful than “that team was so nice and polite and exhibited gracious professionalism.” Take lots of notes if you need to! 1. See #10 again
Robot Design Judging Primer
© 2018 For Inspiration and Recognition of Science and Technology (FIRST®) and The LEGO Group. Used by special permission. All rights reserved.
Robot Design judging in FIRST® LEGO® League can be compared to an engineering design review in the
“real world.” Design teams present their robots to panels tasked with selecting the robots that best meet the
requirements (completion of missions) given constraints like size, parts usage and software. The natural
inclination for engineers and technical people is to say, “There is an easy test to see which robots are best –
the competition!” However, in FIRST LEGO League, and often in the “real world,” decisions are made based
on how well a team can explain their design and all the things they considered while developing it. The FIRST
LEGO League Robot Design rubric represents a set of criteria that we feel are important “takeaways” from
participating in the design of a FIRST LEGO League competition robot. They are analogous to evaluation
criteria used when selecting between competing designs. Judges gather information about teams’ mechanical
design, programming and overall design process to evaluate a team and its robot.
As a Judge, here are some overall things to consider:
The Robot Design judging session is more about the team's ability to present the robot and all the
thoughts and considerations that went into their final product than it is about its performance. The
performance is covered under the Robot Performance Award. The judging session is the time for the
Judges to learn from the teams the design processes they used to make decisions and gain
understanding; it also allows discussion so that Judges can be sure that the teams did the work.
You may ask teams to perform missions with their robot on the Robot Game table, if one is provided in
your judging room. Give teams the benefit of the doubt should these missions not work successfully all
the time. Judging tables and field setup kits are not usually built or maintained to the same standards
as competition ones. There is also a tendency for Murphy’s Law to rule in these sessions and for
teams to be nervous and mistake prone when running missions in a judging setting.
Teams may bring additional prototypes of their robot or attachments into a judging session.
Sometimes these prototypes utilize additional electrical parts beyond those allowable in competition.
Remember that electrical parts and software rules apply only to the robot used in the competition itself,
and that extra parts or software used by teams to demonstrate designs are perfectly allowable.
Simpler is usually better. Don’t be overly impressed with complicated robots. The complication must be
used for a purpose.
Remember that this is an engineering challenge for autonomous robots. Small imperfections in the
field, mission models and environmental variations must be considered by Accomplished and
Exemplary teams.
Mechanical Design Durability – The robot should be able to withstand the rigors of the competition, for example it should be able
to contact walls or mission models without pieces falling off or breaking. Attachments should be similarly
robust. Long arms that delicately grip a lever aren’t very effective if they don’t stay attached to the robot.
Mechanical Efficiency – Here the Judges are looking for robot structures and attachments which show a
judicious use of parts. For example, using six pins to tie two beams together is not as efficient as using one at
each end. One note here: don’t over penalize the teams for adding small bits of “flair” or pieces that are fun for
them to use to express their creativity. Remember the Core Value “We have fun!”
Mechanization – Judges look here for how the robot moves and operates. They look to see whether the
robot balances speed and power.
Programming Just as with Mechanical Design, simplicity is desired when it comes to programs. Teams can develop
amazing programs that aren’t necessarily better than simple programs that perform the same purpose.
Programming Quality – The robot’s programs should work consistently, producing the same results every
time. Examples of quality code could include audible checks or a simplified menu system that teams use to
make sure they are running the appropriate section of code for a particular mission. Be careful to attempt to
assess how the robot’s programs would operate independent of mechanical faults.
Programming Efficiency – The goal here is to encourage teams to develop code that is modular, portable
and flexible, so that it can be used in multiple situations. This criterion also addresses readability and
documentation of code, both of which are good programming practices.
Automation/Navigation – Autonomy in FIRST LEGO League means that the robot operates with minimal
driver intervention. Retrieving a robot and taking a touch penalty may be part of an acceptable strategy for a
team, but it is still driver intervention. So for this instance, a team might have an Accomplished Mission
Strategy, but only score Developing for Automation. This criterion also doesn’t distinguish between sensor
use/feedback and mechanical feedback. For example, it is valid for a team to use an aligning jig in base
followed by a robot using the wall or a mission model to align itself before activating an attachment. It is also
just as valid for a team to use a light sensor to follow a line to the same mission model. Teams should try to
avoid just using driver aiming, motor rotations and timing to navigate the field, as these methods often
become unreliable under variations in field or environmental conditions. Remember that lack of sensors isn’t
necessarily a bad thing. Lack of Automation, however, should be considered.
Strategy & Innovation Remember that Strategy and Innovation can be seen in Mechanical Design or Programming, as well as the
integration of both.
Design Process – Accomplished teams move beyond a trial and error approach to robot improvements to
utilize testing cycles where systematic processes are used. Frequently you will hear teams say, “We tried a lot
of different things and this one was the best.” You are looking for more details and more organization to their
process than that for teams who are Accomplished or Exemplary.
Mission Strategy – This is fairly straightforward. Judges can ask teams, “What is your strategy to complete
the missions?” and “How did you make decisions to support that strategy when designing your robot?”
Innovation – This is often a hard area for Judges to judge. Things to be on the lookout for here include
creativity, uniqueness, a cool attachment or programming trick, or something similar. Most competitions will
have one or more robots that will have some feature that captures the Judges’ attention. Remember that
Innovation implies added benefit, so make sure that the team can state the benefits of their cool feature.
Robot Design Team Number _____________
Judging Room _____________
© 2018 For Inspiration and Recognition of Science and Technology (FIRST®) and The LEGO Group. Used by special permission. All rights reserved.
Directions: For each skill area, clearly mark the box that best describes the team's accomplishments. If the team does not demonstrate skill in a particular area, then put an 'X' in the first box for Not Demonstrated (ND). Please provide as many written comments as you can to acknowledge each team’s hard work and to help teams improve. When you have completed the evaluation, please circle the team’s areas of strength.
Beginning Developing Accomplished Exemplary
Me
ch
an
ical
De
sig
n
Durability Evidence of structural integrity; ability to withstand rigors of competition
ND
quite fragile; breaks a lot frequent or significant
faults/repairs rare faults/repairs
sound construction; no repairs
Mechanical Efficiency Economic use of parts and time; easy to repair and modify
ND
excessive parts or time to repair/modify
inefficient parts or time to repair/modify
appropriate use of parts and time to repair/modify
streamlined use of parts and time to repair/modify
Mechanization Ability of robot mechanisms to move or act with appropriate speed, strength and accuracy for intended tasks (propulsion and execution)
ND
imbalance of speed, strength and accuracy on
most tasks
imbalance of speed, strength and accuracy on
some tasks
appropriate balance of speed, strength and
accuracy on most tasks
appropriate balance of speed, strength and
accuracy on every task
Com
ments
: P
rog
ram
min
g
Programming Quality Programs are appropriate for the intended purpose and would achieve consistent results, assuming no mechanical faults
ND
would not achieve purpose AND would be inconsistent
would not achieve purpose OR would be inconsistent
should achieve purpose repeatedly
should achieve purpose every time
Programming Efficiency Programs are modular, streamlined, and understandable
ND
excessive code and difficult to understand
inefficient code and challenge to understand
appropriate code and easy to understand
streamlined code and easy for anyone to understand
Automation/Navigation Ability of the robot to move or act as intended using mechanical and/or sensor feedback (with minimal reliance on driver intervention and/or program timing)
ND
frequent driver intervention to aim AND retrieve robot
frequent driver intervention to aim OR retrieve robot
robot moves/acts as intended
repeatedly w/ occasional
driver intervention
robot moves/acts as intended every time with no
driver intervention
Com
ments
: S
tra
teg
y &
In
no
va
tio
n Design Process Ability to develop and explain improvement cycles where alternatives are considered and
narrowed, selections tested, designs improved (applies to programming as well as mechanical design)
ND
organization AND explanation
need improvement
organization OR explanation
need improvement
systematic and well-explained
systematic, well-explained and well-documented
Mission Strategy Ability to clearly define and describe the team's game strategy
ND
no clear goals AND no clear strategy
no clear goals OR no clear strategy
clear strategy to accomplish
the team's well defined goals
clear strategy to accomplish
most/all game missions
Innovation Creation of new, unique, or unexpected feature(s) (e.g. designs, programs, strategies or applications) that are beneficial in performing the specified tasks
ND
original feature(s) with no added value or potential
original feature(s) with some
added value or potential
original feature(s) with the potential
to add significant value
original feature(s) that add significant value
Com
ments
:
Strengths: Mechanical Design Programming Strategy & Innovation
What to Expect as a Judge
Day of the Event
Before Judging
Sessions
• Meet with the Judge
Advisor to review
• Event schedule
• Judging
procedures
• Judging
Deliverables
• Last minute items
• Meet your judging
partner(s) and the rest
of the panel
• Attend the Opening
Ceremonies
During Team
Evaluations
• Interview teams
• Make sure sessions
stay on schedule
• Evaluate each team
according to rubric
criteria and note
constructive
comments
• Keep additional notes
of team specifics if
needed
• Note and report:
• cases of adult
intervention
• demonstrations
of Core Values
During
Deliberations
• Submit award
nominations and
rankings by your
judging pair
• Participate with all
area Judges to
determine award
candidates/merged
preliminary ranking
• Work with Judges of
other areas to
determine the
Champion’s Award
winner(s)
• Work with all Judges
to finalize remaining
awards and prepare
scripts
During the Awards
Ceremony
• Attend the Awards
Ceremony (if
possible)
• Help distribute
medals, awards and
other team
recognition
• Join the high-five line,
congratulate all teams
and have fun!
The Judging Process
Awards Ceremony
Develop script & distribute awards
Final Deliberations
Determine Champion’s then all other award winners
Initial Deliberations
Determine preliminary rankings for each area award
Call-Backs and Additional Information
Review and discuss top teams
Nominate and Rank Teams
Determine top teams seen by each pair
Judging Sessions
Evaluate teams; Provide feedbackJudging
Pairs
Three
Judging
Areas
All
Judges
You will work
with other
Judges
throughout
the
tournament
using FIRST
LEGO
League’s
process to
evaluate
teams and
determine
awards
Note that you
may work
with different
Judges at
different
times
During Team
Evaluation and
Feedback, the
Judges focus on
evaluating each
team and
providing them
with constructive
feedbackTeam
Evalu
ati
on
an
d
Fe
ed
ba
ck
Aw
ard
s D
eli
bera
tio
ns
During Awards
Deliberations,
the Judges focus
on determining
the teams
worthy of awards
and recognition
3
The Judging Process
Completed Rubrics +
Comments – 1 per
room
Judging Sessions
1
Champion’s Candidates
Selected by JA/HJ
Select
Champion’s
Candidates
3
1-N Ranking for Each
Award in Each Area
Initial
Deliberations
6
Discuss Champion’s
Candidates
7Finalize
Remaining
Required
Awards
9
Ju
dg
ing
Pa
irs
All
Ju
dg
es
Ju
dg
e A
dv
iso
r F
acilit
ate
s
Discuss Award
Candidates
5
Call Backs
4
Optional
Individual Award Nominations
– ~2 per room
1-N Ranking for Overall
Area – 1 per room
Nominate
& Rank
Teams
2
Ind
ivid
ua
l J
ud
gin
g
Are
as
Head
Ju
dg
es F
acilit
ate
Ju
dg
e A
dvis
or
&
Hea
d J
ud
ges
Vote for
Champion’s
Award
8
Number dependent on
tournament size
Finalize
Optional
Awards
10
Scripts for All Awards
Written Feedback to
All Teams
FIRST® LEGO
®
League
Awards
© 2018 For Inspiration and Recognition of Science and Technology (FIRST®) and The LEGO Group. Used by special permission. All rights reserved.
All Awards Structures
Champion’s Award This award recognizes a team that embodies the FIRST LEGO League experience, by fully embracing our
Core Values while achieving excellence and innovation in both the Robot Game and Project. Considered the
most prestigious, the Champion’s Award is included in both approved awards structures.
Robot Performance This award recognizes a team that scores the most points during the Robot Game. Teams have a chance to
compete in at least three 2.5 minute matches and their highest score counts.
Judges Awards During the course of competition the judges may encounter teams whose unique efforts, performance or
dynamics merit recognition. Some teams have a story that sets them apart in a noteworthy way. Sometimes a
team is so close to winning an award that the judges choose to give special recognition to the team. Judges
Awards allow the freedom to recognize remarkable teams that stand out for reasons other than the Core
Award categories. Examples include:
Against All Odds or Overcoming Adversity or Perseverance
This award goes to the team that improvises and overcomes a difficult situation while still making a
respectable showing, with an attitude that shows, “We can overcome incredible odds if we never give
up, no matter what!”
Rising Star
This award recognizes a team that the judges notice and expect great things from in the future.
Special Recognition Awards
Outstanding Volunteer Award
The FIRST LEGO League program would not exist without its volunteers. This award honors an
extraordinary volunteer(s) whose dedication to FIRST LEGO League has a positive impact on the
team experience.
Coach/Mentor Award
Coaches and mentors inspire their teams to do their best, both as individuals and together. This
award goes to the coach or mentor whose leadership and guidance is clearly evident and best
exemplifies the FIRST LEGO League Core Values.
Full Awards Structure
Required for all Championship events; an option for qualifying tournaments
Core Values Awards
Inspiration
This award celebrates a team that is empowered by their FIRST LEGO League experience and
displays extraordinary enthusiasm and spirit.
Teamwork
This award recognizes a team that can accomplish more together than they could as individuals
through shared goals, strong communication, effective problem solving and excellent time
management.
Gracious Professionalism®
This award recognizes a team whose members show each other and other teams respect at all times.
They recognize that both friendly competition and mutual gain are possible, on and off the playing
field.
Project Awards
Research
This award recognizes a team that utilizes diverse resources to formulate an in-depth and
comprehensive understanding of the problem they have identified.
Innovative Solution
This award recognizes a team’s solution that is exceptionally well-considered and creative, with good
potential to solve the problem researched.
Presentation
This award recognizes a team that effectively communicates the problem they have identified and their
proposed solution to both the judges and other potential supporters.
Robot Awards
Mechanical Design
This award recognizes a team that designs and develops a mechanically sound robot that is durable,
efficient and highly capable of performing challenge missions.
Programming
This award recognizes a team that utilizes outstanding programming principles, including clear,
concise and reusable code that allows their robot to perform challenge missions autonomously and
consistently.
Strategy & Innovation
This award recognizes a team that uses solid engineering practices and a well-developed strategy to
design and build an innovative, high performing robot.
Consolidated Awards Structure An option for qualifying tournaments
Project Award
This award recognizes a team that excels across the Research, Innovative Solution and Presentation
categories. This team utilized diverse resources for their Project to help them gain a comprehensive
understanding of the problem they identified, develop a creative, well-researched solution and effectively
communicate their findings to judges and the community.
Core Values Award
This award recognizes a team that excels across the Inspiration, Teamwork and Gracious Professionalism®
categories. This team displays extraordinary enthusiasm and spirit, knows they can accomplish more together
than they could as individuals, and shows each other and other teams respect at all times.
Robot Design Award
This award recognizes a team that excels across the Mechanical Design, Programming and Strategy &
Innovation categories. This team uses outstanding programming principles and solid engineering practices to
develop a robot that is mechanically sound, durable, efficient and highly capable of performing challenge
missions.
Robot Design
Sample Questions
Durability
How did you get your robot to stay together?
How often does your robot fall apart? What happens and have you thought about ways to fix
this?
Mechanical Efficiency
Would it be possible to use fewer pieces or components for your robot and still accomplish the
same missions?
If your robot has attachments, tell us about them.
Mechanization
Tell us about how your robot uses attachments or other mechanisms to complete missions.
Describe how your robot moves from place to place, or overcomes obstacles, and balances
speed and power.
Programming Quality
What program do you feel is your best? Why?
Do your robot’s programs achieve the same result every time? If not, why do you think this
might happen?
Programming Efficiency
What did you do to make your programs more understandable and easier to use?
What mission is your favorite? Explain the steps in the program for that mission.
Automation/Navigation
Would you explain how your robot turns (or travels a specific distance, or goes from base to a
specific destination)? How satisfied are you with this?
As your robot moves around the field, was there one area that was more difficult to navigate
than another? If so, what did your team do to overcome this challenge?
Would you explain which sensors you used, and how and why you used them?
Would you explain how your robot knows where it is on the field? Note: Sensing includes not
only touch and rotation sensors, but time (timers in the RCX) and passive sensing such as
referencing to walls or other objects, etc.
Design Process
What was the greatest design or programming difficulty you encountered? How did you solve
that problem?
How did you test your designs?
Describe one way your robot got better over the course of the season.
Mission Strategy
How did your team decide which missions to tackle?
How many of the missions has this robot completed successfully in a single match (includes a
tournament match, a tournament practice, or home practice)?
We want to consider the overall strategy behind your robot’s design. Tell us about your robot,
its attachments and sensors and the missions the robot attempts so that we will understand
your team’s design strategy.
Which attachments are most difficult to put on and/or take off?
Innovation
What part of your design, program or strategy do you think is unique to your team?
How did you come up with the idea?
Look For:
Unusual strategy, programming or design.
Propulsion or steering methods or functional aspects that no one else has or you are
surprised someone would try.
Robot is able to effectively perform the same task over and over.
Parts or functional aspects that make something difficult look very easy.
Parts or mechanisms that perform several functions.
Propulsion, steering methods or functional aspects that work, but children have no
understanding how.
Children can describe what the robot will do based on the program.
Does the team look to the coach for answers or are they focused on the robot and Judges?
Noteworthy observations about Core Values to share with the judging team.
Comment Starters
The best comments on FIRST LEGO League rubrics include at least one item the team did well and one challenge or item for improvement. Use these starters and key words to help you write meaningful comments appropriate for FIRST LEGO League teams. Be sure cite evidence or examples and explain to teams why they received the levels you marked (Beginning, Developing, Accomplished, Exemplary).
Positive Include at least one positive in each comment box.
Improvement Needed Include at least one item to improve in each comment box.
We liked how you…
Excellent job on…
Thanks for telling us about…
________ was an innovative way to
accomplish…
Your (diagram/poster/etc.) helped us
understand your …
We appreciated that you…
________ was an effective way to…
________ showed us how your team…
Your approach to…
_______ was an example of how your
team…
Your team worked through…
Your ______ process helped your team…
We would have liked to hear more
about…
Your (project/robot/etc.) could be even
better if you…
How could you change your design to
improve…?
It seemed like your team struggled with…
We were still a little confused by…
Consider changing…
Think about…
Maybe you could add…
One suggestion would be…
We noticed that…
We weren’t sure how…
_________ could have been clearer.
Some words to inspire your comment writing:
Challenging
Consistent
Demonstrate
Decide / decision
Describe
Disciplined
Display
Especially
Example
Explain
In particular
Process
Resourceful
Show
Solve
Specifically
Strategy
Strength
Thorough
Try
Wonder
Solve problems in: The Robot Game ĥ Read the Robot Game Rules in the Challenge Guide
ĥ Identify one or more Missions to solve
ĥ Design a Robot using LEGO® MINDSTORMS® that can solve the Mission(s)
Missions as written below are only an overview. For full detail, go to http://www.firstlegoleague.org/challenge and download the complete Challenge Guide.
Scoring Requirement Signals ĥ Within the Mission descriptions, specific scoring requirements are written in GREEN.
ĥ Methods with an asterisk ✱ must be the ONLY ones used, and must be OBSERVED by the referee.
ĥ Underlined RESULTS/CONDITIONS must be visible at the END of the match.
M01–Space Travel ✱ Start each Payload clearly rolling down the Space Travel Ramp.
• For each roll, the cart must ✱ be Independent by the time it reaches the first track connection.
• Vehicle Payload: 22 Points
• Supply Payload: 14 Points
• Crew Payload: 10 Points
As a Mission requirement in any Mission, the word “Independent” means “not in contact with any of your Equipment.” As long as the cart clearly rolls Independently past the First Track Connection, it’s OK if it doesn’t roll all the way east.
M02–Solar Panel Array • Both Solar Panels are Angled toward the same Field: 22 Points For Both Teams
• Your Solar Panel is Angled toward the other team’s Field: 18 Points
M03–3D Printing • Eject the 2x4 Brick ✱ by placing a Regolith Core Sample into the 3D Printer.
• The 2x4 Brick ejected and completely in the Northeast Planet Area: 22 Points
• OR The 2x4 Brick ejected and not completely in the Northeast Planet Area: 18 Points
M04–Crater Crossing • All weight-bearing features of the crossing equipment must cross ✱ completely between the towers.
• Crossing must be ✱ from east to west, and make it completely past the flattened Gate: 20 Points
M05–Extraction • Move all four Core Samples so they are no longer touching the axle that held them in the Core Site Model: 16 Points
• Place the Gas Core Sample so it is touching the mat, and completely in the Lander’s Target Circle: 12 Points
• OR Place the Gas Core Sample completely in Base: 10 Points
• Place the Water Core Sample so it is supported only by the Food Growth Chamber: 8 Points
M06–Space Station Modules • Inserted Modules must not be touching anything except the Habitation Hub.
• Move the Cone Module completely into Base: 16 Points
• Insert the Tube Module into the Habitation Hub port, west side: 16 Points
• Transfer/Insert the Dock Module into the Habitation Hub port, east side: 14 Points
M07–Space Walk Emergency • Move Gerhard so his body is inserted at least partly into the Habitation Hub’s Airlock Chamber.
• Completely In: 22 Points
• OR Partly In: 18 Points
For this Mission, the word “Body” includes all parts except the loop.
M08–Aerobic Exercise • Advance the Exercise Machine’s Pointer along its Dial ✱ by moving one or both of the Handle Assemblies.
• Get the Pointer tip completely in orange, or partly covering either of orange’s end-borders: 22 Points
• OR Get the Pointer tip completely in white: 20 Points
• OR Get the Pointer tip completely in gray, or partly covering either of gray’s end-borders: 18 Points
M01
M02
M03
M06
M08
M10
M11
M13
M14
M12
M15M09
M07
M04
M05
M09–Strength Exercise • Lift the Strength Bar so the tooth-strip’s 4th hole comes at least partly into view as shown: 16 Points
M10–Food Production • Spin the Food Growth Chamber’s colors so the gray weight is DROPPED after green, but before tan, ✱ by moving the Push Bar: 16 Points
M11–Escape Velocity • Get the spacecraft to go so fast and high that it stays up, ✱ by pressing/hitting the Strike Pad: 24 Points
M12–Satellite Orbits • Move any part of a Satellite on or above the area between the two lines of the Outer Orbit: 8 Points Each
M13–Observatory • Get the pointer tip completely in orange, or partly covering either of orange’s end-borders: 20 Points
• OR Get the pointer tip completely in white: 18 Points
• OR Get the pointer tip completely in gray, or partly covering either of gray’s end-borders: 16 Points
M14–Meteoroid Deflection • Send Meteoroids ✱ over the Free-Line to touch the mat in the Meteoroid Catcher.
• The Meteoroids must be hit/released while they are ✱ clearly and completely west of the Free-Line.
• While between hit/release and scoring position, the Meteoroid ✱ must be clearly Independent.
• Meteoroids in the Center Section: 12 Points Each
• Meteoroids in Either Side Section: 8 Points Each
If ever the Ring-Set Meteoroid is off its Ring, you may remove the Ring from the Field by hand (this is a special exception to the Rules).
M15–Lander Touch-Down • Move the Lander to be intact, touching the Mat, and completely in its Target Circle: 22 Points
• OR Move the Lander to be intact, touching the Mat, and completely in the Northeast Planet Area: 20 Points
• OR Move both parts of the Lander completely into Base: 16 Points
The Lander is “Intact” if its parts are connected by at least two of its four tan location axles.
What does it take to live on a space station or travel to another planet? Can you and your team create the critical innovation that will get earthlings to Mars? We can learn so much from overcoming the challenges of space exploration if you are willing to go INTO ORBITSM and beyond with FIRST® LEGO® League!
The Robot Game Missions can provide real-world examples for your Project research. Learn about the stories behind the Missions in the Challenge Guide.
P01–Interruption Penalties • If you ✱ Interrupt the Robot: Minus 3 Points Each Time
• Upon Penalty, the referee will place one Penalty Disc in the southeast triangle as a permanent Interruption marker. You can get up to six such Penalties.
• If a Penalty Disc comes off the triangle, it is simply returned, with no effect on score.
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 19
Robot Game RulesGuiding PrinciplesGP1 - GRACIOUS PROFESSIONALISM® You are “Gracious Professionals.” You compete hard against problems, while treating all people with respect and kindness. If you joined FIRST LEGO League with a main goal of “winning a robotics competition,” you’re in the wrong place!
GP2 - INTERPRETATION • If a detail isn’t mentioned, then it doesn’t matter.
• Robot Game text means exactly and only what it plainly says.
• If a word isn’t given a game definition, use its common conversational meaning.
GP3 - BENEFIT OF THE DOUBT If the referee feels something is a “very tough call,” and no one can point to strong text in any particular direction, you get the Benefit Of The Doubt. This good-faith courtesy is not to be used as a strategy.
GP4 - VARIABILITY Our suppliers and volunteers try hard to make all Fields correct and identical, but you should always expect little defects and differences. Top teams design with these in mind. Examples include Border Wall splinters, lighting changes, and Field Mat wrinkles.
GP5 - INFORMATION SUPERIORITY If two official facts disagree, or confuse you when read together, here’s the order of their authority (with #1 being the strongest):
#1 = Current Robot Game UPDATES#2 = MISSIONS and FIELD SETUP#3 = RULES#4 = LOCAL HEAD REFEREE In unclear situations, local head
referees may make good-faith decisions after discussion, with Rule GP3 in mind.
• Pictures and video have no authority, except when talked about in #1, #2, or #3.
• Emails and Forum comments have no authority.
DefinitionsD01 - MATCH A “Match” is when two teams play opposite each other on two Fields placed north to north.
• Your Robot LAUNCHES one or more times from Base and tries as many Missions as possible.
• Matches last 2-1/2 minutes, and the timer never pauses.
D02 - MISSION A “Mission” is an opportunity for the Robot to earn points. Requirements are written in the form of
• RESULTS that must be visible to the referee at the END OF THE MATCH.
• METHODS that must be observed by the referee AS THEY HAPPEN.
D03 - EQUIPMENT “Equipment” is everything YOU BRING to a Match for Mission-related activity.
D04 - ROBOT Your “Robot” is your LEGO® MINDSTORMS® controller and all the Equipment you’ve combined with it by hand which is not intended to separate from it, except by hand.
D05 - MISSION MODEL A “Mission Model” is any LEGO® element or structure ALREADY AT THE FIELD when you get there.
D06 - FIELD The “Field” is the Robot’s game environment, consisting of Mission Models on a Mat, surrounded by Border Walls, all on a Table. “Base” is part of the Field. For full details, see FIELD SETUP.
D07 - BASE “Base” is the space directly above the Field’s quarter-circle region, in the southwest. It extends southwest from the outside of the thin curved line TO the corner walls (no farther). The thin line around any scoring area counts as part of that area. When a precise location related to a line is unclear, the outcome most favorable for the team is assumed. (See diagram below.)
D07 - BASE
Completely In Benefit Of The Doubt Partly In Partly In Partly In Benefit Of The Doubt Out
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 20
D08 - LAUNCH Whenever you’re done handling the Robot and then you make it GO, that’s a “Launch.”
D09 - INTERRUPTION The next time you interact with the Robot after Launching it, that’s an “Interruption.”
D10 - TRANSPORTED When a thing (anything) is purposefully/strategically being
• taken from its place, and/or
• moved to a new place, and/or
• being released in a new place,
it is being “Transported.” The process of being Transported ends when the thing being transported is no longer in contact with whatever was transporting it.
Equipment, Software, and PeopleR01 - ALL EQUIPMENT All Equipment must be made of LEGO-made building parts in original factory condition. Except: LEGO string and tubing may be cut shorter.
Except: Program reminders on paper are OK (off the Field).
Except: Marker may be used in hidden areas for identification.
R02 - CONTROLLERS You are allowed only ONE individual controller in any particular Match. • It must exactly match a type shown below (Except: Color).
• ALL other controllers must be left in the PIT AREA for that Match.
• All remote control or data exchange with Robots (including Bluetooth) in the competition area is illegal.
• This rule limits you to only ONE individual ROBOT in any particular Match.
EV3 NXT RCX
R03 - MOTORS You are allowed up to FOUR individual motors in any particular Match. • Each one must exactly match a type shown below.
• You may include more than one of a type, but again, your grand total may not be greater than FOUR.
• ALL other motors must be left in the PIT AREA for that Match, NO EXCEPTIONS.
EV3 “LARGE” EV3 “MEDIUM” NXT RCX
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 21
R04 - EXTERNAL SENSORS Use as many external sensors as you like. • Each one must exactly match a type shown below.
• You may include more than one of each type.
EV3 TOUCH EV3 COLOR EV3 ULTRASONIC EV3 GYRO/ANGLE
NXT TOUCH NXT LIGHT NXT COLOR NXT ULTRASONIC
RCX TOUCH RCX LIGHT RCX ROTATION
R05 - OTHER ELECTRIC/ELECTRONIC THINGS No other electric/electronic things are allowed in the competition area for Mission-related activity. Except: LEGO wires and converter cables are allowed as needed. Except: Allowable power sources are ONE controller’s power pack or SIX AA batteries.
R06 - NON-ELECTRIC ELEMENTS Use as many non-electric LEGO-made elements as you like, from any set. Except: Factory-made wind-up/pull-back “motors” are not allowed. Except: Additional/duplicate Mission Models are not allowed.
R07 - SOFTWARE The Robot may only be programmed using LEGO MINDSTORMS RCX, NXT, EV3, or RoboLab software (any release). No other software is allowed. Patches, add-ons, and new versions of the allowable software from the manufacturers (LEGO and National Instruments) are allowed, but tool kits, including the LabVIEW tool kit, are not allowed.
R08 - TECHNICIANS • Only two team members, called “Technicians,” are allowed at the competition Field at once.
Except: Others may step in for true emergency repairs during the Match, then step away.
• The rest of the team must stand back as directed by tournament officials, with the expectation of fresh Technicians being able to switch places with current Technicians at any time if desired.
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 22
PlayR09 - BEFORE THE MATCH TIMER STARTS After getting to the Field on time, you have at least one minute to prepare. During this special time only, you may also • ask the referee to be sure a Mission Model or setup is correct, and/or
• calibrate light/color sensors anywhere you like.
R10 - HANDLING DURING THE MATCH • You are not allowed to interact with any part of the Field that’s not COMPLETELY in Base.
Except: You may Interrupt the Robot any time. Except: You may pick up Equipment that BROKE off the Robot UNINTENTIONALLY, anywhere, any time.
• You are not allowed to cause anything to move or extend over the Base line, even partly.
Except: Of course, you may LAUNCH the Robot. Except: You may move/handle/STORE things off the Field, any time. Except: If something accidentally crosses the Base line, just calmly take it back – no problem.
• Anything the Robot affects (good or bad!) or puts completely outside Base stays as is unless the Robot changes it. Nothing is ever repositioned so you can “try again.”
R11 - MISSION MODEL HANDLING • You are not allowed to take Mission Models apart, even temporarily.
• If you combine a Mission Model with something (including the Robot), the combination must be loose enough that if asked to do so, you could pick the Mission Model up and nothing else would come with it.
R12 - STORAGE • Anything completely in Base may be moved/stored off the Field, but must stay in view of the referee.
• Everything in off-Field Storage “counts” as being completely in Base and may be placed on an approved holder.
R13 - LAUNCHING A proper Launch (or re-Launch) goes like this: • READY SITUATION
– Your Robot and everything in Base it’s about to move or use is arranged by hand as you like, all fitting “COMPLETELY IN BASE” and measuring no taller than 12 inches” (30.5 cm).
– The referee can see that nothing on the Field is moving or being handled.
• GO! – Reach down and touch a button or signal a sensor to activate a program.
IF FIRST LAUNCH OF THE MATCH – In this case, accurate fair timing is needed, so the exact time to Launch is the beginning of the last word/sound in the countdown, such as “Ready, set, GO!” or BEEEEP!
R14 - INTERRUPTING If you INTERRUPT the Robot, you must stop it immediately, *then calmly pick it up for a re-Launch. Here’s what happens to the Robot and anything it was Transporting, depending on where each was at the time: • ROBOT
– Completely in Base: . . . . . . . . . . . . . . . . . . . . . . . .Re-Launch
– NOT completely in Base: . . . . . . . . . . . . Re-Launch + Penalty
• TRANSPORTED THING WHICH CAME FROM BASE DURING THE MOST RECENT LAUNCH
– Always: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keep it
• TRANSPORTED THING WHICH DID NOT COME FROM BASE DURING THE MOST RECENT LAUNCH
– Completely in Base: . . . . . . . . . . . . . . . . . . . . . . . . . . . Keep it
– NOT completely in Base: . . . . . . . . . . . . .Give it to the referee
The “PENALTY” is described with the Missions.
IF YOU DON’T INTEND TO RE-LAUNCH – In this case, you may shut the Robot down and leave it in place.
R15 - STRANDING If the UNINTERRUPTED Robot loses something it was Transporting, that thing must be allowed to come to rest. Once it does, here’s what happens to that thing, depending on its rest location: • TRANSPORTED THING
– Completely in Base: . . . . . . . . . . . . . . . . . . . . . . . . . . . Keep it
– Partly in Base: . . . . . . . . . . . . . . . . . . . . .Give it to the referee
– Completely outside Base: . . . . . . . . . . . . . . . . . . .Leave as is
R16 - INTERFERENCE • You are not allowed to negatively affect the other team except as described in a Mission.
• Missions the other team tries but fails because of illegal action by you or your Robot will count for them.
R17 - FIELD DAMAGE • If the Robot separates Dual Lock or breaks a Mission Model, Missions obviously made possible or easier by this damage or the action that caused it do not score.
R18 - END OF THE MATCH As the Match ends, everything must be preserved exactly as-is. • If your Robot is moving, stop it ASAP and leave it in place. (Changes after the end don’t count.)
• After that, hands off everything until after the referee has given the OK to reset the table.
CONTINUED »
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 23
R19 - SCORING • SCORESHEET The referee discusses what happened and inspects the Field with you, Mission by Mission.
– If you agree with everything, you sign the sheet, and the scoresheet is final.
– If you don’t agree with something, the head referee makes the final decision.
• IMPACT Only your BEST score from regular Match play counts toward awards/advancement. Playoffs, if held, are just for extra fun.
• TIES Ties are broken using 2nd, then 3rd best scores. If still not settled, tournament officials decide what to do.
Changes for 2018 ĥ MAJOR
– If you Interrupt the Robot while it’s transporting something it took from Base during the most recent launch, you can now keep that object.
ĥ MINOR – Border lines are always part of the area they define.
– Disputes related to the thickness of thin lines (such as the border of Base) always settle in favor of the team.
– You need to conform to local event standards regarding the style and size of your Storage trays and carts.
– It’s OK to shut off the Robot and leave it in place without penalty if it’s done with intended Missions.
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 24
MissionsScoring Requirement Signals
ĥ Within the Mission descriptions, specific scoring requirements are written in GREEN.
ĥ Methods with an asterisk “✱” must be the ONLY ones used, and must be OBSERVED by the referee .
ĥ Underlined RESULTS/CONDITIONS must be visible at the END of the match.
ĥ For each Mission, only the text following “TECHNICALLY SPEAKING” is used for scoring.
M01 - SPACE TRAVEL Incredible engineering accomplishments like space travel come about in steps. And many huge, progressive sub-goals need to be met before we can forever leave Earth and live to tell about it!
Simply Speaking: The Robot needs to send Payload rockets (carts) rolling down the Space Travel Ramp. The first cart is pre-set and ready to go, but the Robot needs to load the other two from Base.
TECHNICALLY SPEAKING: ✱ Start each Payload clearly rolling down the Space Travel Ramp.
• For each roll, the cart must ✱ be Independent by the time it reaches the first track connection.
• Vehicle Payload: 22
• Supply Payload: 14
• Crew Payload: 10
As a Mission requirement in any Mission, the word “Independent” means “not in contact with any of your Equipment.”
As long as the cart clearly rolls Independently past the First Track Connection, it’s OK if it doesn’t roll all the way east.
Possible Scores: 0, 10, 14, 22, 24, 32, 36, 46FIRST TRACK CONNECTION
M02 - SOLAR PANEL ARRAY Solar Panels in space are a great source of energy for a space station in the inner Solar System, but since things in space is always moving, aiming the Panels takes some thought.
Simply Speaking: Solar Panels need to be Angled toward or away from you, depending on strategy and conditions.
TECHNICALLY SPEAKING: • Both Solar Panels are Angled toward the same Field: 22 For Both Teams
• Your Solar Panel is Angled toward the other team’s Field: 18
In the diagrams below, as on your practice Field, “Your” Solar Panel is the one on your west end of the Table.
Possible scores 0, 18, 22, 40 are shown below, as seen from above your North Border, facing north.
OTHER TEAM: 22 OTHER TEAM: 18 OTHER TEAM: 0 OTHER TEAM: 22+18
YOUR TEAM: 22+18 YOUR TEAM: 18 YOUR TEAM: 0 YOUR TEAM: 22
OTHER TEAM: 0 OTHER TEAM: 18 OTHER TEAM: 0 OTHER TEAM: 0
YOUR TEAM: 18 YOUR TEAM: 0 YOUR TEAM: 0 YOUR TEAM: 0
ANGLED
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 25
M03 - 3D PRINTING It is amazingly expensive to send heavy stuff like construction material into space, so scientists and engineers are instead learning how to print what they need in space, using available extraterrestrial elements.
Simply Speaking: The Robot needs to get a Regolith Core Sample and place it into the 3D Printer, which will cause the 2x4 Brick to pop out. The ejected 2x4 Brick can then be delivered elsewhere for more points.
TECHNICALLY SPEAKING: • Eject the 2x4 Brick ✱ by placing a Regolith Core Sample into the 3D Printer.
• The 2x4 Brick ejected and completely in the Northeast Planet Area: 22
• OR The 2x4 Brick ejected and not completely in the Northeast Planet Area: 18
Possible Scores: 0, 18, 22
M04 - CRATER CROSSING For rovers in other worlds, getting stuck is definitely not OK! Teams of rovers can help each other, but a lone rover needs to be very careful.
Simply Speaking: The Robot or whatever agent-craft it sends out needs to cross the Craters Model completely, by driving directly over it. Not near it. Not around it.
TECHNICALLY SPEAKING: • All weight-bearing features of the crossing equipment must cross ✱ completely between the towers.
• Crossing must be ✱ from east to west, and make it completely past the flattened Gate: 20
Possible Scores: 0, 20
NORTHEAST PLANET AREA 22 18
16 LANDER’S TARGET CIRCLE 12 10 8
BETWEEN THE TOWERS PAST THE GATE
M05 - EXTRACTION To live away from Earth, it would help if we were good at detecting and mining resources under the surfaces of other planets, moons, asteroids, and even comets.
Simply Speaking: The Robot needs to get all the Core Samples out of the Core Site Model, then it has options for what to do with them as described here, and in Mission M03.
TECHNICALLY SPEAKING: • Move all four Core Samples so they are no longer touching the axle that held them in the Core Site Model: 16
• Place the Gas Core Sample so it is touching the mat, and completely in the Lander’s Target Circle: 12
• OR Place the Gas Core Sample completely in Base: 10
• Place the Water Core Sample so it is supported only by the Food Growth Chamber: 8
Possible Scores: 0, 16, 24, 26, 28, 34, 36
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 26
M06 - SPACE STATION MODULES Space Stations allow us to learn about and even practice living in space, but improved technology and new international partners require Modules to be easily interchangeable.
Simply Speaking: The Robot needs to remove and insert Modules among the Habitation Hub’s port holes.
TECHNICALLY SPEAKING: • Inserted Modules must not be touching anything except the Habitation Hub.
• Move the Cone Module completely into Base: 16
• Insert the Tube Module into the Habitation Hub port, west side: 16
• Transfer/Insert the Dock Module into the Habitation Hub port, east side: 14
Possible Scores: 0, 14, 16, 30, 32, 46
16 16 14
AIRLOCK CHAMBER 22 18
M07 - SPACE WALK EMERGENCY Space is quiet and beautiful, but with almost no heat, air, nor air pressure, it could freeze, suffocate, and boil you all at once! Help our spacewalking Astronaut “Gerhard” get to safety.
Simply Speaking: The Robot needs to get Gerhard’s body into the Airlock Chamber.
TECHNICALLY SPEAKING: • Move Gerhard so his body is inserted at least partly into the Habitation Hub’s Airlock Chamber.
• Completely In: 22
• OR Partly In: 18
For this Mission, the word “Body” includes all parts except the loop.
Possible Scores: 0, 18, 22
HANDLE ASSEMBLY 22 (BENEFIT OF THE DOUBT) 18 18
M08 - AEROBIC EXERCISE Though spacecraft travel crazy-fast, even the shortest trips involve a lot of time for the traveler’s body away from labor and recreation, which is bad for the heart and lungs.
Simply Speaking: The Robot needs to repeatedly move one or both of the Exercise Machine’s Handle Assemblies to make the Pointer advance.
TECHNICALLY SPEAKING: • Advance the Exercise Machine’s Pointer along its Dial ✱ by moving one or both of the Handle Assemblies.
• Get the Pointer tip completely in orange, or partly covering either of orange’s end-borders: 22
• OR Get the Pointer tip completely in white: 20
• OR Get the Pointer tip completely in gray, or partly covering either of gray’s end-borders: 18
The Handle Assembly is part of the Exercise Machine, but it is shown by itself here for clarity.
Possible Scores: 0, 18, 20, 22
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 27
M09 - STRENGTH EXERCISE In zero-gravity, everything’s easy to move, and you couldn’t fall “down” even if you tried, so Astronauts need movement resistance - two hours a day in fact, just to keep muscle and bone density.
Simply Speaking: The Robot needs to lift the Strength Bar to scoring height.
TECHNICALLY SPEAKING: • Lift the Strength Bar so the tooth-strip’s 4th hole comes at least partly into view as shown: 16
Possible Scores: 0, 16
STRENGTH BAR 16 0
16 16 0
M10 - FOOD PRODUCTION Gardening is easy, right? You just need a truckload of rich soil, some rain, sun, fertilizer, helpful bugs, CO2 and a rake… but what if you were orbiting Neptune, in a room the size of a minivan?
Simply Speaking: Move the Push Bar the right distance at the right speed, to get into the green scoring range.
TECHNICALLY SPEAKING: • Spin the Food Growth Chamber’s colors so the gray weight is DROPPED after green, but before tan, ✱ by moving the Push Bar: 16
Possible Scores: 0, 16
PUSH BAR
STRIKE PAD 24
M11 - ESCAPE VELOCITY Soon after a launch, rocket engines often separate away from spacecraft by design, but that’s long before the spacecraft leaves the pull of gravity. So why doesn’t the spacecraft fall back to Earth?
Simply Speaking: The Robot needs to impact the Strike Pad hard enough to keep the spacecraft from dropping back down.
TECHNICALLY SPEAKING: • Get the spacecraft to go so fast and high that it stays up, ✱ by pressing/hitting the Strike Pad: 24
Possible Scores: 0, 24
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 28
M13 - OBSERVATORY A space telescope is astonishing, but it can’t beat the accessibility and simplicity of a college or science museum observatory - that is, if you know how and where to point it.
Simply Speaking: Rotate the Observatory to a precise direction.
TECHNICALLY SPEAKING: • Get the pointer tip completely in orange, or partly covering either of orange’s end-borders: 20
• OR Get the pointer tip completely in white: 18
• OR Get the pointer tip completely in gray, or partly covering either of gray’s end-borders: 16
Possible Scores: 0, 16, 18, 20
16 16 0
M14 - METEOROID DEFLECTION The chance of a “serious” Meteoroid hitting Earth in our lifetime is extremely low, but it’s not zero, and the devastation could truly wipe us out. How will scientists and engineers keep us safe?
Simply Speaking: From west of the Free-Line, send one or both Meteoroids Independently to the Meteoroid catcher.
TECHNICALLY SPEAKING: • Send Meteoroids ✱ over the Free-Line to touch the mat in the Meteoroid Catcher.
• The Meteoroids must be hit/released while they are ✱ clearly and completely west of the Free-Line.
• While between hit/release and scoring position, the Meteoroid ✱ must be clearly Independent.
• Meteoroids in the Center Section: 12 Each
• Meteoroids in Either Side Section: 8 Each
If ever the Ring-Set Meteoroid is off its Ring, you may remove the Ring from the Field by hand (this is a special exception to the Rules).
Possible Scores: 0, 8, 12, 16, 20, 24
FREE-LINE MUST BE INDEPENDENT WHILE EAST OF THE FREE-LINE
24 20
M12 - SATELLITE ORBITS If a Satellite doesn’t have the correct velocity and distance from Earth, it can fall, drift away, fail to function, or get destroyed by debris. Propulsive adjustments need to be performed with precision.
Simply Speaking: The Robot needs to move one or more Satellites to the Outer Orbit.
TECHNICALLY SPEAKING: • Move any part of a Satellite on or above the area between the two lines of the Outer Orbit: 8 Each
Possible Scores: 0, 8, 16, 24
BETWEEN ONLY THESE TWO LINES
OUTER ORBIT 8 0
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 29
M15 - LANDER TOUCH-DOWN: Our Lander doesn’t have working parachutes, thrusters, or cushions, but one important feature is realistic… it’s very fragile.
Simply Speaking: Get the Lander to one of its targets intact, or at least get it to Base.
TECHNICALLY SPEAKING: • Move the Lander to be intact, touching the Mat, and completely in its Target Circle: 22
• OR Move the Lander to be intact, touching the Mat, and completely in the Northeast Planet Area: 20
• OR Move both parts of the Lander completely into Base: 16
The Lander is “Intact” if its parts are connected by at least two of its four tan location axles.
Possible Scores: 0, 16, 20, 22
INTACT LANDER’S TARGET CIRCLE NORTHEAST PLANET AREA 22
20 20 16 0 0
PENALTY DISCS
P01 – INTERRUPTION PENALTIES: Read the RULES carefully and often.
Simply Speaking: FIRST LEGO League Mission Requirements need to be achieved by your Robot through its programs and its use of equipment. You’re allowed to hand-rescue your Robot, but that does cause this Penalty. Be sure to pay extra attention to the Rules where they talk about “Interruptions.”
TECHNICALLY SPEAKING: • If you ✱ Interrupt the Robot: Minus 3 Each Time
Upon Penalty, the referee will place one Penalty Disc in the southeast triangle as a permanent Interruption marker.
You can get up to six such Penalties.
If a Penalty Disc comes off the triangle, it is simply returned, with no effect on score.
Possible Penalty Totals: -18, -15, -12, -9, -6, -3, 0
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 30
M01
M02
M03
M06
M08
M10
M11
M13
M14
M12
M15M09
M07
M04
M05
FIRST® LEGO® League || 2018/2019 Challenge Guide || Page 31
Robot Design Executive Summary (RDES)An “executive summary” is often used by engineers to briefly outline the key elements of a product or project. The purpose of the Robot Design Executive Summary (RDES) is to give the Robot Design Judges a quick overview of your team’s robot and all that it can do.
Unlike the Core Values Poster, teams do not need to create a poster or written material for the RDES. However, teams may share pictures of the design process and records of strategy sessions, and are strongly encouraged to bring examples of programming (either printed or on a laptop).
Have your team prepare a short presentation (no longer than four (4) minutes) covering the elements below:
1. Robot Facts Share a little bit about your robot, such as the number and type of sensors, drivetrain details, number of parts, and the number of attachments. The Judges also like to know what programming language your team used, the number of programs, and the Robot Game mission where your team had the most success.
2. Design Detailsa. Fun: Describe the most fun or interesting part of robot
design as well as the most challenging parts. If your team has a fun story about your robot please feel free to share.
b. Strategy: Explain your team’s strategy and reasoning for choosing and accomplishing missions. Talk a little bit about how successful the robot was in completing the missions that were chosen.
c. Design Process: Describe how your team designed their robot and what process they used to make improvements to the design over time. Briefly share how different team members contributed to the design.
d. Mechanical Design: Explain the robot’s basic structure. Explain to the Judges how the robot moves (drivetrain), what attachments and mechanisms it uses to operate or complete missions, and how your team makes sure it is easy to add/remove attachments.
e. Programming: Describe how your team programmed the robot to ensure consistent results. Explain how the team organized and documented programs. Mention if the programs use sensors to know the location of the robot on the field.
f. Innovation: Describe any features of the robot’s design that the team feels are special or clever.
3. Trial Run Run the robot briefly to demonstrate how it completes the mission(s) of your team’s choice. Please do not do an entire robot round. The Judges need time to ask questions after the RDES.
Want to Learn More? ĥ Explore the essential details of the Robot Game by reading the Rules and Missions in this Challenge Guide.
ĥ Check the Robot Game Updates, often. FIRST LEGO League staff will clarify common questions. Updates supersede anything in this Challenge document and will be in effect at tournaments.
ĥ Your team will be assessed in the judging room using a standard Robot Design rubric.
ĥ Your team will also compete in at least three Robot Performance matches. Read the Event Guide for Teams to know what to expect at an Official Event.
ĥ If you are completely new, check out the FIRST LEGO League Challenge Resource page for videos, tips, and additional helpful rookie links.
INTO ORBITSM
Challenge Updates
Robot Game Updates
U02 – SOME CORE SAMPLES 20 August 2018
Core Samples can be used to earn points as described in Missions M03 and M05 even if the Core Site Model’s axle is not completely empty. This means additional possible scores related to the Core Samples include: 8, 10, 12, 18, and 20.
U01 – METEOROID CATCHER SHAPE 14 August 2018
The Meteoroid Catcher described in the Mission Model Building Instructions is correct. You can ignore the slight difference seen in the pictures of the Challenge Guide.
Project Updates
U02 – SOLVE YOUR “SPACE PROBLEM” FIRST 01 August 2018
In many past seasons, the Project directions have instructed teams to “design an innovative solution that adds value to society.” For the INTO ORBITSM Project, your problem is very unique: You must “identify a human physical or social problem faced during long duration space exploration within our Sun’s solar system and propose a solution.” For this season, to avoid any confusion about just whom your solution should benefit, we have removed the phrase “adds value to society” from the Challenge Guide. This is to make it clear that your team only needs to worry about finding a solution that helps the people in space affected by your problem. If it happens to also help people on Earth by creating a “spinoff” solution, that’s great! However, it’s not a requirement. Judges will be notified of this Update so that when they are evaluating your team’s solution, they do not expect you to develop an innovation that also solves a problem on Earth. Also, remember that teams are expected to share their work as part of the FIRST® LEGO® League Project. However, we realize that it may not be possible to share your research with an expert in space exploration. That’s OK! Remember that you can share your Project with any of the professionals you consulted as part of your research to achieve Accomplished or Exemplary levels on the rubric.
U01 – FINDING HELP 01 August 2018
One of the most frequent questions we are asked about the Project each year is, “How can we find people to help our team learn more about _____” (space, water, animals, nanotechnology, etc.). For the INTO ORBIT Challenge, we realize that not everyone lives down the street from a place that launches rockets!
However, if you will review the Challenge Guide closely, especially pages 16-18, you will see that the “Ask A Professional” section lists many more jobs than just astronaut and rocket scientist. In fact, many types of professionals can help your team understand some of the problems involved in long-duration space travel. Health care professionals can help you discover some of the physical problems people confront in space, such as exposure to reduced gravity and radiation. Psychologists and social workers can help you understand some of the social problems people face when they are away from family and friends for long periods of time. Aeronautical, mechanical and electrical engineers can help you appreciate some of the amazing systems that are needed to develop spacecraft capable of keeping crews healthy and safe. You might even consider contacting a teacher at a college or university, or seeing if there is a science center or planetarium nearby. The “Websites and Articles” section on page 14 of the Guide has a list of places you can begin looking for assistance.
There are also some starter questions on page 7 of the Guide, and some sample problems listed on page 8. These sections may help you begin your research and select a problem. They may also spark an idea about who you might ask for help. The “Share with Others” section on page 9 of the Guide also has some tips about finding support for your team. Presenting your Project to professionals is a great way to share your work!
Judges are aware that teams will be talking to a wide variety of professionals during the INTO ORBIT season. So, don’t worry, you will not be expected to find your own personal astronaut or rocket scientist!
What’s new for INTO ORBITSM?
• FIRST Core Values: The Core Values have been refreshed and are now consistent across all four
FIRST programs.
• Challenge and Challenge Guide: The relevant pieces of the Challenge are included each Judge
Prep Pack. The Prep Packs are available in the 2018-2019 Core Values, Project, and Robot Design Judge
Certification courses or from your Tournament Director.
• Participation Rules: Please review the updated rules and new video.
• Optional Engineering Notebook for teams: The
Engineering Notebook is not required for the INTO ORBITSM season.
Robot Design Judges should treat the Engineering Notebook just like other
documentation or other information teams provide. Teams who present an
Engineering Notebook may naturally do better in judging, but they do not
automatically get a bonus; teams without an Engineering Notebook are not
penalized.
• Judging-related pilot projects: Check with your Judge Advisor,
Tournament Director, or Partner to find out if your region is participating.
Make sure you’re up to date for the
2018-2019 INTO ORBITSM FIRST® LEGO® League season:
