Below please find information, DAC presentation guidelines and best practices to prepare your final manuscript and session presentation.
RESEARCH MANUSCRIPT TIMELINE
- September 29, 2023 - Submission Opens
- November 13, 2023 - Abstract Deadline
- November 20, 2023 - Manuscript Deadline
- February 26, 2024 - Accept/Reject Notification
- March 13, 2024 - Acceptance confirmation due
- March 20, 2024 - Speaker registration opens
- April 10, 2024 - Accepted papers must submit copyright forms.
- April 10, 2024 - Final manuscript is DUE to the proceedings publisher by 5:00pm PT (-08:00 GMT).
- April 28, 2024 - Speaker Registration Deadline
- April 15, 2024 - Speakers will receive instructions for preparation and submission of presentation slides and video presentations
- April 26, 2024 - Speaker bio and draft slides due for review by subcommittee chairs.
- May 7, 2024 - Subcommittee chairs provide feedback to speakers regarding their draft slides
- May 7, 2024 - Pre-recorded presentation video submission stage opens
- May 21, 2024 - Final presentation slides and video presentations are due for the DAC archive
CAMERA READY PAPER GUIDELINES
ACM is the 2024 copyright holder for 61 DAC so your final paper is planned to be included in the ACM Digital library for archival value after the conference.
Please use the ACM templates to format your paper. Use the Interim templates.
You may not, in any way, revise the content of your manuscript other than to address minor formatting issues, or to add acknowledgements or references that would have invalidated a double-blind review.
ACM authors and co-authors are subject to all ACM Publications Policies https://www.acm.org/publications/policies, including ACM's new Publications Policy on Research Involving Human Participants and Subjects https://www.acm.org/publications/policies/research-involving-human-participants-and-subjects
ACM’s ORCID Requirement will expand to include Conferences October 1, 2022. A unique author ID (ORCID) can be set up at orcid.org/register and be connected to the ACM Profile. ORCIDs allow ACM to more reliably identify authors, even when there are variants in the use of their names or when multiple authors share the same name.
ACM provides access to the Crossref iThenticate® We strongly encourage conferences to take advantage of this system or other plagiarism systems available on the market.
GUIDELINES AND TEMPLATE FOR PPT SLIDES:
- You are required to use the DAC template for all presentations:
- ONLY PPT, PPTX, or PDF files are allowed
- Only landscape format may be used
- We do not allow any information in the footer except for the page number. Everything else will just distract from the content of the slides
- Company/University name and/or logo may only appear on the title (first slide) page
- Please note if the presentation guidelines and template are not used in the final pre-recorded video your presentation may be removed from the program.
POLICY ON 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.
POSTER GUIDELINES
Presenting authors are required to also present a poster describing their work (see below for poster guidelines) for the last 20 minutes of their session. This provides an opportunity for extended discussion with interested members of the audience.
Each author is allocated a 42” tall x 36” wide area for a poster.
- One poster board is allocated to each presentation.
- Posters must be mounted using push pins provided by the organizing committee.
- Do not use foam core material for your poster or any other thick/heavy material.
- Poster presenters are responsible for printing their own poster and carrying or shipping it to the conference.
- The title of your poster should be done in block letters which are AT LEAST 8 to 10 cm (3 to 4 inches) high.
- All text must be easily readable from a distance of 1 to 2 meters. Make the lettering at least 1 cm high, smaller lettering will not be legible from a distance of 1 to 2 meters.
- All graphs and charts should be AT LEAST 25 X 30 cm (approximately 8.5 x 11 inches) or larger.
- Please include a copy of the DAC logo at the bottom right corner of your poster. You can download the PNG image file here.
- It is a good idea to sequentially number your materials in the poster. This will indicate to the viewer a logical progression through your poster.
- Provide an introduction (outline) and a summary or conclusion for your poster.
- Prepare your poster carefully so that it can be used as the basis to explain and answer questions from the viewers.
- Have your business cards available for those who may wish to contact you at a later date.
- Bring along a tablet of blank paper that you may use for a discussion of technical details relating to your poster.
VIDEO GUIDELINES
Each session is required to submit a video presentation along with their final presentation. The pre-recorded video will be used for Best Presentation Award review process. It is imperative for your video to be submitted on schedule for the Best Presentation Award review process. More information will be provided after the selection of Best Presentation candidates.
- This recording will be 15 minutes. Audio and slides are required, optional to record your webcam as a thumbnail image (consider this in your slide layout)
- All presenters are required to use the DAC 2024 PPT template and to follow slide presentation guidelines above.
- Final video presentation files must be saved as an MP4. We can ONLY accept MP4.
- Each speaker will have access to an "Upload Your Final Presentation and Video" stage in the speaker/paper management system beginning May 7.
- Pre-recorded video presentations are due no later than May 21.
- Once the video presentation is uploaded to the secure site there will be no updates or changes.
- Files may be up to 150MB.
How to pre-record your presentation:
- Presentations can be recorded using the following applications:
- All pre-recorded video presentations are required horizontal (landscape) orientation.
- The audio source needs to be as close to the microphone in an environment that has little or no other noise or echo.
- Use a headset to record your audio to reduce outside noises and review the instructions on how to produce clear and quality audio.
GOOD CLEAR AUDIO and CLEAR EASY TO READ SLIDES are essential
- Record more than one video for review and practice. Take note of your lighting and audio when reviewing your pre-recorded presentation. It is not uncommon to take more than 2-3 video recordings before the final version.
It is required that you review the best practice guidelines before pre-recording.
SUBMISSION RULES (ABSTRACT & MANUSCRIPT)
- A submitter must enter the names, affiliations, cities, states, countries and email addresses of ALL the co-authors. The addition of new co-authors will not be permitted after November 20.
- DO NOT identify the author(s) by their name(s) or affiliation(s) anywhere on the manuscript or abstract, with all references to the author(s)' own previous work or affiliations in the bibliographic citations being in the third person. Avoid the use of “omitted for blind review” in the bibliography section. Make sure the PDF metadata does not contain the author information.
- The abstract of approximately 100 words must clearly state the significant contribution, impact, and results of the manuscript.
- The manuscript must be within 6 pages, double-columned, 9 or 10-pt font, in PDF format only, be a readable file and follow the IEEE template
- A submitter is required to check the conflicts of interests (COI) field and the duplicate submission field. See the "Conflict of Interest" tab and the "Duplicate Submission" section for further information.
- An author of each accepted submission is required to:
- Produce a paper for the official conference proceedings.
- Sign and submit a copyright form.
- All accepted presentations are expected to submit a video of their presentation in advance of the event. This does not replace participation in the event.
- In addition:
- One co-author on the paper is required to pay the Speaker Registration Fee.
- The speaker must present the paper at the conference. If anyone other than a co-author of the paper presents the paper at the conference, the paper will be removed from the proceedings.
- Following IEEE's policy on authorship, anyone listed as Author on a paper must meet all the following criteria:
- They have made substantial intellectual contributions to some components of the original work described in the paper; and
- They have participated in drafting and/or revision of the paper; and
- They are aware that the paper has been submitted for publication; and
- They agree to be held accountable for any issues relating to correctness or integrity of the work
DUPLICATE SUBMISSIONS
DAC adheres to strict rules regarding duplicate submissions. Submissions must be clearly novel and distinct with respect to other submissions to DAC 2024, concurrent submissions to other conferences and previously published work.
Submissions which fail to follow the above guidelines will be automatically rejected. In serious cases, the authors’ names will be reported to IEEE and 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.
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.
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. Failure to do so may lead to automatic rejection of the submission. If the submitter marks members of the Technical Program Committee as COI where there is in fact no COI, that may also lead to automatic rejection.
PRESENTATION REVIEW PROCESS
STEP 1: SUBMIT DRAFT SLIDES AND BIO FOR REVIEW
Deadline: May 7
Prior to the conference, the session chair will review each presenter's slides and provide feedback to the speaker.
When the session chair has completed their slide review, the speaker will receive an email notification to log back into the review site to view the session chair comments.
Please contact the session chair if you do not hear from them with feedback by May 7.
STEP 2: UPLOAD FINAL SLIDES FOR PRESENTATION AND ARCHIVE
Deadline: May 21
All speakers are asked to upload their final presentation slides so they can be included in the DAC Archive pages on dac.com. Research presentation slides from this upload will also be loaded onto the presentation computers in the meeting rooms for your use during the presentation. If you update your slides after the final slide upload, email speakers@dac.com to provide a final version for uploading to the DAC computers.
REQUIRED EVENTS
Please attend the Speaker's Breakfast the day of your presentation:
- Tuesday, July 11 at 7:30am
- Wednesday, July 12 at 7:30am
- Thursday, July 13 at 7:30am
AV INFORMATION
Meeting rooms will have the following equipment:
- LCD Projector
- 16x9 Aspect Ratio Screen
- Laptop Computer with Microsoft Office
- Wireless Lavaliere Microphone
- Audio Equipment
- Aisle Microphones for Questions
- Laser Pointer
- Speaker Timer
PRACTICE ROOMS
Practice rooms will be available for:
- Last-minute polishing.
- Rehearsing your presentation in front of friends or colleagues.
- Fine-tuning your timing.
FREQUENTLY ASKED QUESTIONS
How should I submit a research manuscript?
Authors are asked to submit their work in two stages. In stage one (Abstraction 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 for ensuring 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.
Authors are to submit a 6 page manuscript. The manuscript should stand on its own, with references in the last page of the 6-pages manuscript. Authors are responsible for ensuring that their manuscript meets the manuscript guidelines of the ACM, including font size, line spacing, etc. There will be no chance of resubmitting to correct any issues.
In addition, authors should make sure to fulfill the conflict of interest rules as specified in the "Conflict of Interest" tab at the top of this webpage.
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 the is in fact 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 where there is in fact no COI.
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 their 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 Designer or IP Tracks?
The research track at DAC 2024 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 Designer Track or IP Track, 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. No additional supplemental material is allowed.
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 IEEE & ACM communities.
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" tab.
What makes a good DAC manuscript?
- DAC 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).
- DAC Embedded Systems and Software (ESS) research manuscripts cover novel advances in 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. ESS topics will also cover modeling, optimization, and exploration of multiple embedded system constraints (e.g., reliability, power, security). ESS case studies, platforms and design methodologies are also an integral part of these topics.
- DAC 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.
- DAC Security (SEC) research manuscripts span topics relating to embedded systems, cross-layer and hardware security, applied to all the layers of the hardware stack, from devices to architectures. The nature of the manuscripts range from attacks, to protection mechanisms and metrics.
- Finally, DAC Autonomous electronic design (AS) research manuscripts discuss autonomous system design tools and methodologies.
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
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 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.