1 |
none...
|
1 |
none...
|
2 |
\n
|
2 |
\n
|
3 |
\n
|
3 |
\n
|
4 |
curent algorithm: (as far as i know)
|
4 |
curent algorithm: (as far as i know)
|
5 |
sort the teams till you get a match with balanced elos
|
5 |
sort the teams till you get a match with balanced elos
|
6 |
(ignoring any beter matches)
|
6 |
(ignoring any beter matches)
|
7 |
\n
|
7 |
\n
|
8 |
this algorithim:
|
8 |
this algorithim:
|
9 |
pair to lower variance
|
9 |
pair to lower variance
|
10 |
sort the teams till you get a match with balanced elos
|
10 |
sort the teams till you get a match with balanced elos
|
11 |
\n
|
11 |
\n
|
12 |
the pairing should not significantly* increase the elo distance between the 2 teams, and it is faster then curent algorithm
|
12 |
the pairing should not significantly* increase the elo distance between the 2 teams, and it is faster then curent algorithm
|
13 |
\n
|
13 |
\n
|
14 |
*it
may
select
things
like
1640
vs
1660
instead
of
1650
vs
1650
if
it
has
beter
variance,
but
thats
pretymuch
the
limit
(
curent
algorightm
on
avarage
has
a
50
elo
gap
between
2
teams,
so
its
well
within
the
limits)
|
14 |
*it
may
select
things
like
1640
vs
1660
instead
of
1650
vs
1650
if
it
has
beter
variance,
but
thats
pretymuch
the
limit
(
curent
algorightm
on
avarage
has
a
27
elo
gap
between
2
teams,
so
its
well
within
the
limits)
|