You can mimic one the CI job defined in [.gitlab-ci.yml](https://gricad-gitlab.univ-grenoble-alpes.fr/verimag/reproducible-research/sasartifact/blob/master/.gitlab-ci.yml). For instance, if you want to do as in the `expe-dockver` job, you just need to run docker using the `jahierwan/verimag-sync-tools` image (which is available in the cloud) as follows:
@@ -59,7 +59,7 @@ If the last command has run without problem, you are inside a docker image where
You can thus proceed with the instructions below.
<aid="orga6ee562"></a>
<aid="orgb5fbc60"></a>
### Instructions to generate the data contained in Fig.1 of Section 2
...
...
@@ -72,23 +72,23 @@ cd async-unison
make rdbg4
```
You ought to be prompted to type <Enter> or "q" and then <Enter>. Choose the first proposal and press the <Enter> key; this creates a default session using commands defined in the Makefile by the rdbg4 rule.
You ought to be prompted to type `<Enter>` or `q` and then `<Enter>` Choose the first proposal and press the `<Enter>` key; this creates a default session using commands defined in [expe/async-unison/Makefile](https://gricad-gitlab.univ-grenoble-alpes.fr/verimag/reproducible-research/sasartifact/blob/master/expe/async-unison/Makefile) by the `rdbg4` rule.
You ought to see:
1. A pdf view of 4x4 grid with enabled nodes in green, and active ones in orange. This pdf corresponds to the configuration 1 of Fig1 in the article. The active nodes (among the enabled ones) are not necessarily the same as in the article as we did not set the seed of the pseudo-random generator.
2. the (rdbg) prompt in your terminal
2. the `(rdbg)` prompt in your terminal
At the (rdbg) prompt, type "sd" and <Enter>. This will make the simulation move 1 step forward, and update automatically the pdf view that shows up something equivalent to Configuration 2 in Fig1.
At the `(rdbg)` prompt, type `sd` and `<Enter>`. This will make the simulation move 1 step forward, and update automatically the pdf view that shows up something equivalent to Configuration 2 in Fig1.
At the (rdbg) prompt, type <Enter> to replay the last command (i.e., "sd"), and hence move to Configuration 3.
At the `(rdbg)` prompt, type `<Enter>` to replay the last command (i.e., `sd`), and hence move to Configuration 3.
Type <Enter> 3 more times to see Configurations 4, 5, and 6 of Fig.1.
Type `<Enter>` 3 more times to see Configurations 4, 5, and 6 of Fig.1.
Type "q" to exit.
Type `q` to exit.
<aid="org4984bb8"></a>
<aid="orgaf53d00"></a>
### Instructions to generate the data contained in Table 1 of Section 4
...
...
@@ -98,7 +98,7 @@ In order to run the experiments described in Section 4, type in a terminal, from
make expe
```
It launches the experiments on 2 small graphs (grid.dot and ER.dot). It should last a few minutes. Once the previous command returns, you can launch:
It launches the experiments on 2 small graphs (`grid.dot` and `ER.dot`). It should last a few minutes. Once the previous command returns, you can launch:
```sh
find .-name\*.log
...
...
@@ -110,7 +110,7 @@ to see the generated log files. Those files contain the memory usage and the exe
make save_result
```
a (sed) script will parse those .log files to generate a "summary.org" file and save generated files in a directory named "result". The summary.org file ought to contain a summary of all the experiments you have just performed. Table 1 was obtained out of it.
a (sed) script will parse those .log files to generate a `summary.org` file and save generated files in a directory named `result`. The summary.org file ought to contain a summary of all the experiments you have just performed. Table 1 was obtained out of it.
The correspondence between directory names and the Column 1 names is
...
...
@@ -130,7 +130,7 @@ make bigexpe
make save_result
```
Some remarks, comparing the results announced in the paper and the ones obtained in the VM:
Some remarks, comparing the results announced in the paper and the ones obtained on your machine:
- The number of seconds (time/step) may differ as the table was obtained using an other machine.
- 2 examples may run out of memory on your machine: the dfs algo on `hugeER.dot` and `biggrid.dot`. Indeed, as one can notice in Table 1, those examples require more memory (6.6 and 29 G) than your machine have.
