PERCOM 2022 will provide the opportunity for authors of accepted papers to participate in an Artifact Evaluation (AE) process. Authors who choose to participate can provide supplementary materials as artifacts (tools, applications, data sets, etc.) that will be reviewed solely for functional completeness (e.g., does provided code compile and run as expected; do experimental results match expected results, etc.). Participating authors will be allotted two additional pages in a separate Artifacts section of the proceedings to describe the nature and contents of the artifact package. Submission of artifacts packages will have no bearing on paper acceptance or publication. However, papers that have verified artifacts or data will be associated with badges in the conference program and proceedings. Two badges will be available: Artifact-Certified and Result-Certified. Upon submission, participating authors should indicate which badge(s) the committee should consider for the submission.
\nArtifacts of interest include (but are not limited to) the following:
\n\u2022 Software, including implementations or simulations of systems or algorithms.
\n\u2022 Data repositories, including, e.g., logging data, system traces, survey raw data.
\n\u2022 Frameworks, including tools and services illustrating new approaches to pervasive computing systems and application development.
\nThis list is not exhaustive; authors with questions about the suitability of an artifact should reach out to the chairs.<\/p>\n
The submission process is straightforward and follows the following steps: The review process will have three phases: Co-Chairs<\/strong><\/p>\n Reviewers<\/strong> For more important dates see here<\/a>.<\/p>\n For further information about the artifact submission and evaluation, please contact the Artifacts track chair, Janick Edinger (janick.edinger@uni-hamburg.de<\/a>)<\/p>\n","protected":false},"excerpt":{"rendered":" PERCOM 2022 will provide the opportunity for authors of accepted papers to participate in an Artifact Evaluation (AE) process. Authors who choose to participate can provide supplementary materials as artifacts (tools, applications, data sets, etc.) that will be reviewed solely for functional completeness (e.g., does provided code compile and run as expected; do experimental results […]<\/p>\n
\n\u2022 Package software and datasets<\/strong>.\u00a0Use a freely available tool, such as VirtualBox; Docker container image; git\/mercurial\/svn repositories; or zip\/tar files.
\n\u2022 Create an artifact guide<\/strong>.\u00a0The guide can be up to 2 pages and should be prepended to a preliminary version of the accepted paper (as a single PDF file). The guide\u2019s contents will vary based on the artifact but it should describe minimal software and hardware requirements, how to obtain and deploy the artifact, and what a reviewer should expect (e.g., the expected experimental results, or steps to navigate an application). The artifact guide should include a link to a publicly downloadable artifact, whatever that means for your particular submission.
\n\u2022 Submit the artifact guide via EDAS<\/strong>\u00a0at\u00a0https:\/\/edas.info\/newPaper.php?c=28747<\/a>
\n\u2022 Commit to maintaining the artifact for at least three years<\/strong>.\u00a0As part of the submission process, the authors will be asked to certify that they will maintain the artifact as described in the two-page description at the publicly accessible location indicated in the description for at least three years past the date of the conference (i.e., through March 2024).<\/p>\n<\/h4>\n
\nThe Review Process<\/strong><\/h4>\n
\n\u2022 Initial Review<\/strong>.\u00a0The reviewers will follow the instructions given in the artifact\u2019s guide to ensure that artifacts can be deployed and run as described. Any bugs or questions will be documented as feedback.
\n\u2022 Artifact Revision<\/strong>.\u00a0During the second phase, authors will be able to correct any bugs in their artifacts\/guides to make sure reviewers can un-package and run the artifact before the deeper evaluation.
\n\u2022 Final evaluation<\/strong>.\u00a0Reviewers perform their final evaluation to ensure that each artifact runs as expected and\/or contains the expected data.
\nNote that the first two phases may be intertwined (several rounds) if authors and reviewers are quick their communication; every submission is guaranteed at least one opportunity for revision.
\nBest Artifact Award
\nA PERCOM 2022 Best Artifact Award will be presented during the conference.<\/p>\n\nArtifact Review Committee<\/strong><\/h4>\n
\n
\nTBA<\/p>\nImportant Dates<\/strong><\/h4>\n
\n