diff options
author | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-06-30 03:39:36 +0100 |
---|---|---|
committer | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-06-30 03:39:36 +0100 |
commit | fb7154a9c0595f616036b0cea4c1d1dd38863496 (patch) | |
tree | 381c903113c16e7dbd72f1f1f580cae80acabe2e /reproduce | |
parent | 991f4c25729ac2526f30abf3d68111dd820fbfed (diff) |
Implemented comments by Mervyn O'Luing
Mervyn had read the paper and provided some interesting thoughts that I
tried to implement. Mervyn's comments are shown below. I just haven't
addressed the last point yet, because I am affraid it may make the text too
long (we are already on the boundary of the word-limit). We have already
discussed that it is a good research topic, and have hopefully triggered
the curiosity of the readers to test it ;-).
-------------------
Page 2: Regarding Criterion 1: Completeness. A project must be self
contained? So this includes not requiring root or administrator
privileges. This suggests that the project is only made open after the
development has been completed?
Regarding Criterion 5: 'a clerk can do it' -- in the pc world that we live
in could this be taken as a disparaging comment?
Page 5: 'The C library is linked with all programs, and this dependence can
hypothetically hinder exact reproducibility of results, but we have not
encountered this so far.' - what do you think might happen if this does
affect reproducibility? Do you have a plan to deal with this? Or are you
going to wait until you hear of such cases as the number will probably be
small? Have you done probability analysis to show that the rates are likely
to be very small? Or should you have a disclaimer with maneage?
Diffstat (limited to 'reproduce')
0 files changed, 0 insertions, 0 deletions