New at DAC!
The Automotive Track will bring together people from the automotive and EDA domains, highlight current challenges and emerging solutions, and explore the road ahead.
Modern combustion engine vehicles largely rely on onboard electric and electronics components and systems. High-end cars now have over 100 electronic control units (ECUs) that are connected by a heterogeneous communication architecture, and run several millions of lines of software code.
Most of the innovations in the automotive domain are now in electronics and software. The emergence of electric vehicles have further pushed developments on this front.
Moreover, systematic modeling and cross-layer optimization can significantly improve mobility and energy efficiency both in design time and runtime, and EDA (electronics design automation) and embedded systems design therefore now have a major opportunity in the automotive domain and will play a significant role from now on.
Authors are responsible for ensuring that their manuscript meets the following guidelines. There will be no resubmissions to correct any issues.
- Stage one (Abstract Submission), a title, abstract, and a list of all co-authors must be submitted by November 22. You may also submit the manuscript at this time
- Stage two (Manuscript Submission), the paper itself is submitted by
Your manuscript will be reviewed as finished manuscripts. Preliminary submissions will be at a disadvantage.
SUBMISSION RULES (Abstract & Manuscript)
- Submitter must enter the names, affiliations, city, state country and email address of ALL co-authors. The addition of new co-authors will not be permitted after November 22
- 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)'s own previous work or affiliations in the bibliographic citations being in the third person
- The abstract of approximately 100 words must clearly state the significant contribution, impact, and results of the manuscript
- The manuscript must be double-columned, 10-pt font, in PDF format only and be a readable file
- Authors should submit up to 10 pages, in which the first 6 pages are the self-contained technical manuscript and the last 4 pages consist of an appendix. The appendix is completely optional. The purpose of the appendix is to provide supplemental material that could be beneficial to the reviewer, such as derivations, formal proofs, additional diagrams and examples.
- If the author chooses to include an Appendix, this must clearly be marked on the top of page 7 as an Appendix section. Papers that go longer than 6 pages and do not begin page 7 with an Appendix section will automatically be rejected. The purpose for this rule is to make sure authors write the paper to fit within the 6 page manuscript limit and only uses the appendix for additional details.
- Your final manuscript for the conference proceedings will have a maximum of 6 pages. The appendix is not part of the official proceedings.
- The addition of new co-authors will not be permitted after November 22
- DAC manuscripts go through a double-blind review process; i.e., the identity of authors and reviewers is only known to the TPC co-chairs.
- DAC ensures that there are no conflicts of interest between authors and reviewers.
- DAC will compare each submission against a vast database and any manuscript with significant similarity to previously published works or with manuscripts that are simultaneously under review with other venues with archival publications (e.g., conferences, symposia, journals, and workshops with archival proceedings)
- Duplicate submissions will be rejected. Furthermore, DAC will notify the technical chair of the venue where the duplicate was submitted.
AUTO1: Systems and Architecture & Software Design
AUTO1.1 Automotive E/E architectures
AUTO1.2 Model-based systems and software engineering
AUTO1.3 Automotive Control Systems Design
AUTO1.4 Virtualization in the automotive domain
AUTO1.5 Multicore challenges
AUTO2: Safety, Security and Reliability
AUTO2.1 Security threats and vulnerabilities
AUTO2.2 Architecture and software solutions for security
AUTO2.3 Formal verification and model-based testing
AUTO2.4 Safety requirements and their verification
AUTO2.5 Reliability in the nano-scale era
AUTO3: Interfaces & Driver Assistance Systems
AUTO3.1 AUTOSAR and automotive standards
AUTO3.2 HMI, infotainment and usability
AUTO3.3 Advanced driver assistance systems
AUTO3.4 Autonomous vehicles and active safety
AUTO3.5 Environment and uncertainty analysis and modeling
AUTO4: HEV/EV and Electromobility
AUTO4.1 Architectural design and optimization for EVs and HEVs
AUTO4.2 Electric and hybrid drive train and Power electronics
AUTO4.3 Batteries and hybrid energy storage systems
AUTO4.4 Infrastructure analysis, modeling, simulation and optimization
AUTO4.5 Energy-efficient vehicle and infrastructure design
A. 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 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 should submit up to 10 pages, in which the first 6 pages are the self-contained technical manuscript and the last 4 pages consist of an appendix. The appendix is completely optional. The purpose of the appendix supplemental material that could be beneficial to the reviewer, such as derivations, formal proofs, additional diagrams and examples.
If the author chooses to include an Appendix, this must clearly be marked on the top of page 7 as an Appendix section. Papers that go longer than 6 pages and do not begin page 7 with an Appendix section will automatically be rejected. The purpose for this rule is to make sure authors write the paper to fit within the 6 page manuscript limit and only uses the appendix for additional details.
Your final manuscript for the conference proceedings will have a maximum of 6 pages.
||Abstract submission site OPENS
||Abstract deadline: 5:00pm MT (-07:00 GMT)
||Final manuscripts deadline: 5:00pm MT (-07:00 GMT)
|January 29-31, 2014
||A list of accepted manuscripts is posted on the website
||Speaker registration and Copyright form deadline.
||Final manuscript is DUE to the proceedings publisher by 5:00pm MT (-07:00 GMT).
||Draft speaker presentation slides deadline
||Speaker bios are DUE
||Receive feedback on speaker slides from Session Chair
||The Design Automation Conference begins!
The DAC Technical Program Committee (TPC) determines the selection of research manuscripts to be included in the program, as well as their composition into technical sessions within the conference schedule. The Technical Program Committee is organized into a set of subcommittees which focus on the various topic areas involved in design and design automation. These are reasonably close, but not necessarily identical to the categories in the call for contributions. Manuscripts which are assigned by authors to the wrong categories may be reassigned to a subcommittee best able to review them. The Technical Program Committee Co-Chairs may also move manuscripts in order to resolve conflicts of interest with subcommittee members.
Each subcommittee will select the best manuscripts submitted with limits determined by the overall numbers of submissions, the capacity of the DAC schedule, and the number of manuscripts in each area. In recent years, acceptance rates for DAC manuscripts have been about 23% - for example, in 2013, 156 manuscripts were accepted from 743 submissions, a 21% acceptance rate.
The Technical Program Committee and its subcommittees will look at the following in selecting manuscripts:
- Quality of the technical contribution (design, method, research) described in the manuscript.
- Originality of the concepts used and described (whether tools, methods or design). Advances over previous approaches should be reflected in by describing the significant improvement in results section. Comparisons with other approaches are also important to justify the advancement claimed in your manuscript.
- Significance of the results obtained - 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 validation of the concepts. Use in real designs or widely accepted benchmarks with measurable criteria for results is 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.
- The decision to consider the manuscript and topic for a short or long presentation will be based in part on the significance of the work described and the amount of time required to present its content.
- Please be aware that the detailed criteria used to judge these manuscripts will differ from research/embedded-systems-and-software manuscripts and Designer Track papers.
Once a manuscript has been accepted, the subcommittee organizes it into an appropriate theme technical session.
A. The CFC lists several categories; please select the most appropriate one 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. Authors may choose a second submission category to accommodate cross-cutting contributions. Please note the separate categories for embedded systems and software topics.
A.Authors should submit up to 10 pages, in which the first 6 pages are the self-contained technical manuscript and the last 4 pages consist of an appendix.
The appendix is completely optional. The purpose of the appendix supplemental material that could be beneficial to the reviewer, such as derivations, formal proofs, additional diagrams and examples.
If the author chooses to include an Appendix, this must clearly be marked on the top of page 7 as an Appendix section. Papers that go longer than 6 pages and do not begin page 7 with an Appendix section will automatically be rejected.
The purpose for this rule is to make sure authors write the paper to fit within the 6 page manuscript limit and only uses the appendix for additional details.
Your final manuscript for the conference proceedings will have a maximum of 6 pages.
A. 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:Dutt and Hassoun presented a method for listing self-referential citations in .? P. N. Dutt and S. Hassoun, How to write a research DAC paper, 2010. (Available at *www.dac.com)
*link for example purposes only
A. DAC adheres to strict rules regarding double submissions. Your submissions must be clearly distinct. Use your judgment. If in doubt, consult with a more senior colleague. Double submissions are considered unethical, and a serious issue within IEEE and ACM.
- 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) Manuscripts will 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 security. 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.
- Design Automation Methodology Manuscripts and Design Manuscripts must be submitted as Designer Track extended abstract. Please refer to the Designer Track call for contributions and submission guidelines. The submission and review process for Designer Track will be treated separately to encourage the design community to participate at DAC.
A. If the TPC does not accept your manuscript as an regular paper, they will decide if your paper meets the requirements as Work-in-Progress. In this case you will be invited to present during a specific poster session, but the manuscript will not be published in the DAC proceedings. Please see the Work-in-Progress section in the Call for Contributions for more details.
Yes, Please go to the DAC Archives
for previously accepted submissions.
A. DAC will publish up to 6 pages of an accepted manuscript.