Re: Houdini Engine Origins
Posted: Wed Jan 19, 2011 4:27 pm
Yes, I got the same with:

Houdini w32 1_CPU build 2010-05-15

Houdini w32 1_CPU build 2010-05-15
So what's you're telling me is that it is fine for the author to lie about the origins of his engine and steal code from others? Dude, you're morally messed up.Dr. Ivannik wrote:Another guy that dont care. And until the author fess up no Houdini for Peter. Will the world ever be ok until Peter gets his HoudiniPeter C wrote:I dug up this old thread from Talkchess, which has some pretty conclusive evidence that Houdini comes from Ippo*.
I wouldn't care that Houdini comes from Ippo*, except that the author consistently lies that it doesn't. So, no Houdini for me.
Peter![]()
![]()
![]()
Dr. Ivannik
are you talking about houdini or about rybka here ?Peter C wrote: So what's you're telling me is that it is fine for the author to lie about the origins of his engine and steal code from others? Dude, you're morally messed up.
Peter
PeterPeter C wrote:So what's you're telling me is that it is fine for the author to lie about the origins of his engine and steal code from others? Dude, you're morally messed up.Dr. Ivannik wrote:Another guy that dont care. And until the author fess up no Houdini for Peter. Will the world ever be ok until Peter gets his HoudiniPeter C wrote:I dug up this old thread from Talkchess, which has some pretty conclusive evidence that Houdini comes from Ippo*.
I wouldn't care that Houdini comes from Ippo*, except that the author consistently lies that it doesn't. So, no Houdini for me.
Peter![]()
![]()
![]()
Dr. Ivannik
Peter
Please read the thread.Dr. Ivannik wrote:Lock this thread or apologize to Robert Houdart for your baseless and silly allegations.
There is sufficient evidence posted in this thread (disassemble/decompilations, behavior in strange positions, evaluations, PVs, etc) that it's pretty obvious that the author did steal something. Explain how Lance Perkins's disassembly of Houdindi matches almost exactly the disassembly of IvanHoe for example.Dr. Ivannik wrote:PeterPeter C wrote:So what's you're telling me is that it is fine for the author to lie about the origins of his engine and steal code from others? Dude, you're morally messed up.Dr. Ivannik wrote:Another guy that dont care. And until the author fess up no Houdini for Peter. Will the world ever be ok until Peter gets his HoudiniPeter C wrote:I dug up this old thread from Talkchess, which has some pretty conclusive evidence that Houdini comes from Ippo*.
I wouldn't care that Houdini comes from Ippo*, except that the author consistently lies that it doesn't. So, no Houdini for me.
Peter![]()
![]()
![]()
Dr. Ivannik
Peter
I personally don't know if any author lied about anything or stole anything. These allegations are made by other people like yourself. I don't know where people like you come from??? Accusing people of lying and stealing and then questioning my moral standing in life. In the end I will be judged for my moral character but not by you peter. I am embarrassed for you!! I hope you get your head right.
Thank you
Dr. Ivannik
I guess it applies to both (Rybka maybe more so, since that was actually a GPL violation whereas IvanHoe is in the public domain).thorstenczub wrote:are you talking about houdini or about rybka here ?Peter C wrote: So what's you're telling me is that it is fine for the author to lie about the origins of his engine and steal code from others? Dude, you're morally messed up.
Peter
I think that actually might be in the weaker part of the evidence given here. As Gerd Isenberg put it on the Chess Programming wiki:Explain how Lance Perkins's disassembly of Houdindi matches almost exactly the disassembly of IvanHoe for example.
So these could point back to the ideas/code dichotomy in any event. The postings of Jeremy, with identical evals from a variety of positions, seems to me to be more robust as evidence.The idea to index the material table in the same manner by combined counters of queens, rooks, light and dark bishops, knights and pawns, and to calculate piece counters from that table-index by a sequence of mod/div operations by {2,2,3,3,2,2,2,2,3,3,9,9} might be considered obvious after studying the mentioned source code, and if applied that scheme, there is hardly anything to avoid a sequence of almost identical x86 machine code with same constants for reciprocal multiplication.
Oh. I know very little about chess programming, so 2 nearly identical sequences of assembly looked pretty suspicious to me. Thanks.BB+ wrote:I think that actually might be in the weaker part of the evidence given here. As Gerd Isenberg put it on the Chess Programming wiki:Explain how Lance Perkins's disassembly of Houdindi matches almost exactly the disassembly of IvanHoe for example.So these could point back to the ideas/code dichotomy in any event. The postings of Jeremy, with identical evals from a variety of positions, seems to me to be more robust as evidence.The idea to index the material table in the same manner by combined counters of queens, rooks, light and dark bishops, knights and pawns, and to calculate piece counters from that table-index by a sequence of mod/div operations by {2,2,3,3,2,2,2,2,3,3,9,9} might be considered obvious after studying the mentioned source code, and if applied that scheme, there is hardly anything to avoid a sequence of almost identical x86 machine code with same constants for reciprocal multiplication.