In this Section: Overview & Updates | Topics of Interest | Paper Submission | Figures | Open Science Badges | Industry & Demo Sessions

ISSCC 2027 Open Science Badges: Author Guidelines

New for ISSCC 2027. Open Science Badges are voluntary marks of recognition for authors who share the artifacts behind their paper. They increase your paper’s visibility and impact, help build trust in your design and results, and let others build on your work. Participation is optional. The repository link is hidden during blind review.

The two badges

Badge

Open Design

Open Data

What you share

Design source files of the architecture described in the paper, such as synthesizable RTL, netlists, or an executable/behavioral model.
Measurement data (raw or processed) and, where applicable, test scripts, bench configurations, or channel models behind your key performance claims.

A paper may earn one or both badges. You choose the granularity, polish, and license of what you share.

 

Repository content required

Since this is the first year that we roll out this initiative, the minimal required repository content to receive a badge is deliberately kept low. At a minimum, you should share the artifacts behind your key results, described on their own terms so a reader can understand them. Also partial sharing is fine, as long as it covers relevant aspects of your paper and key results.

  • Open Data: the actual data points behind at least your key result(s), in a usable text format (CSV, Excel, or plain text), not a screenshot or image of the plot. Include a short README describing what the data is and its units. You do not need to reference the paper or its figure numbers in the repository. An analysis/plotting script, a description of the measurement setup, and/or benchmarking assumptions are encouraged.

  • Open Design: design source of the architecture behind a key result, such as synthesizable RTL, a netlist, and/or an executable/behavioral model in usable form (not only a block diagram or PDF). Include a README describing what it represents and how to build or run it.

Is an Excel of my data enough? Yes, if it contains the real measured values behind a key result, with a short README and units. Not sufficient: only a picture of the plot, an empty or “coming soon” repository, or data unrelated to your key claims.

How to opt in

  1. Prepare a public repository, place the claimed artifacts there, and include a README (see below). Archiving via a DOI (Zenodo, IEEE DataPort) is encouraged but not mandatory.

  2. At submission, check the badge box(es) in the submission form and enter the public repository URL. The repository URL is hidden during the blind review stage to preserve anonymity. Do not reference or link the repository anywhere in the (blinded) paper. Describe the artifacts neutrally and do not reference the ISSCC submission or its figure numbers in your public repository while the paper is under review; you may add such references after acceptance.

  3. Repositories are checked starting October 1, and badges are assigned in October. Do not modify the repository after October 1, and keep it online for at least 3 years.

After acceptance, badges are displayed on the first page of the badged paper in the ISSCC digest, next to your paper in the program and on the conference website, and on the first and last slide of your presentation. Badge status may also serve as a tie-breaker for paper awards and JSSC invitations.

What to put in the README

Your README should let a reader understand the artifacts on their own, without needing the paper. Include:

  • A short, self-contained description of the design/system or dataset and what it represents.

  • The repository structure, and what each folder and file contains.

  • Open Data: what each dataset is and its units, how it was measured or generated, and (if provided) how to run any analysis/plotting scripts.

  • Open Design: what the model or RTL represents, how to build, run, or simulate it, and any dependencies.

  • The license you chose.

  • (Recommended) a DOI or archive reference.

What a badge means, and what it does not

An assigned badge signals availability, not verified content. The post-acceptance spot-check confirms that artifacts are present and correspond to the paper; it is not a review of correctness, completeness, or reproducibility. ISSCC does not verify, endorse, or take responsibility for the content of shared artifacts. Responsibility stays with the authors, exactly as it does for the content of the ISSCC paper itself. If shared content is later determined to be flawed or fraudulent, a review committee of TPC experts can be convened to take the appropriate actions.