You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,15 +7,16 @@ Our sample of GitHub repositories and our dataset of mined patch scenarios is lo
7
7
The sample and dataset are compressed as zip archives that have to be unpacked before they can be used.
8
8
9
9
Our implementation of mpatch was written in Rust and can be found under [mpatch](mpatch). In its [README](mpatch/README.md), you can also find instructions on
10
-
how to generate the documentation for mpatch, which can also be found under [mpatch/doc](mpatch/doc/mpatch/index.html)
10
+
how to generate the documentation for mpatch.
11
11
12
12
The implementation of our evaluation setup can be found in the Java and Kotlin sources in the [src](src/main) folder.
13
13
The main file of the evaluation is [PatcherEvaluationMain.kt](src/main/kotlin/org/variantsync/evaluation/PatcherEvaluationMain.kt).
14
14
15
15
Our scripts for applying the various metrics to the different patchers and analyzing the statistics can be found under [src/main/python](src/main/python/result_analysis).
16
16
17
17
## Results without outliers
18
-
In our paper, we mention that we re-analyzed our results after excluding 0.05% of results that were outliers.
18
+
In our paper, we mention that we re-analyzed our results after excluding outliers.
19
+
Specifically, we removed the top 0.05% of results with the highest number of required fixes for each patcher; thus, treating patchers equally in this regard.
0 commit comments