From | Message | ||
---|---|---|---|
|
![]() My question is what system do you use? I am always willing to adapt to a better matching system but we have been using this since I was captain in 2016 and before when I was cocaptain and it has been successful for us. I am always willing to learn more. What do you think? |
||
|
![]() |
||
goldentweety 17-Jun-21, 02:46 |
![]() |
||
|
![]() Mouse over the link and it gives you the 90 days. Is this what you are talking about? This is their top rating and indicates player potential. I have always used this and we have never had any problems. I only check further if they are close to being 50 out of range |
||
|
![]() |
||
|
![]() I also check to make sure the players I am planning on matching aren't already playing or have played recently, I try to give some diversity. I'll look at average time per move too, but it isn't priority. |
||
|
![]() We are trying to implement rivals. Our players dont like duplicate matches and if they have a losing record against an opponent there is not much sense matching them but this is a judgement call. With the addition of amacivn, we are going to try using rivals as there are two of us using it now...half the work Hopefully my other cocaptains will agree and we can start using this system as of July 1 |
||
|
![]() I agree that the chart can be very useful. My impression is that it is underused as a matching tool. |
||
|
![]() I recently turned down a match because the chart showed that the opponent was a 1600 player with a 1400 rating currently. While the rest of the stats were ok. my player was overated at 1400 so this is not a fai rmatch. A couple of things you have to watch out for but they are hard to detect. Some players are in the league or the ladders and they lose these games to keep their rating down. So when they play team games they have an unfair advantage.Also I am wary of people that have completed 100 or so games and are crushing their opponents at low ratings while they achieve their true rating. This is not an exact science and you have to rely on intuition and judgement. Every matchup needs to be evaluated on its own merits |
||
|
![]() I click on "Rivals" when I remember to. Seeing the past history can add to the drama of a match. I don't actually know one way or the other how reliable past heads-up records are as a predictive tool, but there are times when the record is lopsided enough that I decide against sending a challenge that I was considering. I do know that if two equal players play enough matches against each other, one or both of them will at some point obtain the "lead" in their rivalry. Even if they're completely equal, not every match will end 1-1. But of course if one player has an advantage over the other, that player will also tend to take the lead in the series. Sometimes it's not easy to figure out if you're looking at variance or a significant trend! Anyhow, the "+/- 4" flexibility that you mention sounds similar to my intuitive reaction to past heads-up histories when I remember to look at them. |
||
|
![]() |
||
|
![]() For that player, I am pretty sure the best estimate of his abilities is his average rating for either one year or for all rated games. An intelligent reading of his graph, also, will yield a similarly accurate estimate of his playing strength. |
||
|
![]() 1) prevent duplicate matches from the same opp0nent 2) prevent loss of matches when a player has played the same opponent several times with a losing score 3) prevent opponents who manipulate their ratings by losing personal games Resolution: 1) evaluate according to elo and 90 day requirement 2) evaluate players graphs to determine if opponents/players are underrated/overrated 3) evaluate current matches to prevent duplication 4) evaluate rivals to see overall record against opponent. I realize some have an extensive rivalry but we wont match unless the overall score is +/- 4 games This additional checking may cause delay in matching but we are seeking quality over quantity enabling our players to have a fair chance in their matches |
||
|
![]() |
||
|
![]() -Dave |