Artifact Evaluation for Computer Systems' Research
We work with the community and ACM to improve methodology and tools for reproducible experimentation, artifact submission / reviewing and open challenges!
Home Artifacts Joint Committee Submission Guide Reviewing Guide FAQ Prior AE

Frequently Asked Questions

This page continuously evolves and can be modified directly at GitHub!

Do I have to open source my software artifacts?

No, it is not strictly necessary and you can provide your software artifact as a binary. However, in case of problems, reviewers will not be able to fix it and will likely give you a negative score.

Is Artifact evaluation blind or double-blind?

AE is a single-blind process, i.e. authors' names are known to the evaluators (there is no need to hide them since papers are accepted), but names of evaluators are not known to the authors. AE chair is usually used as a proxy between the authors and the evaluators in case of questions and problems.

How to pack artifacts?

We do not have strict requirements at this stage. You can pack your artifacts simply in a tar ball, zip file, Virtual Machine or Docker image. You can also share artifacts via public services including GitHub, GitLab and BitBucket. Please see our submission guide for more details.

Is it possible to provide a remote access to a machine with pre-installed artifacts?

Only in exceptional cases, i.e. when rare hardware or proprietary software is required, or VM image is too large, or when you are not authorized to move artifacts outside your organization. In such case, you will need to send an access information to the AE chairs via private email or SMS. They will then pass this information to the evaluators.

Can I share commercial benchmarks or software with evaluators?

Please check the license of your benchmarks, data sets and software. In case of any doubts, try to find a free alternative. In fact, we strongly suggest you to provide a small subset of free benchmarks and data sets to simplify evaluation. Note, that we have a preliminary agreement with the EEMBC consortium to let authors share their EEMBC benchmarks with the evaluators for Artifact Evaluation purposes.

Can I engage with the community to evaluate my artifacts?

Based on the community feedback, we provided an extra option of open evaluations to let the community validate artifacts which are publicly available at GitHub, GitLab, BitBuckets, etc, report issues and help the authors fix them. Note, that at the end, these artifacts still go through traditional evaluation process via AE committee. We successfully validated at ADAPT'16 and CGO/PPoPP'17 AE!

How to automate and customize experiments?

For our past AE experience, the major difficulty for evaluators is that nearly every artifact pack has its own ad-hoc scripts and formats (see our last AE CGO-PPoPP'17 presentation). Things get even worse, if someone would like to validate experiments using latest software environment and hardware (rather than quickly outdated VM and Docker images). Most of the submitted scripts are not easy to change, customize or port, particularly when an evaluator would like to try other compilers, libraries and data sets.

Therefore, we strongly suggest to use portable workflow frameworks with unified JSON API such as Collective Knowledge (CK) to reduce evaluators' burden. It helps automate and unify your experiments, plug in different compilers, benchmarks, data sets, tools, predictive models to your workflows, and unify aggregation and visualization of results. Please, check out this CGO'17 article from the University of Cambridge ("Software Prefetching for Indirect Memory Accesses") with CK-based experimental workflow which won distinguished artifact award:

We now provide free (voluntarily) service to help authors convert their artifacts and ad-hoc scripts to unified and customizable workflows. Contact AE committee for more details.

Do I have to make my artifacts public if they pass evaluation?

No, you don't have to (it may be impossible in some cases of commercial artifacts). Nevertheless, we encourage you to make your artifacts publicly available upon publication (for example, by including them as "source materials" in the Digital Library) as a part of our vision for collaborative and reproducible computer engineering.

Furthermore, if you have your artifacts already publicly available at the time of submission, you may profit from the "public review" option, where you are engaged directly with the community to discuss, evaluate and use your software. See such examples here (search for "example of public evaluation").

How to report and compare empirical results?

First of all, you should undoubtedly run empirical experiments more than once (we still encounter many cases where researchers measure execution time only once)! There is no universal recipe how many times you should repeat your empirical experiment since it heavily depends on the type of your experiments, machine and environment. You should then analyze distribution of execution time as shown in the figure below:

If you have more than one expected value (b), it means that you have several run-time states on your machine which may be switching during your experiments (such as adaptive frequency scaling) and you can not reliably compare empirical results. However, if there is only one expected value for a given experiment (a), then you can use it to compare multiple experiments (for example during autotuning as described here).

You should also report variation of empirical results together with expected values. Furthermore, we strongly suggest you to pre-record results from your platform and provide a script to automatically compare new results with the pre-recorded ones preferably using expected values. This will help evaluators avoid wasting time when trying to dig out and validate results in stdout. For example, see how new results are visualized and compared against the pre-recorded ones using CK dashboard in the CGO'17 distinguished artifact.

How to deal with numerical accuracy and instability?

If the accuracy of your results depends on a given machine, environment and optimizations (for example, when optimizing BLAS, DNN, etc), you should provide a script/plugin to automatically report unexpected loss in accuracy (above provided threshold) as well as any numerical instability.

How to validate models or algorithm scalability?

If you present a novel parallel algorithm or some predictive model which should scale across a number of cores/processors/nodes, we suggest you to provide such an experimental workflow which could automatically detect the underlying topology of a user machine (or it can at least be configurable), validate your models or algorithm scalability, and report any unexpected behavior. In the future, we expect to use public repositories of knowledge where results will be automatically validated against the ones continuously shared by the community (1, 2).

Is there any page limit for my Artifact Evaluation Appendix?

There is no limit for the AE Appendix at the time of the submission for Artifact Evaluation.

There is a 2 page limit for the AE Appendix in the camera-ready CGO,PPoPP and PACT paper. There is no page limit for the AE Appendix in the camera-ready SC paper. We also expect that there will be no page limits for AE Appendices in the journals willing to participate in our AE initiative.

Maintained by
cTuning foundation (non-profit R&D organization)
and volunteers!
          
Powered by Collective Knowledge
                     
  
  
  
           Locations of visitors to this page