Submission Format

Stage One: Abstract Submission

• A title, abstract (approximately 100 words), and a list of all co-authors must be submitted by November 12, 2024 (5:00pm US Pacific Time). You may also submit the manuscript at this time.
• A submitter must enter the names, affiliations, countries and email addresses of ALL co-authors. Conflicts of Interest with TPC members of ALL authors must be identified.

Stage Two: Manuscript Submission

• The manuscript (up to 6 pages plus an additional 1 page for references only) is due by November 19, 2024 (5:00pm US Pacific Time). Each submitted manuscript must discuss original work that has not been previously published in other indexed research databases. It must not be actively reviewed at another conference or journal at the time of submission.
• Authors are responsible for ensuring that their manuscript meets the submission rules. There will be no opportunity for re-submission to correct any issues after the November 19, 2024, deadline.
• Your manuscript will be reviewed as a finished manuscript. Preliminary submissions will be at a disadvantage.

|back to top|

---

Submission Timeline

• September 27, 2024: Submission Opens
• November 12, 2024, 5pm US Pacific Time: Abstract Deadline
• November 19, 2024, 5pm US Pacific Time: Manuscript Deadline
• February 26, 2025: Accept/Reject Notifications Sent
• March 13, 2025: Confirmation Forms Due
• April 10, 2025: Proceedings Manuscript Deadline
• April 10, 2025: Registration Deadline
• April 25, 2025: Draft Slides Due for Subcommittee Chair Review
• May 26, 2025: Slide Feedback Provided
• June 2, 2025: Final Slides Due
• June 22, 2025: DAC begins

|back to top|

---

Submission Rules

• Research manuscripts only submission policy: An individual may not be an author on more than 20 research manuscripts. If an individual exceeds this limit, the first 20 submitted manuscripts (time base submissions) that include that individual’s name will be reviewed. All other submitted manuscripts over 20, will be rejected immediately. Serious violations will be reported to IEEE and ACM for disciplinary action. DAC Technical Program Committee members have additional submission limitations:
  • Technical program committee members are limited to submitting at most five manuscripts, posters, or presentations to their conference program (Research or Engineering Track).
  • In addition, technical program committee members are not allowed to submit more than three manuscripts to their own sub-committee and may be included in at most one invited submission/presentation.
  • Moreover, no Subcommittee Chair, Sub-Committee Co-Chair within a Technical Program Committee shall submit to its own subcommittee.
• A submitter must enter the names, affiliations, countries, and email addresses of ALL co-authors. The addition of new co-authors or re-ordering of authors will not be permitted after the November 19 deadline
• An abstract of approximately 100 words must clearly state the significant contribution, impact and results of the manuscript.
• No new submissions are allowed after the November 12 deadline.
• The submission must not disclose the author(s) by their name(s) or affiliation(s) anywhere in the manuscript or abstract. Submissions that reveal the authors’ identities will be desk rejected and will not be reviewed by the TPC. Any reference to the author(s)' own previous work or affiliations in the bibliographic citations must be cited in the third person. The use of “omitted for blind review” in the bibliography section is not permitted. The authors must make sure that the PDF metadata does not contain the author information.
• The manuscript must be within 6 pages, excluding references, double-columned, 9 or 10-pt font, in PDF format only, be a readable file and follow the IEEE style template. The length and content of the submitted version and that of the final version (if accepted) should not be significantly different. All references must be listed in the additional reference page. Only one page of references is allowed. Inclusion of any content other than the references on the reference page will result in the desk rejection of the submission. The manuscript and the reference page must be formatted as a single PDF file.  
• Your draft manuscript must leave enough space to include authors, acknowledgements and other identifying information for the final version without exceeding the 6 page limit.. 
• A submitter is required to check the conflicts of interests (COI) field and the duplicate submission field. See the "Conflict of Interest" section and the "Duplicate Submission" section for further information

One author of each accepted submission is required to:

