Quote:
Originally Posted by XaulZan11
The problem I have with this 'random' match schedule, is that it can be redone if they feel there are 'too many repeat'. By doing this it is no longer a random schedule. While I don't think this is likely, it leaves the door open for someone to rerun the program because of an unfavorable schedule.
|
While this is possible, it is not likely. For one thing the Scorer, FTA and Field Supervisor are all likely to be present and all will have different ideas about just what an "unfavorable" schedule is. For another it takes about 15 min. to generate a new schedule. We just don't have time to generate more than 2 or 3.
The auditing screen gives the following information about each team:
Number of unique partners - this should be #of rounds x 2 and generally is
Number of unique opponents - ideally this would be # of rounds x 3 but there is some variaition here. This is the number checked most closely.
Number of matches as Surrogate - should be no more than 1 and not many of those.
Teams played and number of times - listed in numeric order, not by what match they are in. # of times played should be no more than 2 for any one team, unless the event is really small and there are lots of matches, in which case there should be lots of 3s not only one or two.
None of this gives very much information about the difficulty of the schedule for a particular team. To figure that out you have to go over the schedule itself which would be very time consuming. Then if you cause the schedule to be re-generated, the schedule you have will disappear. So you are taking a very significant risk that the new scedule will be even worse that the one you just blew away, and you have to do all the analysis all over again to find out. The costs outweigh the benefits very quickly.
In practice, you run the scheduler once and check the output against the criteria above. If it passes you go with it. If not you change one parameter and try again. Once you get somehng that is "good" you lock it and attempt to fire up the printer. But that is a whole different story...