diff options
| author | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-12-02 15:41:29 +0000 |
|---|---|---|
| committer | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-12-02 15:41:29 +0000 |
| commit | e9dfc5bf433fbf61b97179e3243a20e06a4b01dc (patch) | |
| tree | baf31e6434965c841a8f4f47b974d99f1311ea06 /peer-review | |
| parent | 0f3d6ab47f96ef14cd197f2ff3228338b57c937a (diff) | |
Minor edits in newly added parts on statistical verification
Thanks a lot Boud for adding that script in your own project and linking it
here. Since the raw file (without context of the whole project) is very
hard to understand for the users, I switched the URL to the navigable URL
the link is actually on the filename. It will always show the most recent
version of this script, not the particular snapshot of now. But infact that
is better, since we can make it better and improve it over time. Maybe even
by the end of this paper's referee review will be able to include it in
Maneage's core branch.
I also removed the link to this discussion at the first paragraph of
Section IV (proof of concept). Since that is just the introduction, and
going into this level of detail there could be confusing for the
readers. Having the name of the script in the proper place is more direct
and understandable for the readers.
Thanks again Boud for the nice work on this ;-).
Diffstat (limited to 'peer-review')
| -rw-r--r-- | peer-review/1-answer.txt | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/peer-review/1-answer.txt b/peer-review/1-answer.txt index 76c574e..ae28c5f 100644 --- a/peer-review/1-answer.txt +++ b/peer-review/1-answer.txt @@ -703,15 +703,15 @@ discussed in Section IV, in the part on verification ("Where exact reproducibility is not possible (for example due to parallelization), values can be verified by a statistical method specified by the project authors."). We have linked keywords in the latter sentence to a Software -Heritage URI [swh] with the specific file in the Peper and Roukema -Maneage'd paper that illustrates an example of how statistical -verification of parallelised code can work in practice. +Heritage URI [1] with the specific file in a Maneage'd paper that +illustrates an example of how statistical verification of parallelised code +can work in practice (Peper & Roukema 2020; zenodo.4062460). We would be interested to hear if any other papers already exist that use -automatic statistical verification of parallelised code as has been done -in this Maneage'd paper. +automatic statistical verification of parallelised code as has been done in +this Maneage'd paper. -[swh] https://archive.softwareheritage.org/swh:1:cnt:4217e24e4a474ba43a4d30abfb0a42b823ef4640 +[1] https://archive.softwareheritage.org/browse/origin/content/?branch=refs/heads/postreferee_corrections&origin_url=https://codeberg.org/boud/elaphrocentre.git&path=reproduce/analysis/bash/verify-parameter-statistically.sh ------------------------------ |