The programmers can't agree over the Fruit/Rybka issue, so how would I know what the truth is?Sean Evans wrote:Fabien created Fruit, Vas copied Fruit....has the little light bulb gone off yet![]()
Try to have some manners for a change.
Moderator: Ras
The programmers can't agree over the Fruit/Rybka issue, so how would I know what the truth is?Sean Evans wrote:Fabien created Fruit, Vas copied Fruit....has the little light bulb gone off yet![]()
Did you read? Nothing is similar.hgm wrote:Not sure what this has got to do with the issue of whether rule #2 is about copyrights. And it seems to me that in either case it is not the number of differences that is relevant, but how much was similar.
I could post the same message to you, Frank.Frank Quisinsky wrote:Hi Graham,
read not only what you want to read. The thread , the forum is full of information which reflects a different opinion than yours. You should try to respect it.
Best
Frank
Nice try, no cigar.bob wrote:Differences do not matter, it is the similarities and the number of them that violate rule 2. 75% of what you cite above comes from the mailbox/bitboard differences. Irrelevant in this context.Rebel wrote:It's what I said all along, if you can't proof a derivative work then what the verdict was about is the usuage of "too many" ideas.
And even that is wrong.
Every major evaluation ingredient is coded differently, mobility, king safety, passed pawns, double pawns, backward pawns, Rybka is missing Fruit's late endgame knowledge, Rybka has a material table – different from Fruit. Rybka does not contain Fruit's quad function, Rybka’s trapped bishop evaluation is different, rook evaluation is different, bishop pair evaluation different and most importantly, Fruit evaluates in stages in a unique way whereas Rybka adds directly to its score (as every other program on the planet does).
Other key differences between Fruit and Rybka:
1.Time control is different
2.Fen parsing is different
3.Rybka extracts the mainline from the transposition table (TT), Fruit via the classic triangle table
4.Rybka 1.0 beta displays a mainline of maximum of 10 moves, Fruit produces much longer variations
5.Rybka uses a bitboard board representation whereas Fruit is mailbox
6.Rybka’s pawn value is 3200 (which is unique), Fruit uses the classic value of 100
7.The order in the evaluations of Fruit and Rybka are not similar
8.Rybka has lazy evaluation, which is absent in Fruit
9.Futility pruning is different between the two programs
10.Rybka uses Late Move Reductions (LMR) whereas Fruit uses history reductions
11.Fruit uses a history table which is absent Rybka.
12.Fruit only has one evaluation table (king safety) while Rybka has many
13.The two programs have a different move format
14.Rybka does not handle promotions to minor pieces
15.The two programs have different hash table code
16.They have different handling of repetitions and the 50-move rule in search
17.Fruit maintains piece-lists which are not present in Rybka
18.Fruit maintains a pseudo "bitboard" for pawns, Rybka has the real thing.
19.Contrary to Fruit, Rybka needs to update 4 rotations of occupancy bitboard
20.Contrary to Fruit, Rybka updates a rough estimate of material balance with weights of 1:3:3:5:10 (in the evaluation this value is then corrected by a delta obtained from the material table)
21.Fruit has a 16*16 square mailbox, Rybka has an 8*8
22.The programs have different Zobrist hash keys
23.The programs have different user interface options
We found 35 indisputable differences (some of which are very fundamental), not counting the ones that are debatable such as the Piece Square Tables (PSTs) and the contents of the TT.
Doesn't fit the definition of a derivative work.
Another BIG upset is that,Graham Banks wrote:I could post the same message to you, Frank.Frank Quisinsky wrote:Hi Graham,
read not only what you want to read. The thread , the forum is full of information which reflects a different opinion than yours. You should try to respect it.
Best
Frank
I am not a programmer.
If programmers disagree over the issue, then you should respect the fact that non-programmers like me cannot possibly know which group of programmers is right and which group isn't.
Regardless of this, what really upset me was the way that Vas and his family were treated like shit.
Hello Frank,Frank Quisinsky wrote:Hi Sedat,
Please do not speak always of Rybka. Please talk about Rybka 1. What is a causal chain? Easy to learn if you look into the past, must not be a computer chess topic.
Best
Frank