I would model teams as vertices of a graph and quizzes as directed edges. Each edge would be decorated with the round number. Then the problem becomes one of creating a graph with uniform in and out degree at each vertex, ie, a kind of directed regular graph. Furthermore the round numbers must be picked to satisfy all the simultaneity contstraints and the constraints imposed by mapping related vertices to rooms. It is a mess :)

In complicated problems like this, I would assign each violation of a constraint a numerical weight. Then every configuration of teams, quizzes, round numbers, and rooms would be graded by the sum of all the weights of the violations. Then the problem becomes one of minimizing the total weight over all configurations.

To minimize, I would use a genetic algorithm (e.g., Algorithm::Evolutionary) or simulated annealing (Algorithm::Evolutionary has some simulated annealing capabilities as well). In generating mutations, i.e., new configurations, it is best to satisify the truly hard constraints automatically. So always create mutations that have the same number of one-quizzes, two-quizzes and three-quizzes for each team.

Can't help you with the kitchen until you add more geometry to the spec :)

-Mark

In reply to Re: Round-Robin with Three-way Matches by kvale
in thread Round-Robin with Three-way Matches by jonadab

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.