Re: FIDE Rules on ICGA - Rybka controversy
Posted: Sat May 16, 2015 9:39 pm
And now I am eager what Mark has to say.Chris Whittington wrote:hyatt wrote:You said "this":
hahahahaha!! can you read ASM? find it yourself and work it out. Ridiculous question.There's a Rybka bonus (in the discussed code) for rook behind blocked enemy pawn chain, a common pattern.
"rybka bonus for rook behind blocked enemy pawn chain, a common pattern" But you didn't say that?
There is no such bonus. There is a bonus for being on a file in front of all pawns. Which would seem to be a bit silly with a white pawn on e7, white rook on e8, which is a KNOWN bad way to defend said pawn. But of course, his rule is "perfect" right? White gets to play without its rook, and probably lose that pawn quickly as well. Black puts his rook BEHIND said pawn and gets to use it normally.
It is pretty easy to see what he intended. The rook lift idea. But he didn't implement it very well and left a significant hold that was certainly unintentional. If there is a black pawn chain b7/c6/d5 I would certainly not move my rook off the open e file to get it behind that d5 pawn, and let black have the actual open e file while I busily attack a pawn I can't take. It is just a poorly written piece of code, with the intent as already explained, with the actual implementation having a fairly ugly mis-evaluation.
To make it simple for you, common situation - two pawns on same file in opposition to other, not passed. We have three possibilities for a rook:
Both Fruit and Rybka give no bonus to the wR here, wR behind own pawn:
bp
..
..
wp
..
wR
Fruit gives no bonus to the rook here, we might assume the Rook came down an open file and swung over to attack the pawn from in front:
Rybka gives it a bonus (you call this half-open file bonus. Obviously it isn't). Humans would like the rook here too.
bp
..
wR
..
..
wP
Fruit gives no bonus to the Rook here. Again, we might assume the Rook came down an open file and swung across behind the pawn.
Rybka gives this a large bonus (erroneously, again, you call it open file bonus, obviously it isn't). Humans would do the same, they like this position a lot.
wR
..
bp
..
..
wp
So, now you can imagine a closed pawn position, one open file:
Fruit, with its rook-pawn code, likes to get on the open file, that's it.
Rybka with its rook-pawn code, like to get on the open, but it also likes most to get behind the enemy pawn chain.
The bonus for being BEHIND THE BLOCKED ENEMY PAWN CHAIN is an EMERGENT PROPERTY of the Rybka code. It's creative and original, qualitatively different to Fruit (or Crafty at the time, for that matter). But it was dismissed as unimportant. By investigators who clearly don't understand chess, they just understand code. Which is not enough. This chess code is NOT the same. It is not even open file/semi open file code, as you tried to shoehorn it into in desperate attempt to claim Fruit equivalence.
For rook-pawn endings, this Rybka code is a big boost.
Some other points you made:
"Badly implemented". Who cares, even if true? This is about whether Vas plagiariased Fruit. We are looking for disimilarities in chess code, not your idea of good/bad code.
"it is done by rook on 7th code." Who cares and so what? This is about plagiarised or not. Not your idea of how to program ideas.
"the effect is unintentional". Maybe to you. Which doesn't mean you can mind read it into his brain. I'ld imagine it was perfectly intentional, he is a smart programmer and understands chess way better than you do. But so what? It is what it is. A qualitatively different chess coding.
"you can construct positions where the code is not useful". Watkins "with a wp on a7 etc ..." Sure you can disrupt what is effectively a pattern recognition with fanciful patterns. The Rybka code is general purpose, and there are always exceptions. But this is another giant SO WHAT? for our purposes (did Vas plagiarise Fruit?), the question is whether there is or is not a qualitative difference. There is. So you can remove this section from the Zach paper, he got it all wrong, called it unimportant, and the Watkins paper, who also didn't seem to comprehend the effect and was convinced to shoehorn code that was NOT open file code, into Fruits open file model. So he could score it against Rybka. Unreasonable. Probably unconscious bias. Should not even be being compared together. Not same thing.