search

nicholasmr / obblm

Automatically exported from code.google.com/p/obblm
26 stars 54 forks source link

Randomize matches in RR and KO tours #23

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Add an initial shuffle() to the teams array when creating a KnockOut or RR
tournament so the match order wont be predictable for the participating
coaches.

Original issue reported on code.google.com by blodae@gmail.com on 10 Feb 2009 at 4:07

GoogleCodeExporter commented 9 years ago 
This is nearly impossible for knock-out tournaments since it would require me to
restructure the whole knockout handling class, which works excellent with 
backward
comparability and sudden score changes in previously played matches. 
Also, to make things worse, the knock-out implementation is the most obscure and
messy of all the obblm code, and absolutely (!!) requires the order of matches, 
IDs
and competitors not to be changed (more "!!" :-)) - which is also why matches 
can't
be deleted from KO-tours.

I don't think this request makes sense for RR-tours, since everybody eventually 
meets
each other in this tour type? 
I won't, myself anyway, make this change if the only reason for it is, that you 
want
matches to appear in different orders on the fixture list - because the order in
which matches are played does not matter anyway, and so this seems to me as too 
much
fuss for nothing (really).

Original comment by Nimda...@gmail.com on 10 Feb 2009 at 9:28

GoogleCodeExporter commented 9 years ago 
Which criteria are used when the opponents chosen in first round? The order 
that you
get the teams from DB via select?

Original comment by blodae@gmail.com on 11 Feb 2009 at 8:50

GoogleCodeExporter commented 9 years ago 
It's not done like that.

The team list with team IDs is sent as the same ordered list from the schedule
matches section. So, at the moment since teams there are ordered by coach 
names, so
are the paired up matches for RR.

Knock-out is more complicated to explain - I suggest looking in the KO-code
constructor code. It's difficult to explain :-/.

Original comment by Nimda...@gmail.com on 11 Feb 2009 at 12:24

GoogleCodeExporter commented 9 years ago 
Ah, and I understand the difficulties. Well, since I haven't understood the KO 
code I
doubt I understand it fully. ;-)

Original comment by blodae@gmail.com on 11 Feb 2009 at 12:51