Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create precedence preference for pullup restrictions #2446

Closed
tienne-B opened this issue Jun 19, 2024 · 3 comments
Closed

Create precedence preference for pullup restrictions #2446

tienne-B opened this issue Jun 19, 2024 · 3 comments

Comments

@tienne-B
Copy link
Member

The WSDC Power Pairing Procedures has a couple different restrictions on pullups:

It would be good to have some clarity on how these restrictions interact with each-other, as they are quite deferential to each other with "If possible," or general exceptions for other points. In my estimation, if many teams have the lowest number of pullups, the deciding factor goes to 3.7.

@tienne-B tienne-B converted this from a draft issue Jun 19, 2024
@SerbiaWSDCCAs
Copy link

So while ideally you want to adhere to all the rules, in scenarios where not all rules can be followed simultaneously due to conflicts, the prioritization is as follows:

  1. Rule 3.10/3.11 (3-5 prop/opp split) must always be followed, no matter the circumstances. This rule is paramount and overrides all other rules.

  2. If a conflict arises where not all rules can be adhered to, Rule 3.7 is the first rule that can be set aside. While important, it holds the lowest priority in cases of conflict.

  3. The next rule that can be compromised, if necessary, is Rule 3.10/3.11 (4-4 prop/opp split). This rule is secondary to Rule 3.10/3.11 (3-5 prop/opp split) and can be disregarded if conflicts arise with higher-priority rules.

  4. Following that, Rule 3.6 can be set aside if adhering to it causes conflicts with the essential rules mentioned above.

  5. Lastly, if conflicts persist and not all rules can be simultaneously followed, Rule 3.5 can be the next to be compromised. This rule, while significant, is the highest in the hierarchy of rules that can be set aside when conflicts with other critical rules occur.

Thus if conflicts necessitate not following some rules, the order of compromise should be: first Rule 3.7, then Rule 3.10/3.11 (4-4 prop/opp split), followed by Rule 3.6, and finally Rule 3.5.

@SerbiaWSDCCAs
Copy link

SerbiaWSDCCAs commented Jun 28, 2024

REVISED COMMENT:

So while ideally you want to adhere to all the rules, in scenarios where not all rules can be followed simultaneously due to conflicts, the prioritization is as follows:

  1. Rule 3.10/3.11 (3-5 prop/opp split) must always be followed, no matter the circumstances. This rule is paramount and overrides all other rules.

  2. If a conflict arises where not all rules can be adhered to, Rule 3.8 is the first rule that can be set aside. This rule holds the lowest priority in cases of conflict.

  3. The next rule to be set aside, if necessary, is Rule 3.7.

  4. Rule 3.10/3.11 (4-4 prop/opp split) can be set aside if the conflicts persist after setting aside the previous rules. This rule is secondary to Rule 3.10/3.11 (3-5 prop/opp split) and can be disregarded if conflicts arise with higher-priority rules.

  5. Following that, Rule 3.6 can be set aside if adhering to it causes conflicts with the essential rules mentioned above.

  6. Lastly, if conflicts persist and not all rules can be simultaneously followed, Rule 3.5 can be the next to be compromised. This rule, while significant, is the highest in the hierarchy of rules that can be set aside when conflicts with other critical rules occur.

Thus if conflicts necessitate not following some rules, the order of compromise should be: first Rule 3.8, then Rule 3.7, then Rule 3.10/3.11 (4-4 prop/opp split), followed by Rule 3.6, and finally Rule 3.5.

@tienne-B
Copy link
Member Author

Superseded by #2513

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: To do
Development

No branches or pull requests

2 participants