{"id":131,"date":"2020-06-22T22:03:15","date_gmt":"2020-06-22T22:03:15","guid":{"rendered":"https:\/\/new.isfpga.org\/?page_id=131"},"modified":"2021-07-08T18:28:35","modified_gmt":"2021-07-08T18:28:35","slug":"artifact-evaluation","status":"publish","type":"page","link":"https:\/\/wp.isfpga.org.dream.website\/artifact-evaluation\/","title":{"rendered":"Artifact Evaluation"},"content":{"rendered":"\n

If you have questions, you can email: artifactevaluationchair@isfpga.org<\/a><\/p>\n\n\n\n

The goal of this initiative is to promote reproducibility of published results by highlighting papers supported with open-source code. These papers are identified by badges promoted by ACM. More details are provided below.<\/p>\n\n\n\n

We are asking all authors to indicate whether or not there are artifacts associated with their paper(s). Artifacts are not required and the artifact evaluation process is separate to the double-blind paper peer review process.<\/p>\n\n\n\n


Artifact Form Requirements<\/h2>\n\n\n\n


Is the Artifact Form required in order to submit to FPGA?<\/em><\/h3>\n\n\n\n

As an author, you must answer the question whether or not you have artifacts when you submit your paper. If not, answering no is sufficient. Artifacts are not required. If you do have artifacts to evaluate, you should answer Yes. You will have to submit the separate Artifact Form by the rebuttal deadline.<\/p>\n\n\n\n


What is the Artifact Form?<\/em><\/h3>\n\n\n\n

The Artifact Form is the information you must fill out to enable artifact evaluation for your submission and is only required if you answered Yes to artifact evaluation at the time of paper submission. The form describes the presence or absence of computational artifacts (software, hardware or data) that supports the research presented in the paper. You must submit this form by the Rebuttal Deadline if you would like your artifacts to be evaluated.<\/p>\n\n\n\n


Do I need to make my software open source in order to complete the Artifact Form?<\/em><\/h3>\n\n\n\n

No. You are not asked to make any changes to your computing environment or design process in order to complete the form. The form is meant to describe the computing environment in which you produced your results and any artifacts you wish to share. Any author-created software does not need to be open source, unless you wish to be eligible for an ACM Artifacts Available badge (see below).
<\/p>\n\n\n\n


Review Process<\/h2>\n\n\n\n


Who will review my artifact form?<\/em><\/h3>\n\n\n\n

If your submitted paper is accepted to FPGA 2022, then the Artifact form will be reviewed by the Artifact Evaluation Chairs. The Artifact Evaluation Committee (AEC) will review the information provided, and will check that artifacts are indeed available at the URLs provided. They will also help authors improve their forms, in a double-open arrangement. If authors select this option, their paper may be evaluated for the Artifacts Available \u2013 Reusable or Artifacts Available \u2013 Functional badges. Some papers will be evaluated for the ACM \u201cResults Replicated\u201d badge. If your paper is chosen, then the artifact evaluation committee will be in contact with the authors if they have questions regarding your artifacts.
<\/p>\n\n\n\n


How will review of artifacts interact with the double-blind review process?<\/em><\/h3>\n\n\n\n

Artifact review will not take place until after decisions on papers have been made. Reviewers will not have access to the artifact form. Authors should not include links to their repositories in their paper. The paper review process is double blind. The artifact review process is not.
<\/p>\n\n\n\n


Impact of Artifact Evaluation (AE)<\/h2>\n\n\n\n


What\u2019s the impact of an Artifact Form on scientific reproducibility?<\/em><\/h3>\n\n\n\n

An artifact-evaluation effort can increase the trustworthiness of computational results. It can be particularly effective in the case of results obtained using specialized computing platforms, not available to other researchers. Leadership computing platforms, novel testbeds, and experimental computing environments are of keen interest to the FPGA community. Access to these systems is typically limited, however. Thus, most reviewers cannot independently check results, and the authors themselves may be unable to recompute their own results in the future, given the impact of irreversible changes in the environment (compilers, libraries, components, etc.). The various forms of Artifact Evaluation improve confidence that computational results from these special platforms are correct.<\/p>\n\n\n\n


The paper text explains why I believe my answers are right and shows all my work. Why do I need an Artifact Evaluation?<\/strong><\/em><\/h3>\n\n\n\n

There are many good reasons for formalizing the artifact description and evaluation process. Standard practice varies across disciplines. Labelling the evaluation as such improves our ability to review the paper and improves reader confidence in the veracity of the results.
<\/p>\n\n\n\n


Artifacts<\/h2>\n\n\n\n


What are \u201cauthor-created\u201d artifacts and why make the distinction?<\/em><\/h3>\n\n\n\n

Author created artifacts are the hardware, software, or data created by the paper\u2019s authors. Only these artifacts need be made available to facilitate evaluation. Proprietary, closed source artifacts (e.g. commercial software and CPUs) will necessarily be part of many research studies. These proprietary artifacts should be described to the best of the author\u2019s ability but do not need to be provided.
<\/p>\n\n\n\n


What about proprietary author-created artifacts?<\/em><\/h3>\n\n\n\n

The ideal case for reproducibility is to have all author-created artifacts be publicly available with a stable identifier. Papers involving proprietary, closed source author-created artifacts should indicate the availability of the artifacts and describe them as much as possible. Note that results dependent on closed source artifacts are not reproducible and are therefore ineligible for some of the ACM\u2019s artifact review badges. See https:\/\/www.acm.org\/publications\/policies\/artifact-review-badging.
<\/p>\n\n\n\n


Are the numbers used to draw our charts a data artifact?<\/em><\/h3>\n\n\n\n

Not necessarily. Data artifacts are the data (input or output) required to reproduce the results, not necessarily the results themselves. For example, if your paper presents a system that generates charts from datasets then providing an input dataset would facilitate reproducibility. However, if the paper merely uses charts to elucidate results then the input data to whatever tool you used to draw those charts isn\u2019t required to reproduce the paper\u2019s results. The tool which drew the chart isn\u2019t part of the study, so the input data to that tool is not a data artifact of this work.
<\/p>\n\n\n\n


Help! My data is HUGE! How do I make it publicly available with a stable identifier?<\/em><\/h3>\n\n\n\n

Use Zenodo (https:\/\/help.zenodo.org\/). Contact them for information on how to upload extremely large datasets. You can easily upload datasets of 50GB or less, have multiple datasets, and there is no size limit on communities.
<\/p>\n\n\n\n


ACM Artifacts Available and Artifacts Evaluated Badges<\/h2>\n\n\n\n

For more information, see https:\/\/www.acm.org\/publications\/policies\/artifact-review-badging<\/a><\/p>\n\n\n\n

The badges we will consider for FPGA 2022 are Artifacts Available, Artifacts Evaluated \u2014 Functional, Artifacts Evaluated \u2014 Reusable, and Results Validated.<\/p>\n\n\n\n

By the ACM Badging definitions:<\/p>\n\n\n\n


Artifacts Available:<\/strong>
This badge is applied to papers in which associated artifacts have been made permanently available for retrieval.<\/p>\n\n\n\n

The Artifact form will be used to determine eligibility for an ACM Artifacts Available badge on the basis of the answers to questions about the availability of author-created software, hardware or data products. The conditions of eligibility are:<\/p>\n\n\n\n

All author-created software artifacts are maintained in a public repository under an OSI-approved license.<\/p>\n\n\n\n

All author-created hardware artifacts are available and comply with the Open Source Hardware Definition.<\/p>\n\n\n\n

All author-created data artifacts are maintained in a public repository with a stable identifier, such as a DOI.<\/p>\n\n\n\n


Artifacts Evaluated \u2014 Functional:<\/strong>
The artifacts associated with the research are found to be documented, consistent, complete, exercisable, and include appropriate evidence of verification and validation.<\/p>\n\n\n\n


Artifacts Evaluated \u2014 Reusable:<\/strong>
The artifacts associated with the paper are of a quality that significantly exceeds minimal functionality. That is, they have all the qualities of the Artifacts Evaluated \u2013 Functional level, but, in addition, they are carefully documented and well-structured to the extent that reuse and repurposing is facilitated. In particular, norms and standards of the research community for artifacts of this type are strictly adhered to.<\/p>\n\n\n\n


Results Replicated:<\/strong>
The main results of the paper have been obtained in a subsequent study by a person or team other than the authors, using, in part, artifacts provided by the author.<\/p>\n\n\n\n

Exact replication or reproduction of results is not required, or even expected. Instead, the results must be in agreement to within a tolerance deemed acceptable for experiments of the given type. In particular, differences in the results should not change the main claims made in the paper. <\/p>\n\n\n\n

It is easy to see how research articles that develop algorithms or software systems could be labeled as described above. Here, the artifacts could be implementations of algorithms or complete software systems, and replication would involve exercise of software, typically software provided by the author. However, we intend these badges to be applicable to other types of research as well. For example, artifacts associated with human-subject studies of novel human-computer interface modalities might be the collected data, as well as the scripts developed to analyze the data. \u201cReplication\u201d might focus on a careful inspection of the experimental protocol along with independent analysis of the collected data.<\/p>\n\n\n\n


Notes about artifacts:<\/strong>
A design artifact can be a hardware or software design. Software could include design tools or host code. Hardware designs can include designs intended to become ASICs, or designs that map to FPGA fabric.<\/p>\n\n\n\n

Hardware artifacts should comply with the Open Source Hardware Definition. See https:\/\/www.oshwa.org\/definition\/<\/p>\n\n\n\n


FAQ:
<\/h2>\n\n\n\n

Q: In the past I have included a link to my code in the paper, and kept the code anonymous. Can I still do this?<\/em><\/h4>\n\n\n\n

A: Yes you can still do this. However, if you do so you will not be eligible for any of the Artifact Evaluation process. Be sure that any information included in the submission is blind. No author information should be included. The Artifact Evaluation process is not blind and must include author information so that the AE committee can contact the authors with questions.
<\/p>\n\n\n\n

Q: I only want to make my artifacts public if the paper is accepted. Is that okay?<\/em><\/h4>\n\n\n\n

A: Yes. Artifacts will only be examined after papers are accepted. You can wait until you hear the decision on your paper before making your artifacts public, but you must complete the form by the deadline set; information in the form will not be used until after paper acceptance.

<\/p>\n\n\n\n

Q: Does the artifact submission link need to be anonymous?<\/em><\/h4>\n\n\n\n

Any information in the paper must be anonymous. In the artifact descriptor form the link should not be anonymous. The artifact descriptor form will not be reviewed until after paper decisions are made.
<\/p>\n\n\n\n

Q: What is the deadline for submission of artifacts?<\/em><\/h4>\n\n\n\n

No one will look at artifacts until your paper is accepted. We require the information available to start the evaluation process as soon as papers are accepted, hence the requirement to submit the form by the rebuttal deadline.
<\/p>\n\n\n\n

Q: Can I update the artifact evaluation form after paper acceptance?<\/em><\/h4>\n\n\n\n

You are free to make changes to details of the artifacts up to the start of the evaluation and in consultation with your evaluator, but the initial submission should include as many details as possible to allow the evaluation process to be organized.<\/p>\n","protected":false},"excerpt":{"rendered":"

If you have questions, you can email: artifactevaluationchair@isfpga.org The goal of this initiative is to promote reproducibility of published results by highlighting papers supported with open-source code. These papers are identified by badges promoted by ACM. More details are provided below. We are asking all authors to indicate whether or not there are artifacts associated […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/wp.isfpga.org.dream.website\/wp-json\/wp\/v2\/pages\/131"}],"collection":[{"href":"https:\/\/wp.isfpga.org.dream.website\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/wp.isfpga.org.dream.website\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/wp.isfpga.org.dream.website\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wp.isfpga.org.dream.website\/wp-json\/wp\/v2\/comments?post=131"}],"version-history":[{"count":7,"href":"https:\/\/wp.isfpga.org.dream.website\/wp-json\/wp\/v2\/pages\/131\/revisions"}],"predecessor-version":[{"id":533,"href":"https:\/\/wp.isfpga.org.dream.website\/wp-json\/wp\/v2\/pages\/131\/revisions\/533"}],"wp:attachment":[{"href":"https:\/\/wp.isfpga.org.dream.website\/wp-json\/wp\/v2\/media?parent=131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}