Datasets:

Formats:
parquet
Languages:
English
ArXiv:
Tags:
code
DOI:
Libraries:
Datasets
pandas
License:
Areyde commited on
Commit
33818ef
1 Parent(s): e96494f

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +3 -0
README.md CHANGED
@@ -327,6 +327,7 @@ configs:
327
  This is the benchmark for the Bug localization task as part of the
328
  🏟️ [Long Code Arena benchmark](https://huggingface.co/spaces/JetBrains-Research/long-code-arena).
329
 
 
330
  The bug localization problem can be formulated as follows: given an issue with a bug description and a repository snapshot in a state where the bug is reproducible, identify the files within the repository that need to be modified to address the reported bug.
331
 
332
  The dataset provides all the required components for evaluation of bug localization approaches in real project-level large-scale data collected from GitHub, including:
@@ -335,6 +336,8 @@ The dataset provides all the required components for evaluation of bug localizat
335
  * List of files that should be changed in order to solve the bug;
336
  * Other additional data and metrics that can be useful in developing new approaches.
337
 
 
 
338
  The collected dataset was carefully filtered, enhanced with useful metrics and, what's more, manually labeled, which assures the data quality and provides a golden subset of good examples for evaluation.\
339
  Moreover, the dataset was split into several categories, namely:
340
 
 
327
  This is the benchmark for the Bug localization task as part of the
328
  🏟️ [Long Code Arena benchmark](https://huggingface.co/spaces/JetBrains-Research/long-code-arena).
329
 
330
+
331
  The bug localization problem can be formulated as follows: given an issue with a bug description and a repository snapshot in a state where the bug is reproducible, identify the files within the repository that need to be modified to address the reported bug.
332
 
333
  The dataset provides all the required components for evaluation of bug localization approaches in real project-level large-scale data collected from GitHub, including:
 
336
  * List of files that should be changed in order to solve the bug;
337
  * Other additional data and metrics that can be useful in developing new approaches.
338
 
339
+ All the repositories are published under permissive licenses (MIT, Apache-2.0, BSD-3-Clause, and BSD-2-Clause). The datapoints can be removed upon request.
340
+
341
  The collected dataset was carefully filtered, enhanced with useful metrics and, what's more, manually labeled, which assures the data quality and provides a golden subset of good examples for evaluation.\
342
  Moreover, the dataset was split into several categories, namely:
343