Search found 18 matches

by pete
Sat Jun 09, 2012 4:31 pm
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.

bakekoq wrote:hello.
may I know how to install it?
it can be good for me and my clubs in the future.


There are instructions on the linked page. It's a ruby gem, so you must be familiar with ruby and rubygems first.
by pete
Wed May 30, 2012 3:58 pm
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.



| | KGS | EGF | EGF | KGS | EGF | EGF |
| | exp. | exp. | obs. | exp. | exp. | obs. |
| even game | win % | win % | win % | elo | elo | elo |
|-----------|-------|-------|-------|-------|-------|-------|
| 10k vs 9k | 30.0 | 33.9 | 44.8 | 148 | 116 | 36 |
| 5d ...
by pete
Wed May 30, 2012 12:30 pm
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.

Yoyoma,

I'm wondering if we have different models in our heads at this point. When you present a probability statement like P = 1 / ( 1 + 10^((RankB-RankA)/400)) ) and then go on to say that RankB and RankA are actual kyu/dan ranks, I don't follow.

The model that WHR uses (and Remi, correct me if ...
by pete
Wed May 30, 2012 9:15 am
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.

As an aside, I'm glad to finally have some questions and feedback on this code that I struggled to write.

I'm certainly open to the possibility that there may be mistakes in the code, and would love to have someone other than me look it over. That's one of the reasons I open sourced it. If you see ...
by pete
Wed May 30, 2012 9:06 am
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.


How did you select the volatility meta-parameter of WHR? handicap values?


I did some optimization runs, and came up with 300 Elo^2/day, somehow. You can configure the library like this:

@whr = WholeHistoryRating::Base.new(:w2 => 17)

I know 300 seems like a lot. But it does ...
by pete
Wed May 30, 2012 8:41 am
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.

So after 5 games (3 wins 2 losses) I still don't have a rank. This is somewhat frustrating and not encouraging me to carry on trying. In general I prefer servers that allow one to self-select a starting rank, and find KGS quite annoying, but even KGS gives me a rank after 2 games. Kind of off-topic ...
by pete
Wed May 30, 2012 8:26 am
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.


60 elo for a handicap stone? That is far too low! KGS uses 148 per rank for 30k-5k, and 226 per rank for 2d+ (The constants are given in a different form here m log(e^0.85)*400=148 to convert to Elo form). EGF uses similar numbers. Besides, even using your too low value of 60, this is just a 10 ...
by pete
Tue May 29, 2012 4:30 pm
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.


player gives anchor 600 Elo advantage (maybe 3 stones, depends on your model), 50% wins


Yes, giving it crazy input can produce crazy output. I should have documented the handicap parameter better, but I'm not sure what the exact range is.

On GoShrine, handicap values for a single stone range ...
by pete
Tue May 29, 2012 7:11 am
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.

BTW, this is what I would do in a server: give the lower bound of the confidence interval as player rating. It has the advantage of giving players an incentive to play more, as the bound would slowly go down when they stop playing. This would be unlike KGS, where the best way to increase one's ...
by pete
Mon May 28, 2012 9:36 pm
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.

I noticed there is a bit of rating drift. With WHR, you can set bots to have a constant rating. That should prevent drift.

Also, I played a few games (account Remi) and still don't have a rating. Do games against bots count?


RE: rating drift, it seems that on the whole, the mean & spread of all ...
by pete
Thu May 24, 2012 12:38 pm
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.

I suppose the value of each handicap combination should itself be determined by Bayesian methods...

I did do some analysis based on game results to help determine the handicap weighting function in GoShrine. It's also constrained by the fact that ranks (non-elo, but kyu-dan ranks) themselves are ...
by pete
Thu May 24, 2012 12:13 pm
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.



Hi Pete,

I am glad you implemented my algorithm. I wonder how you deal with handicap. In my early experiments, I found that the value of a one-stone handicap is much higher for stronger players.

Rémi

The ruby gem primarily supports a handicap that is a fixed elo amount for a given game. I ...
by pete
Thu May 24, 2012 11:32 am
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.


As i had understood, WHR requires a massive recalculation with each result right? Have you benchmarked your solution?

I have about 40k games I'm putting in it right now. To update the two involved players' ratings after a new game is a tiny fraction of a second, and only grows with the number of ...
by pete
Sun May 20, 2012 2:50 pm
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Re: Whole History Rating open source implementation.

coffeeimam wrote:I believe this is the repo itself, for those who are looking: https://github.com/goshrine/whole_history_rating


Sheesh. Thanks coffeiamam! I updated the post.
by pete
Sun May 20, 2012 10:28 am
Forum: Announcements
Topic: Whole History Rating open source implementation.
Replies: 39
Views: 22769

Whole History Rating open source implementation.

The core of the rating engine used by GoShrine is now open source. It's an implementation of Rémi Coulom's Whole History Rating method with support for handicaps.

https://github.com/goshrine/whole_history_rating

If anyone ends up using it anywhere, I'd love to hear about it.

-Pete