Section 3 General Competition Rules, continued
<G4> Piloting and programming skills must represent the skill level of the team. Piloting and programming skills must represent the skill level of the team. A team is made up of pilot(s), co-pilot(s), programmer(s), and visual observer(s). Students may not fulfill any of these roles for more than one Aerial Drone Competition Team in a given competition season. Students may swap roles or have more than one role on their own team. 1. Team members may move from one team to another for non-strategic reasons outside of the team’s control. a.Examples of permissible moves may include, but are not limited to, illness, changing schools, conflicts within a team, or combining/splitting teams. b.Examples of strategic moves in violation of this rule may include, but are not limited to, one programmer “switching” teams in order to write programs for multiple drones, or one student piloting the drone for multiple teams. c. 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 programmer leaves a team, then that team’s programming skills must still represent the skill level of the team without that programmer. One way to accomplish this would be to ensure that the programmer teaches or trains a replacement programmer in their absence. 2. 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 pilots or programmers for the team. a. An exception is allowed if one (1) pilot and/or one (1) programmer on the team cannot attend the event. The team can make a single substitution of a pilot or programmer 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. Violations of this rule will be evaluated on a case by-case basis, in tandem with the REC Foundation Student- Centered Policy as noted in <G2>, and the REC Foundation Code of Conduct as noted in <G1>. Event Partners should bear in mind rule <G3>, and use common sense when enforcing this rule. It is not the intent to punish a team who may have a team member move to another team due to illness, changing schools, conflicts within a team, etc. Event Partners and referees are not expected to keep a roster of any students. This rule is intended to block any instance of loaning or sharing team members to other teams for the sole purpose of gaining a competitive advantage.
22 ROBOTICS EDUCATION & COMPETITION FOUNDATION - AERIAL DRONE COMPETITION
Made with FlippingBook HTML5