• Prepare and submit the final version of the manuscription for the official conference proceedings.
• Sign and submit the copyright form.

In addition:

• One co-author on the paper is required to pay the full conference Speaker Registration Fee; student rates cannot be used. Each accepted paper requires a unique registration.
• The speaker must present the paper IN-PERSON at the conference. As part of the acceptance confirmation, international authors will be required to identify an alternative presenter who will present the work if there are any issues in obtaining travel visas.
• The authors of each accepted paper must prepare a poster to be displayed after the conference.

Following IEEEs policy on authorship, anyone listed as Author on a paper must meet all the following criteria:

• made a significant intellectual contribution to the theoretical development, system or experimental design, prototype development, and/or the analysis and interpretation of data associated with the work contained in the paper;
• contributed to drafting the paper or reviewing and/or revising it for intellectual content;
• approved the final version of the paper as accepted for publication, including references.

Contributors who do not meet all of the above criteria may be included in the Acknowledgment section of the paper. Submissions which fail to follow the above guidelines will be automatically rejected. Serious violations will be reported to IEEE and ACM for disciplinary action.

|back to top|

---

Duplicate Submissions

DAC adheres to strict rules regarding duplicate submissions. Submissions must be clearly novel and distinct with respect to other submissions to 62 DAC, concurrent submissions to other conferences and previously published work.

• All closely related work should be properly referenced. If such related work is authored by one of the co-author(s) of the manuscript in submission, it should be referenced as if it were written by others.
• Any extended version of the submitted manuscript should not be submitted or under review before the formal notification of the DAC ‘s review decision.
• If any co-author has any paper that may be perceived as having overlapping contributions and that is simultaneously under review by another venue, such papers must be disclosed in the submission process.

The DAC publication policy does allow for papers published on arXiv to be submitted to DAC. Note, however, that the authors are expected to follow all reasonable efforts to ensure that the DAC submission is compliant with the double-blind review process.

Submissions which fail to follow the above guidelines will be automatically rejected. In serious cases, the authors’ names will be reported to IEEE & ACM and kept in records, as well as sent to the Technical Chair or the Editor of the venue where the duplicate manuscript was submitted; the authors may be banned from publishing at future DAC conferences.

|back to top|

---

Disclosure Process for Unpublished Work

When submitting to DAC, authors face a dilemma. DAC has a blind review process in which the author’s identity remains anonymous. However, the submission rules compel the authors to cite relevant publications that have already been accepted or are under review by another conference (such as ICCAD, DATE, ASP-DAC, etc.). Disclosing these papers under the citation list reveals the authors’ identities. To circumvent this issue, DAC has implemented a disclosure process.

When submitting a paper, the authors are asked to list each relevant paper that has not yet been published and include the corresponding pdf of the paper. The TPC Chair will be able to check for self-plagiarism and relevance without revealing the author identities to the reviewers. Failure to disclose such papers will be considered as omission of closely related work and subject to the same penalties outlined in the Duplicate Submissions, as discussed in the section.

|back to top|

---

Conflict of Interest

To further strengthen the review process, each submitter is asked to identify any Technical Program Committee (TPC) members with whom s/he has conflict of interests (COI). The TPC list is available below.

An author has a conflict with a member of the Technical Program Committee if one or more of the situations below holds:

• Advisor-advisee relation
• Co-authors of a paper (published and/or under review) in the last 24 months
• Author and TPC member are from the same institution
• Co-PIs of a grant in the last 2 years
• Close personal or family relationship

The submitter should indicate the COIs of all authors with members of the Technical Program Committee upon submission and make the best effort to ensure their correctness. Failure to do so may lead to desk rejection of the submission. Intentional omission or false assertion of COI information will also lead to desk rejection of the submission.  

|back to top|

---

Frequently Asked Questions

How should I submit a research manuscript?

