Topics of interest for workshop submissions include (but are not limited to)
- Programming experiences porting applications in any scientific domain
- Compiler and runtime support for current and emerging architectures (e.g. heterogeneous architectures, low-power processors
- Experiences in implementing compilers for accelerator directives on newer architectures
- Language-based extensions and its prototype for directive-based programming model
- Abstract handling of complex/heterogeneous memory hierarchies
- Extensions to and shortcomings of current directives for heterogeneous systems
- Comparisons against lower or higher level abstractions
- Application performance evaluation, validation and lessons learnt
- Modeling, verification and performance analysis tools
- Auto-tuning and optimization strategies
- Parallel computing using hybrid programming paradigms (e.g. MPI, OpenMP, OpenACC, OpenSHMEM)
- Asynchronous execution and scheduling (task based approaches)
- Scientific libraries interoperability with directive based models
Workshop Important Deadlines
- Paper Submission Deadline: August 22, 2018
- Author Notification: September 30, 2018
- Workshop Ready Deadline: October 10, 2018
- Workshop @SC18: November 11, 2018
- Camera Ready Deadline: December 10, 2018
- Proceedings Published: February/March 2019
WACCPD papers will be peer-reviewed and selected for presentation at the workshop. Papers will then be published as a post-proceedings in Lecture Notes in Computer Science. This means the camera ready version is due after the workshop. This is so that you improve your paper for the camera-ready version based on feedback received from the workshop along with reviews from the peer-review process.
Paper Submission Guidelines
- Papers should be submitted electronically via the SC18 Submission Page (https://submissions.supercomputing.org).
- They must follow the Springer LNCS format. Submissions are limited to 20 pages. The 20-page limit includes figures, tables, and appendices, but does not include references, for which there is no page limit.
- Submitted papers should not have appeared in or be under consideration for a different workshop, conference or journal.
- In submitting the paper, the authors acknowledge that at least one author of an accepted submission will register for and attend the workshop.
Reproducibility has already been well adopted within the SC Papers program, with about 40% of submissions and 50% of accepted papers containing a reproducibility appendix.
Moving in this direction, reproducibility is being strongly encouraged by submitters to SC workshops as well.
Please use additional 2 pages beyond the 20-page limit to add appendix information. These 2 pages will be part of your full technical paper during the review process. Once your paper is accepted, you will be able to lift these pages off the paper to be published by Springer and add the information to Zenodo or an associated capsule of Code Ocean or anything else you would like to use (pls avoid using personal webpages for this step).
You will then be asked to add a blurb or “artifacts available” in your paper to be published and point readers to wherever you have added information regarding reproducibility.
This way information on reproducibility is yours and will not become part of your Springer published proceedings.
For an example on how to go about this, please refer to any publication in https://collegeville.github.io/sc-reproducibility/ArtifactDescriptionAppendixTemplate.html and look for the 2 pages of information on reproducibility.
- A paper cannot be disqualified based on information provided or not provided in this appendix, nor if the appendix is not available.
- The availability and quality of an appendix can be used in ranking a paper. In particular, if two papers are of similar quality, the existence and quality of the appendices can be part of the evaluation process.
- In order to be considered for the Best Paper Award, the authors must submit an Artifact Description appendix.
- If the authors are not able to add such details, they must add a note that says, why not?