Quote:
Originally Posted by Boltman
I believe "Class" has a lot to do with year to year success in a 20 year organization of 4000 or so teams... just like in horse racing.
|
The programmer of the 2007 match algorithm believed the same thing. Whether or not it is correct doesn't matter much to the results of implementing that belief: with fewer than about 60 teams at an event, the number of times a given team plays with or against a specific other team skyrockets. This is exactly what you're trying to avoid, isn't it?
Quote:
Originally Posted by Citrus Dad
The solution is in fact quite easy. It's a two-step scheduling algorithm that accounts for last season's performance. I believe that all of the professional sports leagues already do this. First, you sort the teams in bins A, B & C based on a ranking criterion--probably a system akin to the district point system. (Rookies = 0). Each match is scheduled by drawing a team from each bin for each alliance as an added step. All of the other constraints then come into place.
|
Unless you have an extraordinarily large pool of teams to draw from, "all of the other constraints" conspire to cluster teams into essentially the same groupings over and over again. What problem were you trying to solve again?