Authors are asked to submit their work in two stages. In stage one (Abstract Submission), a title, abstract, and a list of all co-authors must be submitted via the DAC web-submission site. In stage two (Manuscript Submission), the manuscript itself is submitted. Authors are responsible to ensure that their manuscript submission meets all guidelines, and that the PDF is readable. To ensure fairness for all submitters, there will be no grace periods to fix problematic submissions.

The manuscript should stand on its own, with references in the last page. The manuscript must be within 6 pages, with one additional reference page, double-columned, 9 or 10-pt font, in PDF format only, be a readable file and follow the IEEE style template. The length and content of the submitted version and that of the final version (if accepted) should not be significantly different; the draft manuscript must leave enough room to allow for the inclusion of author information, acknowledgements and other identifying information in the final version. There will be no chance of resubmitting to correct any issues.

How should I submit the conflict of interest (COI) information?

Submitters should report COIs of all co-authors with respect to members of the Technical Program Committee upon submission. However, it is recommended that submitters work on marking COIs as soon as they submit their manuscript's abstract, since this task may require some time, which is often scarce in the final sprint towards the completion of a manuscript's submission. Modifications to marked COIs can be made any time prior to the manuscript deadline.

Authors are asked to mark all the TPC members who have COIs with at least one of the authors at the time of abstract registration. Do not mark any members of the Technical Program Committee as COI where there is no COI.

What if authors failed to identify TPC members with COI?

DAC assumes that authors have no additional COIs with TPC members, beside those that have been declared at the time of manuscript submission. If a manuscript is found to have failed in identifying a  COI, during or after the paper selection process, the submitted manuscript will be automatically rejected. Same hold if members of the Technical Program Committee are marked as COI if no COI exists.

Which category should I select when I submit my manuscript?

The Call for Contributions lists several categories; please select the most appropriate primary topic when submitting your abstract. Authors of submissions that cover cross-cutting topics should select a category that is closest to the essential contribution of the submission. Submissions will be asked to select a broad category (ex. “EDA1. System-on-chip and HW/SW Codesign”). A complete list of available categories and topic areas can be found in the CFP.  Please note that there are separate categories for electronic design automation topics, embedded systems and software topics, autonomous electronic design, design and system security, and electronic design topics.

If my work is mainly about design, should I submit it to the regular research track or the Engineering Tracks?

The Research track at 62 DAC will include a DESIGN (DES) focus to feature high-quality contents on design research, design practices, and design automation for cross-cutting topics.

If you think that your work makes a significant contribution to any of the design related topics, you should consider writing a complete 6-page research manuscript and submit it to the regular research track. On the other hand, if your work is more of a design practice using EDA tools or if you cannot meet the research manuscript deadline, you can consider submitting your work to the Engineering Tracks, which do not require a manuscript and entail no publication.

Six pages only, or is additional 4-page supplemental material allowed?

All submissions to the Research Track are subject to the six-page limit, with one additional page for references only. The manuscript plus one page of references should be formatted as a single PDF file. It is the authors’ responsibility to ensure the readability of the PDF file and submit it by the November 19 deadline.

The page limit of the submissions is 6+1, not 7. The last page is reserved for references only. Inclusion of any content other than references on the additional reference page will lead to the desk rejection of the submission.

How do I avoid referencing my own work to ensure the integrity of the blind review process?

To satisfy the criteria for a blind review process, the Call for Contributions states that any references to the author(s) own previous work or affiliations in the bibliographic citations must be in the third person. For the blind review process, DO NOT LIST THE NAMES OR AFFILIATIONS OF ANY OF THE AUTHORS ANYWHERE ON THE MANUSCRIPT, except in the references section (if citation to prior work is required).

Example: A. and B. presented a method for listing self-referential citations in [5].


[5] A. A and B. B, How to write a research DAC paper, 2021.

DO NOT use “omitted for blind review” to cite authors’ own papers. Describe all related papers published by you as if they were written by others.

Citation of authors’ unpublished papers is not allowed, including citation of potential double and/or simultaneous submissions. If this situation arises, submitters must follow the disclosure requirements to disclose their (or their co-authors) related work that is under review or accepted for publication.

