Skip to content

Commit

Permalink
keep the latest version of script and data in the repo. Point to the …
Browse files Browse the repository at this point in the history
…release for the old version
  • Loading branch information
mohayemin committed Jan 29, 2024
1 parent 4812185 commit 864f919
Show file tree
Hide file tree
Showing 1,170 changed files with 12 additions and 81,529 deletions.
29 changes: 12 additions & 17 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,29 +1,24 @@
PyMigBench is a benchmark of Python Library Migrations.
This repository contains the data and code for the dataset.


## PyMigBench v2
This is the latest version of the dataset.
This includes all data from [PyMigBench v1](#pymigbench-v1) and additional migrations borrowed from the [SALM dataset](https://ieeexplore.ieee.org/document/10123560).
The data also includes more information per migration-related code change.
The dataset includes 3,096 migration-related code changes from 335 migrations between 141 analogous library pairs.
The data is available in the [v2](/v2) directory.
The current version, PyMigBench-2.0, includes 3,096 migration-related code changes from 335 migrations between 141 analogous library pairs.
This includes all migrations from [PyMigBench v1](#pymigbench-v1) and additional migrations borrowed from the [SALM dataset](https://ieeexplore.ieee.org/document/10123560).
The data also includes additional information per migration-related code change compared to v1.

The paper is published in FSE 2024.
The dataset is published through the FSE 2024 paper titled *Characterizing Python Library Migrations*.
We will add the citation info once it is available.
[Release 2.0.1](https://github.com/ualberta-smr/PyMigBench/releases/v2.0.1) points to the exact dataset linked to the paper.
We may update the [v2](/v2) directory to correct any mistakes or add more data and it may go out of sync with the paper.
So, for reproduction of the paper, use the release mentioned above.
For, the latest data, use the [v2](/v2) directory of the latest version of the repository.
[Release 2.0.2](https://github.com/ualberta-smr/PyMigBench/releases/v2.0.2) points to the exact dataset linked to the paper.
The data is also permanently archived in [figshare](https://doi.org/10.6084/m9.figshare.24216858.v2).
Use either of these links to reproduce the paper.

We may update this repository to correct any mistakes or add more data and it may not synch with the paper.
For, the latest data, use the [latest release](https://github.com/ualberta-smr/PyMigBench/releases/latest) in this repository.

## PyMigBench v1
The 2023 version of the dataset includes 375 migration-related code changes from 75 migrations between 34 analogous library pairs.
The data is also available in the [v1](/v1) directory.
Please visit [the PyMigBench website](https://ualberta-smr.github.io/PyMigBench) for detailed instructions on using PyMigBench v1.
We recommend using [PyMigBench v2](#pymigbench-v2) for any new research,
however, if you are going to use this version, please cite the [MSR 2023 paper](https://ieeexplore.ieee.org/abstract/document/10174111) as below.
[Release 1.0.3](https://github.com/ualberta-smr/PyMigBench/releases/v1.0.3) points to the dataset linked to the paper.
We recommend using PyMigBench v2 for any new research.
However, you want to use the v1 dataset, you should look at [Release 1.0.3](https://github.com/ualberta-smr/PyMigBench/releases/v1.0.3).
Cite the paper below if you use the v1 dataset.

```
@INPROCEEDINGS{pymigbench,
Expand Down
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
Loading

0 comments on commit 864f919

Please sign in to comment.