AERIAL DRONE COMPETITION • REC FOUNDATION
<G3> Use common sense. When reading and applying the rules in this document, please remember that common sense always applies in the Aerial Drone Competition. Some examples may include : • If there is an obvious typographical error, this does not mean that the error should be taken literally until corrected in a future update. • When in doubt, if there is no rule prohibiting an action, it is generally legal. However, if you have to ask whether a given action would violate <S1>, <G1>, or <T1>, then that’s probably a good indication that it is outside the spirit of the competition. • In general, Teams will be given the “benefit of the doubt” in the case of accidental or edge-case rule infractions. However, there is a limit to this allowance, and repeated or strategic infractions will still be penalized. <G4> Each Student can only belong to one Team, and all work must represent the skill level of the Students on the Team. Teams cannot “borrow” Students from other Teams to serve as Pilot(s), Co-Pilot(s), Visual Observer(s), or Coder(s). Students may swap roles or have more than one role on the Team (e.g., the Pilot may also be the Coder, the Coder may also be a Visual Observer) a. The Team’s coding must represent the skill level of the Students currently on the Team. i. Students are encouraged to explore and learn from external libraries, example code, and online resources to build their skills. However, all code used must be assembled and authored by the Team’s own Students to reflect their current skill level. ii. While Teams may be inspired by publicly available strategies or code, they should not directly copy or rely on code written by others, including Adults, Mentors, or educators. Instead, Students should use those resources as learning tools and develop their own unique solutions. b. Team members may only 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, 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 the same program for multiple Teams, or one Student writing the Competition Logbook 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.
28 MISSION 2026 TIME WARP COMPETITION MANUAL V 1.0
Made with FlippingBook HTML5