I submitted a longer version of my manuscript to another conference/journal. Can I still submit it to DAC?

DAC adheres to strict rules regarding double and/or simultaneous submissions. No new technical content should be under review during any time overlapping with DAC's selection and publication of manuscripts. In general, an extended version of the conference paper should be submitted to a journal after the first day of the conference. Your submissions must be clearly distinct from any other submissions under review. Use your judgment. If in doubt, consult with a more senior colleague. Double submissions are unethical, and a serious issue within the ACM & IEEE communities.

Can a paper that has been uploaded to *arXiv* be submitted to DAC?

The DAC publication policy does allow for papers published on arXiv to be submitted to DAC. Note, however, that the authors are expected to follow all reasonable efforts to ensure that the DAC submission is compliant with the double-blind review process.

How do I disclose a paper under review or an accepted but not published paper?

When submitting a paper, the authors are asked to list all potentially relevant papers that have not yet been published and provide an electronic copy (in pdf format) of those papers. The TPC Chair will be able to check for self-plagiarism and relevance without revealing author identities to the reviewers. Failure to disclose such papers will be considered as omission of closely related work and subject to the same penalties outlined in the "Duplicate Submissions" section.

What makes a good DAC manuscript?

• Artificial Intelligence (AI)  research manuscripts feature advances in the field of AI / Machine Learning (ML) with a focus on design automation and designs at the cross section between AI/ML algorithms/applications and hardware. The scope includes but is not limited to novel AI/ML algorithms, applications, infrastructures, and how to address growing security/privacy concerns of AI/ML.
• Electronic Design Automation (EDA) research manuscripts have at their core novel algorithms or novel algorithm implementations for important problems facing leading edge electronic design automation. These may address the problem at any level of abstraction (from high-level blocks down to the bare transistor). They can cover both design implementation (for example, physical layout or logic synthesis) and design analysis (for example, signal integrity analysis, rule checking, functional verification, and circuit simulation).
• Design (DES) research manuscripts feature high-quality contributions on design research, design practices, and design automation for cross-cutting topics, ranging from systems and architectures, particularly specialized solutions to embedded systems, storage and memory structures.
• Security (SEC)
• Systems (SYS) research manuscripts cover novel advances in areas such as embedded systems software and hardware, from the very highest levels of system specification (e.g., domain-specific languages and model based design) to hardware/software implementations of embedded systems, their associated software design tools and architectural platforms, as well as validation, verification, and reliability. Systems topics will also cover modeling, optimization, and exploration of multiple embedded system constraints (e.g., reliability, power, security). Systems  case studies, platforms and design methodologies are also an integral part of these topics.

Can I submit as a Work-in-Progress (WIP) presentation if my paper is not accepted as a research manuscript?

If the TPC subcommittee does not accept your manuscript as a research manuscript at DAC, they will also determine if your submission meets the requirements for a WIP presentation and invite WIP-eligible manuscripts to present during a specific poster session at DAC. Note that WIP presentations papers are not published in the DAC proceedings. Thus, in this situation, you do not need to re-submit your manuscript to the WIP submission site.

You may also submit other distinct works directly through the LBR submission site. Please see the Late Breaking Results section in the Call for Contributions for more details.

 I still have some questions. Who do I contact?

For additional information, please contact:

• Chia-Lin Yang, 62 DAC Technical Program Chair
• Frank Liu, 62 DAC Technical Program Co-Chair
• Natarajan Viswanathan, 62 DAC Technical Program Co-Chair

|back to top|

---

Review and Selection Process

The DAC Technical Program Committee (TPC) determines the selection of research manuscripts to be included in the DAC program, as well as how they are integrated into technical sessions within the conference schedule. The Technical Program Committee is organized into several subcommittees, which focus on the various topic areas that are relevant to the conference. These are reasonably close, but not necessarily identical to the categories in the call for contributions. Manuscripts which are assigned by authors to unfitting categories may be reassigned by the program committee chair and subcommittee chairs to a subcommittee best able to review them.

