<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Hi Howard,
<div class=""><br class="">
</div>
<div class="">Good idea - we should devise the structure collaboratively, then divide up the writing between us. I use ShareLatex/Overleaf for collaborative “paper in latex" writing.</div>
<div class="">
<div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<br class="Apple-interchange-newline">
Cheers,</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Dan.</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
—<br class="">
Dr Daniel Holmes PhD<br class="">
Applications Consultant in HPC Research<br class="">
<a href="mailto:d.holmes@epcc.ed.ac.uk" class="">d.holmes@epcc.ed.ac.uk</a><br class="">
Phone: +44 (0) 131 651 3465<br class="">
Mobile: +44 (0) 7940 524 088<br class="">
Address: Room 3415, JCMB, The King’s Buildings, Edinburgh, EH9 3FD</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
—</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.</div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
—</div>
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 31 Jul 2018, at 00:30, Pritchard Jr., Howard <<a href="mailto:howardp@lanl.gov" class="">howardp@lanl.gov</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">we’re controversial - so maybe good for hot topic abstract?<br class="">
<br class="">
-- <br class="">
Howard Pritchard<br class="">
<br class="">
B Schedule<br class="">
HPC-ENV<br class="">
Office 9, 2nd floor Research Park<br class="">
TA-03, Building 4200, Room 203<br class="">
<br class="">
Los Alamos National Laboratory<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
On 7/30/18, 1:18 PM, "sc-workshop-attendee-cfp on behalf of Dosanjh,<br class="">
Matthew" <<a href="mailto:sc-workshop-attendee-cfp-bounces@group.supercomputing.org" class="">sc-workshop-attendee-cfp-bounces@group.supercomputing.org</a> on<br class="">
behalf of <a href="mailto:mdosanj@sandia.gov" class="">mdosanj@sandia.gov</a>> wrote:<br class="">
<br class="">
<blockquote type="cite" class="">From: Dosanjh, Matthew<br class="">
Sent: Monday, July 30, 2018 11:19 AM<br class="">
To: <a href="mailto:hpc-announce@mcs.anl.gov" class="">hpc-announce@mcs.anl.gov</a><br class="">
Subject: CFP: Workshop on Exascale MPI 2018 (ExaMPI), held in<br class="">
conjunction with Supercomputing 2018 (SC18), Dallas, TX<br class="">
<br class="">
ExaMPI18 - Workshop on Exascale MPI 2018<br class="">
Sunday November 11th, 2018<br class="">
Dallas, TX, USA<br class="">
<a href="https://sites.google.com/site/exampiworkshop2018" class="">https://sites.google.com/site/exampiworkshop2018</a><br class="">
<br class="">
Held in conjunction with SC18: The International Conference<br class="">
for High Performance Computing, Networking, Storage and Analysis<br class="">
<br class="">
===========================================================<br class="">
<br class="">
The MPI standard and its implementations have proved surprisingly<br class="">
scalable. Issues that hampered scalability have been addressed in the MPI<br class="">
2.1 – 2.2 definition process, and continued into MPI 3.0 and 3.1. Thus<br class="">
MPI has been robust, and been able to evolve, without fundamentally<br class="">
changing the model and specification. For this and many other reasons MPI<br class="">
is currently the de-facto standard for HPC systems and applications.<br class="">
However, there is a need for re-examination of the message-passing<br class="">
model for extreme-scale systems characterized by asymptotically<br class="">
decreasing local memory and highly localized communication networks.<br class="">
Likewise, there is a need for exploring new innovative and potentially<br class="">
disruptive concepts and algorithms partially to explore other roads than<br class="">
those taken by the recently released MPI 3.1 standard.<br class="">
The aim of workshop is to bring together developers and researchers to<br class="">
present and discuss innovative algorithms and concepts in Message Passing<br class="">
programming models, in particular related to MPI. This year’s theme is on<br class="">
concurrency in MPI and underlying networks and we especially encourage<br class="">
submissions aligned with this theme.<br class="">
<br class="">
Topics of interest (but are not limited to)<br class="">
<br class="">
--------------------------------------------------------------------------<br class="">
-------------<br class="">
<br class="">
* Development of scalable Message Passing collective operations.<br class="">
<br class="">
* Communication topology mapping interfaces and algorithms.<br class="">
<br class="">
* Innovative algorithms for scheduling/routing to avoid network<br class="">
congestion.<br class="">
<br class="">
* Integrated use of structured data layout descriptors.<br class="">
<br class="">
* One-sided communication models and RDMA-based MPI.<br class="">
<br class="">
* MPI multi-threading and threading requirements from OSes.<br class="">
<br class="">
* Interoperability of Message Passing and PGAS models.<br class="">
<br class="">
* Integration of task-parallel models into Message Passing models.<br class="">
<br class="">
* Fault tolerance in MPI.<br class="">
<br class="">
* MPI I/O.<br class="">
<br class="">
Paper submission and publication<br class="">
--------------------------------------------------------------------------<br class="">
-------------<br class="">
There are two submission categories:<br class="">
<br class="">
* Regular research paper: submission of full paper. Regular paper<br class="">
submissions are limited to 10 single-space pages (including figures,<br class="">
tables<br class="">
and references) using a 10-point on 8.5x11-inch pages (US Letter).<br class="">
<br class="">
Templates can be found at:<br class="">
https://www.acm.org/publications/proceedings-template. Instructions for<br class="">
preparing regular papers for the proceedings will be emailed to authors<br class="">
of accepted papers.<br class="">
<br class="">
* Hot topic abstract: submission of an extended abstract. These<br class="">
submissions target work-in-progress research on potentially controversial<br class="">
topics in Message-Passing. Hot topic extended abstracts are limited to 3<br class="">
single-space pages:<br class="">
https://www.acm.org/publications/proceedings-template. Accepted hot topic<br class="">
extended abstracts will be published only on the ExaMPI15 website.<br class="">
<br class="">
Regular Papers and extended abstracts should be submitted electronically<br class="">
at: https://tinyurl.com/ExaMPI2018<br class="">
<br class="">
This year, ExaMPI has streamlined the paper review and submission<br class="">
process. Submissions will be accepted via the regular SC submission<br class="">
system and reviews will be available via that system. For publication of<br class="">
the papers, accepted papers from the SC submission system will be invited<br class="">
to submit the papers that were reviewed in the conference review system<br class="">
to a special issue of the Journal of Concurrency and Computation:<br class="">
Practice and Experience. This will allow for quick publication in the<br class="">
journal of accepted papers that only require minor revisions in the<br class="">
journal process, while some papers may be shepherded with major revisions<br class="">
overseen using the journal submission process.<br class="">
<br class="">
Accepted papers at ExaMPI will only be published in the journal (CCPE),<br class="">
not the workshop proceedings, so there is no need for a 30% difference<br class="">
between the submitted paper and the journal submission.<br class="">
<br class="">
Important dates<br class="">
--------------------------------------------------------------------------<br class="">
-------------<br class="">
Paper Submissions close: October 9th<br class="">
Paper Notification: October 23rd<br class="">
Papers submitted to Journal: November 9th<br class="">
Final notification from Journal: December 7th<br class="">
Final camera ready version: December 14th<br class="">
<br class="">
_______________________________________________<br class="">
sc-workshop-attendee-cfp mailing list<br class="">
sc-workshop-attendee-cfp@group.supercomputing.org<br class="">
http://group.supercomputing.org/mailman/listinfo/sc-workshop-attendee-cfp_<br class="">
group.supercomputing.org<br class="">
</blockquote>
<br class="">
_______________________________________________<br class="">
mpiwg-sessions mailing list<br class="">
<a href="mailto:mpiwg-sessions@lists.mpi-forum.org" class="">mpiwg-sessions@lists.mpi-forum.org</a><br class="">
https://lists.mpi-forum.org/mailman/listinfo/mpiwg-sessions<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>