Datasets:

Modalities:
Text
Formats:
parquet
ArXiv:
Libraries:
Datasets
Dask
License:
ryanse commited on
Commit
3cee0bc
·
verified ·
1 Parent(s): 8e720e4

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +2 -2
README.md CHANGED
@@ -44,7 +44,7 @@ configs:
44
 
45
  ## Introduction
46
 
47
- [SWE-bench](https://www.swebench.com/) is a popular benchmark that measures how well systems can solve real-world software engineering problems. To solve SWE-bench problems, systems need to interact with large codebases that have long commit histories. Interacting with these codebases in an agent loop using git can be slow and take up large amounts of storage space.
48
 
49
  This dataset provides the complete Python codebase snapshots for all problems in the [SWE-bench Verified](https://openai.com/index/introducing-swe-bench-verified/) dataset. For each problem instance, it includes all Python files present in the repository at the commit hash specified by the original SWE-bench Dataset.
50
 
@@ -54,7 +54,7 @@ The dataset consists of two main components:
54
  1. `file_content`: Contains the actual content of all unique files
55
  2. `problem_files`: Maps each problem instance to its relevant files
56
 
57
- Here's an example of how to load and use the dataset:
58
 
59
  ```python
60
  from datasets import load_dataset
 
44
 
45
  ## Introduction
46
 
47
+ [SWE-bench](https://www.swebench.com/) is a popular benchmark that measures how well systems can solve real-world software engineering problems. To solve SWE-bench problems, systems need to interact with large codebases that have long commit histories. Interacting with these codebases in an agent loop using git naively can be slow, and the repositories themselves take up large amounts of storage space.
48
 
49
  This dataset provides the complete Python codebase snapshots for all problems in the [SWE-bench Verified](https://openai.com/index/introducing-swe-bench-verified/) dataset. For each problem instance, it includes all Python files present in the repository at the commit hash specified by the original SWE-bench Dataset.
50
 
 
54
  1. `file_content`: Contains the actual content of all unique files
55
  2. `problem_files`: Maps each problem instance to its relevant files
56
 
57
+ Here's an example of how to load and use the dataset to access the files for a specific problem:
58
 
59
  ```python
60
  from datasets import load_dataset