Sponsored by USENIX, the Advanced Computing Systems Association.
Submit an Artifact
After your paper has been (conditionally) accepted, please check the Artifact Submission Guidelines. The submission system will be available soon. The following dates apply for three deadlines:
Summer Quarter Deadline
- Notification for paper authors of summer quarter: Friday, September 11, 2020
- Artifact submission deadline: Wednesday, September 16, 2020 (AoE)
- Answering AE reviewer questions: September 21–October 2, 2020
- Artifact decisions announced: Thursday, October 8, 2020
- USENIX Security final papers deadline: Tuesday, October 13, 2020
Fall Quarter Deadline
- Notification for paper authors of fall quarter: Thursday, January 21, 2021
- Artifact submission deadline: Tuesday, January 26, 2021 (AoE)
- Answering AE reviewer questions: February 1–February 12, 2021
- Artifact decisions announced: Wednesday, February 17, 2021
- USENIX Security final papers deadline: Monday, February 22, 2021
Winter Quarter Deadline
- Notification for paper authors of winter quarter: Friday, April 30, 2021
- Artifact submission deadline: Wednesday, May 5, 2021 (AoE)
- Answering AE reviewer questions: May 10–May 21, 2021
- Artifact decisions announced: Thursday, May 27, 2021
- USENIX Security final papers deadline: Wednesday, June 2, 2021
The artifact evaluation process will take about two weeks. Please make sure that at least one of the authors is reachable to answer questions in a timely manner. Given the camera-ready deadline, we have unfortunately only a short amount of time to perform the actual AEC process, but we expect that this time is enough to evaluate artifacts in a reasonable way.
Artifact Evaluation Committee Co-Chairs
Thorsten Holz, Ruhr-Universität Bochum
Clémentine Maurice, IRISA
Artifact Evaluation Committee
Artifact Submission Guidelines
Step 1. Registration
By the registration deadline, please submit the abstract and PDF of your accepted USENIX Security 2021 paper, as well as topics, conflicts, and any "optional bidding instructions" for the potential reviewers.
Step 2. Package and Submit Artifact
By the artifact finalization deadline, please provide a stable URL or (if that is not possible) upload an archive of your artifact. You will no longer be able to change these after the artifact finalization deadline. For your artifact to be considered you also need to check the "ready for review" box before the finalization deadline.
We recommend creating a single web page at a stable URL that contains the artifact and instructions for installing and using the artifact (in case of software or special hardware). For other types of artifacts, please make sure that they can be evaluated in a meaningful way, please describe your artifact in detail to simplify this process. If something is unclear, you will be contacted to clarify any questions regarding your artifact. Feel free to reach out in advance in case something is unclear.
The artifact evaluation committee will read your accepted paper before evaluating the artifact. But it is quite likely that the artifact needs more documentation to use. In particular, please make concrete what claims you are making of the artifact, especially if these differ from the expectations set up by the paper. This is a place where you can tell us about difficulties we might encounter in using the artifact, or its maturity relative to the content of the paper. We are still going to evaluate the artifact relative to the paper, but this helps set expectations upfront, especially in cases that might frustrate the reviewers without prior notice.
Artifact authors not anonymous
The artifact submissions are not anonymous. The reviewers will see the authors for each artifact from the start. So please do not waste your time trying to hide the artifact authors.
We ask that, during the evaluation period, you do not embed any analytics or other tracking in the Web site for the artifact or, if you cannot control this, that you do not access this data. This is important for maintaining the confidentiality of reviewers. If for some reason you cannot comply with this, please notify the chairs immediately such that we can discuss options.
Authors should consider one of the following methods to package the software components of their artifacts (though the AEC is open to other reasonable formats as well):
- Source code: If your artifact has very few dependencies and can be installed easily on several operating systems, you may submit source code and build scripts. However, if your artifact has a long list of dependencies, please use one of the other formats below.
- Virtual machine/container: A virtual machine or Docker image containing software application already setup with the right tool-chain and intended runtime environment. For example:
- For raw data, the VM would contain the data and the scripts used to analyze it.
- For a mobile phone application, the VM would have a phone emulator installed.
- For mechanized proofs, the VM would have the right version of the theorem prover used.
- We recommend using VirtualBox or Docker, since both are freely available on several platforms. An Amazon EC2 instance is also possible.
- Binary Installer: Please indicate exactly which platform and other runtime dependencies your artifact requires.
- Live instance on the Web: Ensure that it is available for the duration of the artifact evaluation process.
- Hardware: In case your artifact requires special hardware (e.g., SGX or another type of trusted execution environment) or your artifact is actually a piece of hardware, please make sure that the reviewers can somehow access the device. Some kind of VPN/SSH access to the device might be an option, but due to anonymity we would need to discuss options - please contact the chairs in advance.
- Screencast: A detailed screencast of the tool along with the results, especially if one of the following special cases applies:
- The artifact needs proprietary/commercial software or proprietary data that is not easily available or cannot be distributed to the committee.
- The artifact requires significant computation resources (e.g., more than 24 hours of execution time to produce the results) or requires huge data sets.
- The artifact requires specific hard- or software that is not generally available in a typical lab and where no access can be provided in a reasonable way.
Remember that the AEC is attempting to determine whether the artifact meets the expectations set by the paper. If possible, package your artifact to help the committee easily evaluate this. This can for example be achieved via automated test cases that reproduce the experiments described in the paper or a step-by-step documentation to help setting up the artifact.
If you have any questions about how best to package your artifact, please do not hesitate to contact the AEC chairs, at firstname.lastname@example.org.