FIRE14 Detection of SOurce COde Re-use

<p>This data&nbsp;was used for the PAN shared task on source code re-use detection at FIRE2014.&nbsp;</p> <p>Please find the task description at&nbsp;https://pan.webis.de/fire14/pan14-web/index.html.</p> <p><strong>THIS DATA</strong></p> <p>For the training phase we provide an annotated corpus including with the programming language extensions. It includes information about whether a text fragment has been re-used and, if it is the case, what its source is.</p> <ul> <li>The collection consists of source codes written in Java and C.</li> <li>Re-use is commited in both programming languages but ONLY at monolingual level.</li> <li>The Java collection contains 259 source codes from 000.java to 258.java.</li> <li>The C collection contains 79 source codes from 000.c to 078.c.</li> <li>Relevance Judgements represent re-use in both directions(a&rarr;b and b&rarr;a)</li> </ul> <p>In the test phase the only annotation that will be provided in the corpus is the programming language extensions.</p> <ul> <li>It is divided by programming language (C/C++ and JAVA) so you do not need any pre-process to identify the programming language of the source codes.</li> <li>Each programming language folder contains 6 folders (A1, B1, B2, C1 and C2) that contains a specific scenario with monolingual re-use.</li> <li>There is not re-use between scenarios so you just need to look for re-used cases among the source code files inside each folder.</li> <li>The name of the files consists of the name of the task which they belong plus an identifier. For example, file &quot;B10021&quot; belongs to scenario B1 and its identifier number is 0021.</li> <li>It could not exist re-use between source codes that belong to different scenarios. For example, you do not have to submit a re-used case between files &quot;B10021&quot; and &quot;B20013&quot;. The first one belongs to scenario B1 but the second one belongs to B2.</li> </ul>