Skip to content

Commit 47d13f8

Browse files
committed
results/splc23-views/INSTALL.md minor improvements
1 parent aaf7ad5 commit 47d13f8

File tree

1 file changed

+8
-9
lines changed

1 file changed

+8
-9
lines changed

replication/splc23-views/INSTALL.md

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ To execute the replication you can run the `execute` script corresponding to you
7070
> `./stop-execution.sh`
7171
7272
You might see warnings or errors reported from SLF4J like `Failed to load class "org.slf4j.impl.StaticLoggerBinder"` which you can safely ignore.
73-
Further troubleshooting advice can be found at the bottom of this file.
73+
Further **troubleshooting advice** can be found at the bottom of this file.
7474

7575
The results of the verification will be stored in the [results](results) directory.
7676

@@ -90,19 +90,18 @@ The files are:
9090
- `<first commit hash>.committimes.txt`: Contains the time in milliseconds each commit in the batch required to be analysed.
9191
- `<first commit hash>.views.csv`: contains information on each generated view. This file contains the main results of our feasibility study.
9292

93-
Additionally, each repository directory also contains a `totalresult.metadata.txt` that is an aggregation of the `*.metadata.txt` files of each batch.
93+
Additionally, each repository directory also contains a `totalresult.metadata.txt`, which is an aggregation of the `*.metadata.txt` files of each batch.
9494

9595
#### results/views/current_plots
9696

97-
The directory `results/views/current_plots` contains plots, latex tables, and aggregated results that we used to report
98-
our results in the paper. The directory should contain the following files:
97+
The directory `results/views/current_plots` contains plots, latex tables, and aggregated results that we used to report results in the paper. The directory should contain the following files:
9998
- `count.csv`: Lists how many views of each view type were generated.
100-
- `hist.tex`: A latex table that reports the runtimes of the view-smart and view-naive algorithm. Table 1 in our paper is a slightly adapted variant of `hist.tex`.
101-
- `median.tex`: A latex table that repots the median runtime for each view type per algorithm.
99+
- `hist.tex`: A latex table that reports the runtimes of the $view_{smart}$ and $view_{naive}$ algorithm. Table 1 in our paper is a slightly adapted variant of `hist.tex`.
100+
- `median.tex`: A latex table that reports the median runtime for each view type per algorithm.
102101
- `merged.csv`: An aggregation of all `*.views.csv` of all batches of all repositories within the `results/views/current` directory. This file thus lists the result data for each view we generated during the entire feasibility study.
103-
- `rank.csv`: Lists the slowest view generations with the naive algorithm. This table allows us to inspect how the view-smart algorithm performs on the worst case candidates of the view-naive algorithm.
104-
- `rel_speedup1sOrMore.csv`: Shows the relative speedups with the optimized algorithm view-smart relative to the naive algorithm view-naive for all views that required 1s or longer to generate with view-naive.
105-
- `wilcoxon.csv`: Results of the Wilcoxon Signed-Rank Test for determining whether there is a statistically significant improvement in runtimes with the optimized algorithm view-smart.
102+
- `rank.csv`: Lists the slowest view generations with the naive algorithm. This table allows us to inspect how the $view_{smart}$ algorithm performs on the worst case candidates of the $view_{naive}$ algorithm.
103+
- `rel_speedup1sOrMore.csv`: Shows the relative speedups with the optimized algorithm $view_{smart}$ relative to the naive algorithm $view_{naive}$ for all views that required 1s or longer to generate with $view_{naive}$.
104+
- `wilcoxon.csv`: Results of the Wilcoxon Signed-Rank Test for determining whether there is a statistically significant improvement in runtimes with the optimized algorithm $view_{smart}$.
106105

107106
### (Optional) Running the Feasibility Study on Custom Datasets
108107
You can also run the feasibility study on other datasets by providing the path to the dataset file as first argument to the execution script:

0 commit comments

Comments
 (0)