My point was that the TEAMS have to be checked in etc. before the schedule can be generated. If a schedule was generated and a team should happen not to show up, then a new schedule would have to be generated. Any existing copies of the old schedule would need to be destroyed. This would have to happen no matter how the schedule is determined.
Having been through this sort of thing I can tell you it causes all kinds of problems. It is bad enough if the schedule has not been released, just grab the old schedules and toss them in a secure place. So you just wasted alot of paper. If incorrect schedules get out you have teams showing up for the wrong matches, unhappy spectators who miss their team's match, Cueing can get screwed up (if somehow they get the wrong version). It just gets ugly. Been there, done that.
All the division schedules are released at the same time so one division does not have an advantage. So until every team has checked in or it has been determined that they will not be showing up, no schedule.
Quote:
Originally Posted by lemiant
1) It doesn't seem like separating this software would be hard, and it would give us more freedom. So why not?
2)Since the schedule doesn't balance anything specific to teams competing, why can't we create a rainbow table of sorts with the optimal couple of schedules for each number of teams and then randomly assign teams to slots? No need to recompute the same thing over and over.
|