Uri Blass wrote:jesper_nielsen wrote:Dann Corbit wrote:
<<<SNIP!>>>
I don't think DanChess belongs in that group. DanChess did borrow the SEE from crafty (albeit with changes to accomodate his data structures). However, that was an unintentional violation of what Dr. Hyatt considered acceptable. The other instances were total program snatches and stamping a new name on them (El Chinito did have some interesting ideas injected into it, but it was a clear 'program snatch').
Now, to step back, DanChess stepped over the line. But it was one toe over the line. The other two programs mentioned were 29' broad jumps.
Now you have me worried!
In Pupsi i use the SEE algorithm from Crafty.
I state in the readme, that this is so: "SEE evaluation. (As seen in Crafty)"
I was under the impression, that this was OK, but maybe i was wrong?!
Where does the line go?
Kind regards,
Jesper
The problem with DanChess was not only SEE based on my memory.
I remember that
DanChess took some evaluation code from Crafty(not as copy and paste but I remember cases when he used the same evaluation numbers
so it was not only copying the idea).
I remember that DanChess also used the same type of bitboards as Crafty.
Uri
Here is the DanChess controversy, relived in all its glory:
http://www.stmintz.com/ccc/index.php?id=349222
In summary the bones of contention were:
1. Bitboard used the same numbering scheme (A1 = 0...)
2. King tropism tables were identical
3. SEE used the same decisions.
Subsequent rewrites of DanChess removed every shred of crafty code and his latest programs are very un-crafty like.
In Daniel's case it was (IMO) innocent ignorance as to what constitues fair use. He did not try to hide the crafty association (but he did fail to give credit initially). He was a micron away from giving up chess programming completely because of his bitter dissappointment.
I guess that the whole DanChess misunderstanding would have been completely avoided by sending an email to Dr. Hyatt when Daniel first started the project and also by giving credit where credit is due in the readme file. (I think that Dr. Hyatt is a very fair person and also that he was really sick and tired of things like BIONIC {which I nicknamed 'Believe It Or Not It's Crafty!'} and Voyager [along with several others] which increased the strength of his response due to his irritation).
The bottom line (as I see it) is to keep things open and above board and give credit where credit is due. Ask permission before you do *anything* with someone else's code. These simple steps will prevent CCC tornados. At least (with my wishful thinking) I hope so.