The current implementation can be improved:
When using constraints, the validator passes a chronological list of available matches. Sometimes there are exactly enough matches to fill the session teams, but sometimes we have a choice.
Example: session 4 teams can be in matches 16, 17, 18, 19.
Currently we just use the first match, which means we actually prioritize shorter breaks between judging sessions and matches.
This can be improved by choosing the last matches first, but that can lead to other problems if the last matches are also included in another session. We need to verify that the slots actually can be used by us without interfering with other sessions, and then prioritize the last slots.
This approach will result in larger wait times whenever possible when using constraints.
The current implementation can be improved:
When using constraints, the validator passes a chronological list of available matches. Sometimes there are exactly enough matches to fill the session teams, but sometimes we have a choice.
Example: session 4 teams can be in matches 16, 17, 18, 19.
Currently we just use the first match, which means we actually prioritize shorter breaks between judging sessions and matches.
This can be improved by choosing the last matches first, but that can lead to other problems if the last matches are also included in another session. We need to verify that the slots actually can be used by us without interfering with other sessions, and then prioritize the last slots.
This approach will result in larger wait times whenever possible when using constraints.