Commit d7c9395d authored by Thom Badings's avatar Thom Badings
Browse files

Update README.md

parent 4b37454a
......@@ -69,15 +69,15 @@ The results for individual experiments are saved in the `data/` folder. Dependin
## 4. How to run experiments?
The and tables in the experimental section of [1] can be reproduced by running the shell script `run_experiments.sh` in the `opt/upmdps/` folder. To speed up run times, consider to reduce the numbers of parameter samples or the number of iteration (note that the `data/` folder is shared with the host machine if you run the container with the command above). We also included a benchmark set with such reduced numbers in `run_experiments_fast.sh`.
The and tables in the experimental section of [1] can be reproduced by running the shell script `run_experiments.sh` in the `opt/upmdps/` folder. To speed up run times, consider to reduce the numbers of parameter samples or the number of iteration (note that the `data/` folder is shared with the host machine if you run the container with the command above). We also included a benchmark set with such reduced numbers in `run_experiments_fast.sh` (note that results of these experiments will be different than in the paper, due to these reduced sample sizes and iterations).
All results are stored in the `data/` folder, and the tables in [1] can be replicated as follows:
Table 1 can be replicated by putting the CSV output files from running the drone experiment that end with `_satprob.csv`. Note that three of such CSV files are created, for the different wind conditions in the experiment. Every of each files represents a row in Table 1.
- Table 1 can be replicated by putting the CSV output files from running the drone experiment that end with `_satprob.csv`. Note that three of such CSV files are created, for the different wind conditions in the experiment. Every of each files represents a row in Table 1.
Table 3 can be replicated by collecting all CSV output files that end with `_confprob.csv` (except for the drone results, which are presented in Table 1). For every benchmark instance, such a file is created, which represents one row in Table 3.
- Table 3 can be replicated by collecting all CSV output files that end with `_confprob.csv` (except for the drone results, which are presented in Table 1). For every benchmark instance, such a file is created, which represents one row in Table 3.
Table 4 can be replicated by collecting all CSV output files that end with `_satprob.csv` (except for the drone results, which are presented in Table 1). For every benchmark instance, such a file is created. Table 4 can be produced by putting together the rows from the CSV files for the correct number of values (N).
- Table 4 can be replicated by collecting all CSV output files that end with `_satprob.csv` (except for the drone results, which are presented in Table 1). For every benchmark instance, such a file is created. Table 4 can be produced by putting together the rows from the CSV files for the correct number of values (N).
## 5. List of possible arguments
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment