![](https://damforum.nl/bb3/images/ua.png)
Plagiarism
-
- Posts: 1368
- Joined: Thu Jun 20, 2013 17:16
- Real name: Krzysztof Grzelak
Plagiarism
I have a question. How to check if another program does not use the code of a program.
Re: Plagiarism
There might be several levels (with difference in acceptance by the community), with several levels of detection.
Use code and data as is.
In some cases it might be acceptable, for example Ed allowed others to use the 8P DB and corresponding drivers.
And in the past many 6P DBs were based (both data as code) on the work of Michel and Harm.
General accepted, as all DBS (if they contain no errors) should yield the same results, not detectable, but it might be good to mention that somewhere.
One can code ideas of other programs , but not use the code as is.
Here are many examples like the base alpha-beta and all kinds of search enhancements like aspiration windows, killers, hast table and LMR (too name a few).
Think in general there is no exclusive right for ideas, and it is common practice to share and use.
Were things become critical is the evaluation function.
Basically the DNA of the program, and which result in a recognizable fingerprint.
I guess that (for example) using the ideas of Fabien (so the way positions are evaluated) is something which others might use (or already used in the past like Michel with Dragon).
However using exactly the same code and data-file is not done.
Bert
Use code and data as is.
In some cases it might be acceptable, for example Ed allowed others to use the 8P DB and corresponding drivers.
And in the past many 6P DBs were based (both data as code) on the work of Michel and Harm.
General accepted, as all DBS (if they contain no errors) should yield the same results, not detectable, but it might be good to mention that somewhere.
One can code ideas of other programs , but not use the code as is.
Here are many examples like the base alpha-beta and all kinds of search enhancements like aspiration windows, killers, hast table and LMR (too name a few).
Think in general there is no exclusive right for ideas, and it is common practice to share and use.
Were things become critical is the evaluation function.
Basically the DNA of the program, and which result in a recognizable fingerprint.
I guess that (for example) using the ideas of Fabien (so the way positions are evaluated) is something which others might use (or already used in the past like Michel with Dragon).
However using exactly the same code and data-file is not done.
Bert
-
- Posts: 1368
- Joined: Thu Jun 20, 2013 17:16
- Real name: Krzysztof Grzelak
Re: Plagiarism
The more I mean about how to check if a program uses code from another program.
Re: Plagiarism
In the end one needs to have a look at the source code.
Many programmers in this forum can recognize code fragments from other programs.
Bert
Many programmers in this forum can recognize code fragments from other programs.
Bert
-
- Posts: 1368
- Joined: Thu Jun 20, 2013 17:16
- Real name: Krzysztof Grzelak
Re: Plagiarism
Bert, how to detect that a programmer is using someone else's code in his program.
-
- Posts: 28
- Joined: Fri Jun 05, 2015 10:30
- Real name: Igor Le Masson
- Location: Brazil
Re: Plagiarism
There are a lot of techniques, most of them non-trivial and based on reverse-engineering tasks and move pattern similarity deep analysis.
Just for historical reference occurred on chess community: Rybka plagiarism case
Just for historical reference occurred on chess community: Rybka plagiarism case
-
- Posts: 1368
- Joined: Thu Jun 20, 2013 17:16
- Real name: Krzysztof Grzelak
Re: Plagiarism
For God's sake we write about draughts rather than chess.igorlemasson wrote:There are a lot of techniques, most of them non-trivial and based on reverse-engineering tasks and move pattern similarity deep analysis.
Just for historical reference occurred on chess community: Rybka plagiarism case
-
- Posts: 1722
- Joined: Wed Apr 14, 2004 16:04
- Contact:
Re: Plagiarism
See the RYBKA_FRUIT.pdf report in the first post on this thread: http://www.open-chess.org/viewtopic.php?f=5&t=1104Krzysztof Grzelak wrote:For God's sake we write about draughts rather than chess.igorlemasson wrote:There are a lot of techniques, most of them non-trivial and based on reverse-engineering tasks and move pattern similarity deep analysis.
Just for historical reference occurred on chess community: Rybka plagiarism case
It explains how compare program binaries through reverse engineering en similarity analysis
-
- Posts: 1368
- Joined: Thu Jun 20, 2013 17:16
- Real name: Krzysztof Grzelak
Re: Plagiarism
A brief question as to how to do this analysis. Remember that you do not know programming.Rein Halbersma wrote:See the RYBKA_FRUIT.pdf report in the first post on this thread: http://www.open-chess.org/viewtopic.php?f=5&t=1104
It explains how compare program binaries through reverse engineering en similarity analysis
Re: Plagiarism
Hi KrzysztofKrzysztof Grzelak wrote:A brief question as to how to do this analysis. Remember that you do not know programming.Rein Halbersma wrote:See the RYBKA_FRUIT.pdf report in the first post on this thread: http://www.open-chess.org/viewtopic.php?f=5&t=1104
It explains how compare program binaries through reverse engineering en similarity analysis
I think that without any knowledge in programming you will not be able to do it yourself. Reverse engineering and others programming tricks must be knew.
Best regards
Catherine.
-
- Posts: 1368
- Joined: Thu Jun 20, 2013 17:16
- Real name: Krzysztof Grzelak
Re: Plagiarism
Well that alone does not solve my problem during my future tournaments. How do I know if a particular engine is allowed to enter the tournament or not. Another thing is that if the programmer's file (engine) is encrypted by the programmer then how to check if the programmer is using another program code. At one time Bert Tuyt wrote that it is easy to check, only wish he did not write like.Catherine wrote:Hi Krzysztof
I think that without any knowledge in programming you will not be able to do it yourself. Reverse engineering and others programming tricks must be knew.
Best regards
Catherine.