AERIAL DRONE COMPETITION PRO • RECF
<G4> Each Student can only belong to one Team, and all work must represent the skill level of the Students on the Team. A Team is made up of Mission Crew Member(s), Pilot(s), Driver(s), Designer(s), Coder(s), Visual Observer(s), Builder(s), Notebooker(s), and other Student support members. No Student may fulfill any of these roles for more than one ADC Pro Team in a given competition season. Students may swap roles or have more than one role on their own Team. (E.g., a Pilot may also be the Coder, and the Coder can also be a Driver) a. The Team’s Robot and Teamwork Mission Drone design, coding, strategy, and ongoing work must represent the skill level of the Students currently on the Team. i. Teams may use Robot and Drone assembly instructions provided by the vehicle manufacturer or the REC Foundation, but are encouraged to use these only as a starting point that Students modify, improve, or replace as their skills increase. ii. Students are encouraged to explore and learn from external libraries, example code, and online resources to build their skills. However, all code used on the Drones and Robots must be assembled and authored by the Team’s own Students to reflect their current skill level. iii. While Teams may be inspired by publicly available strategies, design ideas, or code, they should not directly copy or rely on designs or code created by others, including Adults, Coaches, or Students from other Teams. Instead, Students should use those resources as learning tools and develop their own unique solutions. b. Team members may move from one Team to another for non-strategic reasons outside of the Team’s control. i. Examples of permissible moves may include, but are not limited to, illness, changing schools, conflicts within a Team, or combining/splitting Teams. ii. Examples of strategic moves in violation of this rule may include, but are not limited to, one Coder “switching” Teams in order to write programs for multiple Drones, or one Student Driving the Robot for multiple Teams. iii. If a Student leaves a Team to join another Team, <G4> still applies to the Students remaining on the previous Team. For example, if a Coder leaves a Team, then that Team’s code must still represent the skill level of the Team without that Coder. One way to accomplish this would be to ensure that the Coder teaches or trains a replacement Coder in their absence. c. When a Team qualifies for a Championship event, the Students on the Team attending the Championship event are expected to be the same Students on the Team that was awarded the spot. Students can be added as support to the Team, but may not be added as a Pilot or Driver. i. An exception is allowed if only one member of the Team is able to attend the Championship event. The Team can make a single substitution of a Pilot or Driver for the Championship event with another Student, even if that Student has competed on a different Team. This Student will now be on this new Team and may not substitute back to the original Team during the season.
24 | MISSION 2026-2027 OFF GRID COMPETITION MANUAL V 1.1
Made with FlippingBook HTML5