diff options
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 ------------------------------ |