USENIX Security '22 Winter Artifact Evaluation

Thank you for submitting an artifact!

Please find some additional information on the USENIX Security '22 Call for Artifacts and the Artifact Appendix Guidelines.

Your artifact package must include an obvious "README" that describes your artifact and provides a road map for evaluation (if you are requesting an Artifact Functional or Results Reproduced badge). The README should contain or point to suitable instructions and documentation, to save committee members the burden of reverse-engineering the authors' intentions. (A tool without a quick tutorial is generally very difficult to use. Similarly, a dataset is useless without some explanation on how to browse the data.) For software artifacts, the README should—at a minimum—provide instructions for installing and running the software on relevant inputs. For other types of artifacts, describe your artifact and detail how to "use" it in a meaningful way.

Here are a few additional resources to prepare your artifact for evaluation:

• HOWTO for AEC Submitters, by Dan Barowy, Charlie Curtsinger, Emma Tosch, John Vilk, and Emery Berger.
• Artifact Evaluation: Tips for Authors, by Rohan Padhye.
• How Are Award-winning Systems Research Artifacts Prepared (Part 1), by Tianyin Xu.