DAC strives to ensure that there are no conflicts of interest (COI) between authors and reviewers so as to provide a review process that is fair to all the authors. Submitters should report conflict of interests for all co-authors with members of the Technical Program Committee by the manuscript submission deadline, as discussed in the “Conflict of Interests” tab. The Technical Program Committee Chair may reassign manuscripts to different subcommittees to resolve conflicts of interest with Technical Program Committee members.

DAC will also compare each submission against a vast database to identify manuscripts which have significant similarity to previously published works. Submissions identified as plagiarized during this process will be rejected. Furthermore, the names of all the authors of the submission will be reported to IEEE and ACM, as well as the TPC Chair or the Editor-in-Chief of the venue where the duplicate was submitted. Further information on duplicate submissions is provided under the "Duplicate Submissions" tab at the top of this page.

Then DAC manuscripts undergo a double-blind review process; i.e., the identity of authors and reviewers is only known to the Technical Program Committee (TPC) Chair. Each subcommittee will select the best manuscripts submitted. The selectivity is influenced by the overall numbers of submissions, the capacity of the DAC schedule, and the number of manuscripts in each area.

The Technical Program Committee and its subcommittees will take into account the following aspects in selecting manuscripts:

• Quality of the technical contribution (design, solution, methodology) described in the manuscript.
• Originality of the concepts used and described. Advances over previous approaches should be reflected in the discussion of significant improvements in the results section. Comparisons with other approaches are also important to justify the advancement claimed in the submitted manuscript.
• Significance of the results obtained, described by measurable quantitative criteria (runtime for tools, optimality of results, time for design process steps, simplification or automation of manual effort, etc.).
• Degree of experimental evidence to support the claims of the manuscript. Results supported by evidence in industry-strength designs or widely accepted benchmarks with measurable criteria are highly desirable, if not essential.
• A good discussion of limitations of the approach and concepts, and possible areas for future improvement.
• The quality of manuscript writing, use of English, organization and clarity of presentation.
• Once a manuscript has been accepted, the subcommittee organizes it into an appropriate technical session; sessions are then scheduled throughout the duration of the conference.

|back to top|

---

Copyright Information

Authors of accepted papers must complete the IEEE Copyright Form, which will be emailed to the contact author in March. One copyright form is required for each accepted paper.

• Any issues/questions authors have regarding the copyright form or IEEE Policy may be addressed to IEEE.
• Authors and co-authors are subject to all IEEE Publications Policies
• Any issues/questions authors have regarding the copyright form or IEEE Policy may be addressed to IEEE.

|back to top|

---

Policy on the AI/ChatGPT

We follow ACM/IEEE policy ond the AI/ChatGPT. In brief, the use of AI software tools (such as ChatGPT, Jasper, AI Write, Lex, for example) is permitted, subject to the following requirements.

• That these systems do not plagiarize, misrepresent, or falsify contents in submissions.
• That if any of generative AI software tools are used to generate new content such as text, images, tables, code, etc., it must be disclosed in either the acknowledgements section of the work or elsewhere in the work prominently, including but not limited to the specific tools and versions, the text of the prompts provided as input, and any post-generation editing (such as rephrasing the generated text). 
• That if authors are using generate AI software tools to edit and improve the quality of your existing text in much the same way you would use a typing assistant like Grammarly to improve spelling, grammar, punctuation, clarity, engagement or to use a basic word processing system to correct spelling or grammar, it is not necessary to disclose such usage of these tools in the work. 
• That the authors accept full responsibility for the veracity and correctness of all material in their work, including any computer-generated materials. 
• ACM’s Publishing Policy can be found here and the Author Rights page can be found here.
• Any issues/questions authors have regarding the copyright form or ACM Policy addressed to ACM.

