16th World Computer Chess Championship In Progress
vmartell writes "The 16th World Computer Chess Championship is now in progress in Beijing, as part of the Computer Games Championship. Currently in the lead are Rybka 3.0, recognized as the world's strongest chess engine and Hiarcs, another commercial engine. Another curiosity is a Java ME based engine running on a Nokia phone, which is currently being trounced by the other engines. A very interesting sideline: before the computer tournament, a Women's Grandmaster played two games against Rybka. The result? Rybka won both games!"
How much of the "skill" in computerized chess comes from the programmers and how much comes from the raw cpu horsepower available? TFA was quoting 40-core boxes competing with Nokia cell phones.
Transliterated back into Russian, Rybka means Fish. Maybe I don't know the joke, but I've never known fish to be particularly strong chess players.
Sam ty sig.
Does chess really need to separate the rankings between male and female champions? Isn't this a sport that gender really doesn't factor in?
Chess has become boring, like checkers or backgammon.
To even competitively play at the local club level you really need a ridiculously deep memorization of openings and endings. At the grandmaster level, they've basically memorized the tables used by computers.
Average games of chess only last around 60 moves. The depth of opening and closing books increasingly has reduced the middle game of actually interesting play. If it's not down to only 1-5 moves, it will be soon.
The game will be dead--or at least not interesting enough to be seriously played--long before it is solved.
P.S. You arrogant fans of Go can frak yourselves. Where do you think the scientists will go once they're done with chess. Enjoy it while it lasts.
obviously no deficiencies vs. no obvious deficiencies
http://en.wikipedia.org/wiki/Rybka
The page also goes into detail on the name...
No sig today...
"P.S. You arrogant fans of Go can frak yourselves. Where do you think the scientists will go once they're done with chess. Enjoy it while it lasts."
Considering Go's harder. I'd say they're welcome to try.
Shai Schticks:"You don't make peace with friends, you make peace with enemies"
"So in other words, it's not the the number of cycles you have, but how you use them."
That's what she said.
Shai Schticks:"You don't make peace with friends, you make peace with enemies"
When I think of powerful chess programs, I think of Deep Fritz. It did beat the human World Champion after all. Does anyone know why Deep Fritz isn't competing?
This story, for example, apparently has zero comments.
Here I was thinking I could get a Turk related first post :( At least Hiarcs almost rhymes with Turk. I didn't actually realise that the name was a reference to this - should have known what with the rest of the series being full of references.
Is anyone really surprised that a computer beat a human grandmaster twice in a row? As computers get more powerful, it is inevitable that they will completely outclass humans in games with perfect knowledge. There were times when Kasparov fooled Deep Blue's algorithms a couple of times (presumably giving it a piece or two in return for a square with significant strategic advantage), but they just trained it so that it wouldn't fall for those tricks again. I honestly wouldn't be surprisd if a grandmaster never won a tournament game against a chess supercomputer ever again.
which is totally what she said
There are several commercial use for better engines:
1) Game analysis. When you have played a game against and lost, you try to understand why you lost. Sometimes it is because you made an obvious blunder, but when you get better at the game, you start loosing for strategical reasons (lost control of a certain square, etc, etc). Having a good engine helps you try new ideas, and play a lot of what-if scenarios
2) Game understanding. When you follow a live tournament between grandmasters, having a good engine can give you an explanation about what the underlying ideas are ("Why doesn't he plays Nb6? You try it, and get the answer instantly")
3) Correspondence & Centaur Chess. Correspondence chess are long running games where both players have access to whatever they want. It delivers very subtle games, where the strategy is a very important aspect, as all the tactical blunders are removed by the use of good chess engines. Centaur chess is the same with lower time control.
And, of course, bragging rights are important too: having a better engine than other people in the chess club is a bit like having the better graphic card among fps players...
As you may have seen, playing against the engine is not one of the uses. Rybka is supposedly at 3200 elo. By definition, 200 elo points higher means you have a 75% win probability. The current world champion is at 2800, which means that he have a 6% win probability against rybka. Good club chess play is around 2000 (it takes several years to reach that level -- at that level, you can generally play blind, or multiple opponents, etc, etc). Such players have a 1 against 4000 chance against a 3200 player. Which means zero chance...
After having dealt the last seven years with the anime-obsessed crowd invading Go, and (at least in my limited experience) being nothing but whiny about how much there is to learn, I'd say that engineers, chess players, and heads of state (though to be fair, in this case, he was merely Prime Minister and was assassinated trying to avoid the militarization of Japan pre-WWII) would be welcome back into the fold.
On that note, I wouldn't say I'm an arrogant Go player. I've played chess at the local club level for awhile, but then I realized that I'd rather enjoy a game of chess with a friend over a beer out at the park than several hours of study to keep my opening and endgame up. I picked up Go about a year after that, and while I'm not very good, I enjoy it and enjoy teaching it to others.
I had a similar experience in 1978: I had written a neat but slow chess program in Basic for the Apple II. The guy who organized the first West Coast Computer Fair chess tournament encouraged me to enter, and I did not fair so well against the programs nicely crafted in assembler language. Still, since I was handing out free copies of my program, and people liked that, it was a fun experience.
I actually did a little chess programming last week. I am finishing up the 3rd edition of my Java AI book (self plug: a PDF version will always be available on my web site) and since I have generally "caught the Java generics" disease, I re-coded the chess alpha-beta search example using the new collection classes and generics - it ran so much slower than the old native data type + array version that I archived and tossed the new version :-)
P.S. You arrogant fans of Go can frak yourselves. Where do you think the scientists will go once they're done with chess. Enjoy it while it lasts.
This is obviously trolling, but what the heck. Chess has been dominated by computers for quite some time now - many have moved on to Go, and they still fail to beat amateur-level Go players. There are practical reasons why a Go AI is more difficult to program than a Chess one, which I'm sure by the time this has been posted will be explained in great detail by other replies.
What I want to explain is why Go is better than Chess. It is not because it is more difficult for computers. While Chess doesn't really scale well, Go can be scaled down quite nicely to where the number of moves that have to be read out is equivalent to that of a Chess game. On 9x9 boards, Go AIs are rapidly catching up to humans. MoGo, for instance, consistently beats many amateur-level go players on 9x9's. There is more lost in the transition to a smaller board than simply brute-force reading, but the example still stands.
The reason Go is better than Chess is that unlike Chess much of it's depth is a natural, mathematical result of the very simple rule set. Essentially the entire game:
Players take turns placing pieces on the board. When a piece or group of pieces by one team is surrounded (ie, no empty spaces touching any of them in the group), the pieces are removed from the board. Whoever controls the majority of the board at the end wins.
There are details missing there about things such as defining who controls the majority of the board, but with one exception (ko) that's really all the game is. Everything, all of it's depth, is a mathematical result. Interesting patterns emerge, comparable to things like prime numbers or pi. For example: From the rules I put above it should quickly become apparent that I could just surround the opponents pieces that surrounded mine, and my opponent could do the same. No piece would ever really be safe, or ever really be captured that could not be replaced. No rules had to be made to remedy this: go naturally has a system in place where pieces cannot be captured. It's just plain cool. (See: "eyes").
For the most part, Go is not about brute-force reading so much as recognizing and understanding the patterns. I don't have to mathematically derive the formula for the area of a circle each time I need to calculate it - once I understand the concept I can retain it. Go is very similar. That's not to say there is no brute-force reading. For example: one of the interesting phenomenon in Go is the "ladder," which results in one player chasing the other across the board diagonally. The winner will be determined based on whose pieces (if any) are met along the way. As a result, people just read out the very simple pattern across the board rather than playing the whole thing out.
Go isn't flawless. There is a situation (ko) which essentially breaks the game. It's comparable to where in Chess if both players repeatedly make the same moves the game becomes a draw. There had to be rules added to deal with this situation, and while they do add even more depth and change the way the game is played, it is an area where Go's awesome depth-through-simplicity is marred.
I recognize that Chess does have some depth to it other than just brute-force reading. There are concepts like pinning which result from the rules, but they're far fewer and generally not as interesting. There's also many concepts which carry between the two, such as Go's sente/gote vs Chess's tempo.
Go is less about reading than it is about understanding. This, combine with the cool patters and concepts which emerge, is why Go is better than Chess. This is largely opinion; someone who plays Go is not necessarily a better, smarter person than someone who plays Chess. It is possible for an intelligent, healthy, mentally-stable human to prefer Chess's convoluted rules, simpler concepts and overwhelming amounts of brute-force reading. They'd just be silly for it.
"A witty saying proves nothing." - Voltaire