Datasets:
Update README.md
Browse files
README.md
CHANGED
|
@@ -407,7 +407,6 @@ The following sections describe the utilities around the dataset, as well as dat
|
|
| 407 |
|
| 408 |
* Data streaming via [HFDataSource](https://github.com/anon-iclr-submission/benchname-baselines/blob/main/bug_localization/src/baselines/data_sources/hf_data_source.py).
|
| 409 |
Besides data loading, `HFDataSource` returns a datapoint for running the baseline along with the content of the repository at the state where the bug is reproducible (aka `base_sha` commit of the pull request that resloves the bug issue). \
|
| 410 |
-
All source code for working with the Git history of repositories (commits, diffs, etc.) is available in [`git_utils.py`](https://github.com/anon-iclr-submission/benchname-baselines/blob/main/bug_localization/src/utils/git_utils.py), as is an example of baselines, utilizing this dataset.
|
| 411 |
|
| 412 |
### Bug localization data
|
| 413 |
|
|
@@ -466,6 +465,5 @@ The metrics-related fields are:
|
|
| 466 |
### Repositories data
|
| 467 |
The compressed repositories are provided in the [repos](https://huggingface.co/datasets/anon-iclr-submission/benchname-bug-localization/tree/main/repos) section, separately from datapoints, to provide access to the various stages of repositories, saving their initial structure, as well as to reuse their content for different datapoints connected to the same repository.
|
| 468 |
To extract the required information from repositories, each `zip` file should be unarchived. Afterwords, we recommend to use [GitPython](https://github.com/gitpython-developers/GitPython) or [PyDriller](https://github.com/ishepard/pydriller) Python libraries to navigate through the repository history and extract its content on the required commit or calculate diff.
|
| 469 |
-
Most of the required utility methods are provided in our repository in the [`git_utils.py`](https://github.com/anon-iclr-submission/benchname-baselines/blob/main/bug_localization/src/utils/git_utils.py) file, so you may reuse them to access the required repository data.
|
| 470 |
|
| 471 |
##
|
|
|
|
| 407 |
|
| 408 |
* Data streaming via [HFDataSource](https://github.com/anon-iclr-submission/benchname-baselines/blob/main/bug_localization/src/baselines/data_sources/hf_data_source.py).
|
| 409 |
Besides data loading, `HFDataSource` returns a datapoint for running the baseline along with the content of the repository at the state where the bug is reproducible (aka `base_sha` commit of the pull request that resloves the bug issue). \
|
|
|
|
| 410 |
|
| 411 |
### Bug localization data
|
| 412 |
|
|
|
|
| 465 |
### Repositories data
|
| 466 |
The compressed repositories are provided in the [repos](https://huggingface.co/datasets/anon-iclr-submission/benchname-bug-localization/tree/main/repos) section, separately from datapoints, to provide access to the various stages of repositories, saving their initial structure, as well as to reuse their content for different datapoints connected to the same repository.
|
| 467 |
To extract the required information from repositories, each `zip` file should be unarchived. Afterwords, we recommend to use [GitPython](https://github.com/gitpython-developers/GitPython) or [PyDriller](https://github.com/ishepard/pydriller) Python libraries to navigate through the repository history and extract its content on the required commit or calculate diff.
|
|
|
|
| 468 |
|
| 469 |
##
|