|
| 1 | +--- |
| 2 | +title: "Call for papers: PACT'25: Submission Date Extension" |
| 3 | +timestamp: "4/9/2025 19:35:45" |
| 4 | +--- |
| 5 | +Call for Papers PACT'25 |
| 6 | + |
| 7 | +PACT 2025 will be held in Irvine, California, USA, from November 3-6, 2025. |
| 8 | +Abstract due: April 11 April 18 |
| 9 | +Full paper due: April 18 April 25 |
| 10 | + |
| 11 | +Submission Site: https://pact25.hotcrp.com/ |
| 12 | + |
| 13 | +Scope |
| 14 | +The International Conference on Parallel Architectures and Compilation Techniques (PACT) is a unique technical conference at the intersection of hardware and software, with a special emphasis on parallelism. PACT brings together researchers from computer architectures, compilers, execution environments, programming languages, and applications to present and discuss their latest research results, tools, and practical experiences. |
| 15 | + |
| 16 | +PACT 2025 will be held as an in-person event in Irvine, California, USA. We encourage all authors of accepted papers to participate, and at least one author must attend the conference. |
| 17 | + |
| 18 | +PACT seeks submissions in two categories: |
| 19 | + • Research Papers |
| 20 | + • Tools and Practical Experience (TPE) Papers |
| 21 | + |
| 22 | +Topics of Interest |
| 23 | +PACT welcomes submissions on topics including, but not limited to: |
| 24 | + • Parallel architectures, including accelerators for AI and other domains |
| 25 | + • Compilers and tools for parallel architectures |
| 26 | + • Applications and experimental studies of parallel processing |
| 27 | + • Computational models for concurrent execution |
| 28 | + • Multicore, multithreaded, superscalar, and VLIW architectures |
| 29 | + • Compiler and hardware support for reducing memory latencies |
| 30 | + • Support for correctness in hardware and software |
| 31 | + • Reconfigurable parallel computing |
| 32 | + • Dynamic translation and optimization |
| 33 | + • I/O issues in parallel computing and their application impact |
| 34 | + • Parallel programming languages, algorithms, and applications |
| 35 | + • Middleware and runtime system support for parallel computing |
| 36 | + • Application-specific parallel systems |
| 37 | + • Distributed computing architectures and systems |
| 38 | + • Heterogeneous systems leveraging various accelerators |
| 39 | + • In-core and in-chip accelerators and their optimization |
| 40 | + • Applications of machine learning to parallel computing |
| 41 | + • Large-scale data processing, including in-memory computing accelerators |
| 42 | + • Insights from modern parallel applications for architecture and compiler design |
| 43 | + |
| 44 | +Research Papers |
| 45 | +Research papers will be evaluated by the PACT Program Committee based on: |
| 46 | + • Relevance: The paper should align with PACT’s topics of interest. |
| 47 | + • Novelty/Originality: The work should present new ideas or offer fresh perspectives. |
| 48 | + • Significance: The research should address an important problem and have the potential to influence future work. |
| 49 | + • Results: The claims should be well-supported by clear and validated results. |
| 50 | + • Comparison to Prior Work: The paper should properly discuss existing literature, highlighting similarities, differences, and improvements. |
| 51 | + |
| 52 | +Tools and Practical Experience (TPE) Papers |
| 53 | +TPE papers focus on practical applications, industry challenges, and experience reports. A TPE paper must clearly explain its functionality, summarize practical experience with realistic case studies, and describe any supporting artifacts. The title of a TPE paper must include the prefix “TPE:”. TPE papers follow the same submission guidelines and are reviewed by the same Program Committee as research papers. |
| 54 | + |
| 55 | +TPE papers will be evaluated based on: |
| 56 | + • Originality: They should present PACT-related technologies applied to real-world problems. |
| 57 | + • Usability: The tool or software should have broad applicability and aid PACT-related research. |
| 58 | + • Documentation: The tool/software should be well-documented on a public website. |
| 59 | + • Benchmark Repository: A benchmark suite should be provided for testing. |
| 60 | + • Availability: Preference is given to tools/software that are freely available, though industry/commercial tools may be considered with justification. |
| 61 | + • Foundations: The paper should relate to PACT’s principles, though extensive theoretical discussion is not required. |
| 62 | + |
| 63 | +Submission Guidelines |
| 64 | +Submissions are due April 18, 2025, via the conference submission site. Ensure that your submission meets the following requirements: |
| 65 | + • Format: Papers are limited to 10 pages (excluding references) in ACM 8.5” x 11” format, double-column, 9pt font (e.g., using the sigconf LaTeX template). The text box must not exceed 7.15” x 9” (18.2cm x 22.9cm). Templates are available on the ACM Author Gateway. |
| 66 | + • Abstract: Papers must include an abstract of under 300 words. |
| 67 | + • Originality: Submissions must contain original material not previously published or under review elsewhere. Material presented at workshops without copyrighted proceedings may be submitted. |
| 68 | + • TPE Papers: Must be prefixed with “TPE:” in the title. |
| 69 | + • Double-Blind Review: The review process is double-blind to prevent bias. Submissions must not include author names, affiliations, or self-references that reveal authorship. Prior work by the authors must be cited in the third person. |
| 70 | + • Legibility: Figures and graphs must be readable without magnification. |
| 71 | + • Submission Format: Papers must be submitted in PDF format. |
| 72 | + • Supplementary Material: A single anonymized PDF may be uploaded with additional proofs, results, or datasets. Reviewers are not required to consult supplementary material. |
| 73 | + |
| 74 | +Posters: |
| 75 | + • Poster submissions must follow the same formatting guidelines but are limited to 2 pages. |
| 76 | + • Papers not accepted for full presentation will automatically be considered for posters unless authors opt out in their abstract submission. |
| 77 | + • Two-page poster summaries will be included in the conference proceedings. |
| 78 | + |
| 79 | +Conflicts of Interest |
| 80 | +Authors must declare all conflicts of interest with PC members and external reviewers at submission time. Papers with undeclared or false conflicts may be rejected. Conflicts follow ACM’s Conflict of Interest Policy. |
| 81 | + |
| 82 | +Artifact Evaluation |
| 83 | +Authors of accepted papers are encouraged to submit their artifacts for evaluation. The Artifact Evaluation Committee assesses availability, functionality, and reproducibility. Successful artifacts will receive a seal of approval in the published paper. Authors can include a 2-page Artifact Appendix in the final paper. |
| 84 | +We encourage authors to use open-source frameworks such as Docker, OCCAM, reprozip, CodeOcean, and Collective Knowledge to improve artifact portability and reproducibility. |
| 85 | + |
| 86 | +Camera-Ready Instructions |
| 87 | + • Page Limit: The final version must not exceed 11 pages, with an optional 2-page Artifact Appendix. |
| 88 | + • Extra Pages: Up to 2 additional pages may be purchased for $200 per page. |
| 89 | + |
| 90 | +Important Dates |
| 91 | + • Abstract Submission Deadline: April 11, 2025 |
| 92 | + • Paper Submission Deadline: April 18, 2025 |
| 93 | + • Rebuttal Period: June 24-27, 2025 |
| 94 | + • Author Notification: July 28, 2025 |
| 95 | + • Artifact Submission: August 8, 2025 |
| 96 | + • Camera-Ready Deadline: September 15, 2025 |
| 97 | +All deadlines are firm at midnight anywhere on Earth (AoE). |
| 98 | + |
| 99 | +Code of Conduct |
| 100 | +All participants must adhere to: |
| 101 | + • ACM Code of Ethics and Professional Conduct |
| 102 | + • IEEE Code of Ethics and Code of Conduct |
| 103 | + • ACM Policy Against Harassment |
| 104 | + |
| 105 | +Publication Policies |
| 106 | +PACT is supported by ACM and IEE. Accepted papers will be published in both the ACM Digital Library and IEEE Xplore. By submitting a paper, authors agree to comply with all ACM and IEEE publication policies. |
| 107 | +All authors must obtain an ORCID ID to complete the publication process. ORCID improves author discoverability, proper attribution, and name normalization. |
| 108 | + |
| 109 | +We look forward to your submissions! |
0 commit comments