-
-
Notifications
You must be signed in to change notification settings - Fork 860
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
Comments
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:
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. |
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:
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. |
Superseded by #2513 |
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.
The text was updated successfully, but these errors were encountered: