It's all pretty simple, rule #2 since day-1 is about copying. The word "derivative" in the Fabien letter says it all. Copying code + changes makes a derivative. But the R/F case has changed the landscape, if you take too much ideas you are toasted.BB+ wrote:mjlef wrote:[...]you [Rebel] included a huge mix of sophisticated and original ideas. We did not see that in the Rybka EXEs we examined. [...] Looking over your documentation, You did not take almost the whole evaluation from any single program. [...] I would expect if we did an evaluation of Rebel. etc we would find it to be very unique. [...]It seems to me that (in the context here) MarkL meant "sophisticated and original ideas in the evaluation"? Other than the material imbalance table, what much is there along these lines in Rybka 1.0 or 2.3.2a?marcelk wrote:I'm sorry but the panel did not consider or look for "sophisticated and original ideas" in Rybka or they had excrement in their eyes as there are so many of them it is difficult to miss.
I agree with you here that there is no (complete) relief from mere enhancements, but I don't think the interpretation is that hawkish (the R/F verdict was strongly punitive, but for a different reason). The LION++ defense made such a claim ("all the newly developed routines which surrounded the ideas of Letouzey", in Jaap's words), but the decision in that case didn't exactly address the matter. In the R/F ordeal, as VR clearly did go significantly beyond Fruit, I had suggested (and others did the same -- see GI's comments in the Report) simply re-naming the winner Rybka/Fruit and author Letouzey/Rajlich -- but this would have required commitment from both FL and VR.marcelk wrote:Besides, how does including "sophisticated and original ideas" relief oneself from violating the hawkish interpretation of rule #2?
In this regard, one can re-read Jaap's editorial in ICGA Journal 20/1 on Augmented Ideas, particularly the (brief) comment on Donninger's challenge, before switching to the explicit Crafty/Gunda case: Since both teams gave due credit to CRAFTY as their original source, it is comparable to using ideas from articles while giving appropriate reference. Nevertheless, the question remains to what extent can we prolong the similarity of publications and programs. For articles, we do not allow plagiarism. For algorithms and programs I believe we are in a state of flux. Yet, the researcher who is the originator of the ideas should always be given pride of place. [As Jaap notes prior to this, he does not give any real answers: the best we can do is to make these problems explicit].
Here is the Donninger ensemble in full (from page 240, ICGA Journal 19/4):Chrilly Donninger wrote:7. NIMZO-3, A CHALLENGE FOR THE ICCA TOURNAMENT RULES?
The probably greatest scandal in the history of the ICCA tournaments was the attempt of the German engineer Langer to win the WMCC with a cloned program of R. Lang. In NIMZO-3, not only the ORACLE, but also the whole search process, the opening book and a so-called knowledge base, can be substantially modified by the user. What happens if Langer buys NIMZO-3, writes his own ORACLE, optimizes the search parameters along his own criteria, creates a new opening book...? The program would play differently from the program he has bought and, he would have done, with better tools, a substantial part of the work of a classical chess programmer. I personally would encourage the efforts of Langer as long as he does not deny the NIMZO roots of his program and as long as he also makes it clear, that it is his own version of the program. An entry NIMZO-Langer would be, from my point of view, perfectly acceptable.
The cases of Nimzo-3 and Lion are clear, derivatives. Using someone else code.