Ordo 0.9.6
Posted: Wed Sep 10, 2014 6:34 pm
https://sites.google.com/site/gaviotach ... e/releases
Finally, I merged the experimental branch with "loose" anchors and relative ones, mentioned a while ago.
http://www.talkchess.com/forum/viewtopi ... o+approach
In addition, now the user can round the output number (switch -N)
Switches added:
-N <value> Output, number of decimals, minimum is 0 (default=1)
-y <file> loose anchors: file contains rows of "Player",Rating,Uncertainty
-r <file> relations: rows of "PlayerA","PlayerB",delta_rating,uncertainty
-u <value> white advantage uncertainty value (default=0.0)
-k <value> draw rate uncertainty value % (default=0.0 %)
Excerpts from the readme file:
Loose anchors with prior information
Ordo offers an alternative approach to calculate ratings with previous knowledge from the user (using Bayesian concepts). With the switch -y, the user can provide a file with a list of players whose ratings will float around an estimated value. Those players will work as loose anchors in the list. This strategy is useful when the data is scarce and, as a consequence, wild swings could appear in the ratings. This is what happens at the beginning of a new rating list or tournament. Ordo accepts an estimated rating for a player, but takes into account how uncertain that value is. In other words, the user also has to provide the standard error for the estimated value.... etc
Relative anchors
Another problem in some engine tournaments is that version upgrades enter with no previous ratings. However, we know in certain situations that the new versions cannot have very different ratings from the previous one. Therefore, the user can make a good educated guess about the rating of the new version.... etc
Latest readme file
Miguel
Finally, I merged the experimental branch with "loose" anchors and relative ones, mentioned a while ago.
http://www.talkchess.com/forum/viewtopi ... o+approach
In addition, now the user can round the output number (switch -N)
Switches added:
-N <value> Output, number of decimals, minimum is 0 (default=1)
-y <file> loose anchors: file contains rows of "Player",Rating,Uncertainty
-r <file> relations: rows of "PlayerA","PlayerB",delta_rating,uncertainty
-u <value> white advantage uncertainty value (default=0.0)
-k <value> draw rate uncertainty value % (default=0.0 %)
Excerpts from the readme file:
Loose anchors with prior information
Ordo offers an alternative approach to calculate ratings with previous knowledge from the user (using Bayesian concepts). With the switch -y, the user can provide a file with a list of players whose ratings will float around an estimated value. Those players will work as loose anchors in the list. This strategy is useful when the data is scarce and, as a consequence, wild swings could appear in the ratings. This is what happens at the beginning of a new rating list or tournament. Ordo accepts an estimated rating for a player, but takes into account how uncertain that value is. In other words, the user also has to provide the standard error for the estimated value.... etc
Relative anchors
Another problem in some engine tournaments is that version upgrades enter with no previous ratings. However, we know in certain situations that the new versions cannot have very different ratings from the previous one. Therefore, the user can make a good educated guess about the rating of the new version.... etc
Latest readme file
Miguel