<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p>Workshop on Dynamic Distributed Data-Intensive Applications, Programming Abstractions, and Systems (3DAPAS)</p><p><a href="http://sites.google.com/site/3dapas/">http://sites.google.com/site/3dapas/</a></p><p>To be held in conjunction with HPDC-2011, 8 June 2011, San Jose, CA</p><p>There has been a lot of effort in managing and distributing tasks
where computational loads are dominant. Such applications have after
all, been historically the drivers of “grid” computing. There has,
however, been relatively less effort on tasks where the computational
load is matched by the data load, or even dominated by the data load.
For such tasks to be able to operate at scale, there are conceptually
simple run-time trade-offs that need to be made, such as determining
whether to move data to compute versus keeping data localized and move
computational tasks to operate on the data in situ, or possibly neither,
and with data regenerated on-the-fly. Due to fluctuating resource
availability and capabilities, as well as insufficient prior information
about application requirements, such decisions must be made at
run-time. Furthermore, resource, connectivity and/or storage constraints
may require the data to be manipulated in-transit so that it is
“made-right” for the consumer. Currently it is very difficult to
implement these dynamic decisions or the underlying mechanisms in a
general-purpose and scalable fashion.<br>
Although the increasing volumes and complexity of data will make many
problems data load dominated, the computational requirements will still
be high. In practice, data-intensive applications will encompass
data-driven applications. For example, many data-driven applications
will involve computational activities triggered as a consequence of
independently created data; thus it is imperative for an application to
be able to respond to unplanned changes in data load or content.
Therefore, understanding how to support dynamic computations is a
fundamental, but currently missing element in data-intensive computing.</p><p>This workshop will operate at the triple point of dynamic and
distributed and data-intensive (3D) attributes. This workshop will
operate at the triple point of dynamic, distributed and data-intensive
(3D) attributes. It will also focus on innovative approaches for
scalability in the end-to-end real-time processing of scientific data.
We refer to 3D applications as those are data-intensive, need to support
and respond to dynamic data, and, either are fundamentally, or need to
be, distributed. We are interested in papers that span the spectrum from
the design of cyberinfrastructure to support 3D applications, to novel
application examples. We are also looking to bring researchers together
to look at holistic, rather than piecewise, approaches to the end-to-end
processing and managing of scientific data.</p><p>3DAPAS builds upon a 3 year research theme on Distributed
Programming Abstractions (DPA), which has held a series of related
workshops (see: DPA Past Events,
<a href="http://wiki.esi.ac.uk/Distributed_Programming_Abstractions#Past_Events">http://wiki.esi.ac.uk/Distributed_Programming_Abstractions#Past_Events</a>)
including but not limited to e-Science2008, EuroPar 2008 and the CLADE
series. 3DAPAS will also draw on ideas from the ongoing 3DPAS Research
Theme (<a href="http://wiki.esi.ac.uk/3DPAS">http://wiki.esi.ac.uk/3DPAS</a>) funded by the NSF and UK EPSRC.</p><p>Topics of interest include but are not limited to:</p>
<ul>
        <li>Case studies of development, deployment and execution of representative 3D applications</li>
        <li>Programming systems, abstractions, and models for 3D applications</li>
        <li>What are the common, minimally complete, characteristics of 3D application?</li>
        <li>What are major barriers to the development, deployment, and
execution of 3D applications? What are the primary challenges of 3D
applications at scale?</li>
        <li>What patterns exist within 3D applications, and are there commonalities in the way such patterns are used?</li>
        <li>How can programming models, abstraction and systems for
data-intensive applications be extended to support dynamic data
applications?</li>
        <li>Tools, environments and programming support that exist to enable
emerging distributed infrastructure to support the requirements of
dynamic applications (including but not limited to streaming data and
in-transit data analysis)</li>
        <li>Data-intensive dynamic workflow and in-transit data manipulation</li>
        <li>Abstractions and mechanisms for dynamic code deployment and “moving the code to the data”</li>
        <li>Application drivers for end-to-end scientific data management</li>
        <li>Runtime support for in-situ analysis</li>
        <li>System support for high end workflows</li>
        <li>Hybrid computing solutions for in-situ analysis</li>
        <li>Technologies to enable multi-platform workflows</li>
</ul><p>Submission Requirements:</p><p>Authors are invited to submit technical papers of at most 8 pages in
PDF format, including all figures and references. Papers should be
formatted in the ACM Proceedings Style
(<a href="http://www.acm.org/sigs/publications/proceedings-templates">http://www.acm.org/sigs/publications/proceedings-templates</a>) and
submitted via EasyChair
(<a href="https://www.easychair.org/account/signin.cgi?timeout=1;conf=3dapas">https://www.easychair.org/account/signin.cgi?timeout=1;conf=3dapas</a>).
Accepted papers will appear in the conference proceedings, and will be
incorporated into the ACM Digital Library.</p><p>Submission of a paper implies that at least one author will attend the workshop to present the paper, if it is accepted.</p><p>Papers must be self-contained and provide the technical substance
required for the program committee to evaluate the paper’s contribution.
Papers should thoughtfully address all related work. Submitted papers
must be original work that has not appeared in and is not under
consideration for another conference or a journal. See the ACM Prior
Publication Policy
(<a href="http://www.acm.org/publications/policies/sim_submissions">http://www.acm.org/publications/policies/sim_submissions</a>) for more
details.</p><p>Important Dates:</p><p>Submissions Due: 31 Jan 2011<br>
Paper Decisions Announced: 28 Feb 2011<br>
Final Camera-Ready Papers Due: 24 Mar 2011<br>
Workshop Date: 8 June 2011<br>
(all dates are firm)</p><p>Organizers:</p>
<ul>
        <li>Daniel S. Katz, University of Chicago & Argonne National Laboratory, USA</li>
        <li>Shantenu Jha, Louisiana State University, USA & e-Science Institute, UK</li>
        <li>Jon Weissman, University of Minnesota, USA</li>
</ul><p>Program Committee Members:</p>
<ul>
        <li>Gabrielle Allen, Louisiana State University, USA</li>
        <li>Malcolm Atkinson, eSI & University of Edinburgh, UK</li>
        <li>Henri Bal, Vrije Universiteit, Netherlands</li>
        <li>Jon Blower, Reading e-Science Centre, University of Reading, UK</li>
        <li>Shawn Brown, University of Pittsburgh & Pittsburgh Supercomputing Center, USA</li>
        <li>Simon Dobson, University of St. Andrews, UK</li>
        <li>GIles Fedak, INRIA, France</li><li>Geoffrey Fox, Indiana University, USA,</li><li>Dennis Gannon, Microsoft, USA</li>
        <li>Keith R. Jackson, Lawrence Berkeley National Lab, USA</li>
        <li>John R. Johnson, Pacific Northwest National Laboratory, USA</li>
        <li>Scott Klasky, University of Tennessee & Oak Ridge National Laboratory, USA</li>
        <li>Bertram Ludscher, University of California, Davis, USA</li>
        <li>Abani Patra, University of Buffalo, USA</li>
        <li>Manish Parashar, Rutgers & NSF, USA</li>
        <li>Omer Rana, Cardiff University, UK</li>
        <li>Joel Saltz, Emory University, USA</li>
        <li>Domenico Talia, Universita’ della Calabria, Italy</li>
</ul><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 9px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 9px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span class="Apple-style-span" style="font-family: 'Lucida Grande'; font-size: 10px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="font-family: Helvetica; font-size: 12px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "><font class="Apple-style-span" face="Courier">-- </font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "><font class="Apple-style-span" face="Courier">Daniel S. Katz</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "><font class="Apple-style-span" face="Courier">University of Chicago</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "><font class="Apple-style-span" face="Courier">(773) 834-7186 (voice)</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "><font class="Apple-style-span" face="Courier">(773) 834-3700 (fax)</font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; "><font class="Apple-style-span" face="Courier"><a href="mailto:d.katz@ieee.org">d.katz@ieee.org</a> or <a href="mailto:dsk@ci.uchicago.edu">dsk@ci.uchicago.edu</a></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; min-height: 14px; "><span class="Apple-style-span" style="font-family: Courier; "><a href="http://www.ci.uchicago.edu/~dsk/">http://www.ci.uchicago.edu/~dsk/</a></span></div><div><font class="Apple-style-span" face="Courier"><br></font></div></div></div></span></div></div></div></span></div></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br></body></html>