​|back to top|

---

Categories

For a list with detailed descriptions, visit the Research Paper Submissions Categories page.

Artificial Intelligence (AI)

The Artificial Intelligence (AI) program highlights the advances in the field with a focus on leading AI designs and AI usage in design automation. 

• AI1. AI/ML Algorithms
• AI2. AI/ML Application and Infrastructure
• AI4. AI/ML Architecture Design
• AI5.  AI/ML System and Platform Design

Design (DES)

The design topics covered in the research track include the design of cyber-physical, System-on-Chip (SoC) and multi-die architectures, accelerator-based computing, emerging models of computation such as brain-inspired and quantum computing, digital and analog circuits, and emerging device technologies.

• DES1. SoC, Heterogeneous, and Reconfigurable Architectures
• DES2A. In-memory and Near-memory Computing Circuits 
• DES2B. In-memory and Near-memory Computing Architectures, Applications and Systems
• DES3. Emerging Models of Computation
• DES4. Digital, and Analog Circuits
• DES5. Emerging Device and Interconnect Technologies
• DES6. Quantum Computing

Electronic Design Automation (EDA)

In addition to the traditional EDA topics ranging from physical design to system architectures, DAC features high-quality papers on design research, design practices, and design automation for cross-cutting topics including low-power, reliability, multicore/application-specific/heterogeneous architectures, 3-D integrations, multi-die systems, emerging device technologies, design automation of "things", and their applications. 

• EDA1. Design Methodologies for System-on-Chip and 3D/2.5D System-in Package
• EDA2. Design Verification and Validation
• EDA3. Timing Analysis and Optimization
• EDA4. Power Analysis and Optimization
• EDA5. RTL/Logic Level and High-level Synthesis 
• EDA6. Analog CAD, Simulation, Verification and Test
• EDA7. Physical Design and Verification
• EDA8. Design for Manufacturability and Reliability 
• EDA9. Test, Validation and Silicon Lifecycle Managemen

Security (SEC)

Security topic at DAC focuses on the urgent need to create, analyze, evaluate, and improve the hardware, embedded systems and software base of the contemporary security solutions. Secure and trustworthy software and hardware components, platforms and supply chains are vital to all domains including financial, healthcare, transportation, and energy.

• SEC1. AI/ML Security/Privacy
• SEC2. Hardware Security: Primitives, Architecture, Design & Test
• SEC3. Hardware Security: Attack and Defense
• SEC4. Embedded and Cross-Layer Security 

Systems (SYS)

Systems Design is the art of choosing and designing the proper combination of hardware and software components to achieve system-level design goals like speed, efficiency, reliability, security, and safety. 

• ​SYS1. Autonomous Systems (Automotive, Robotics, Drones)
• SYS2. Design of Cyber-Physical Systems and IoT
• SYS3. Embedded Software
• SYS4. Embedded System Design Tools and Methodologies
• SYS5. Embedded Memory and Storage Systems
• SYS6. Time-Critical and Fault Tolerant System Design

Topics

Please select up to two of the following Topic Areas:

• Artificial Intelligence
• Design
• Electronic Design Automation
• Security
• Systems

Keywords

Please select up to three of the following Keywords:

• AI and Machine Learning
  Analog & Mixed-signal Design
• Architecture & System Design
• Chiplets and Interconnects
• Circuits and Technology
• Cloud Computing
• Design Technology Co-optimization
• Embedded Systems and IoT
• Emerging Technologies
• FPGA Systems
• Formal/Static Methods
• Low Power
• Logic & High-level Synthesis
• Manufacturing and Process
• Physical Design
• Quantum Computing
• Safety & Reliability
• Security & Privacy
• Test
• Verification & Validation

Industry

If a submission will be relevant to a specific industry or industries, one or more of the following industries may be selected:

• Aerospace and Defense
• Automotive
• Consumer
• Data Center
• Industrial
• Wireless Communications
• Wired Communications

|back to top|