<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><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=""><div class=""><b class="">2nd Call for Submissions:<br class=""><br class="">4th Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE4)</b><br class="">(<a href="http://wssspe.researchcomputing.org.uk/wssspe4/" class="">http://wssspe.researchcomputing.org.uk/wssspe4/</a>)<br class=""><br class="">Location: School of Computer Science, Kilburn and IT Buildings, University of Manchester, Manchester, UK<br class="">Dates: 2 ½ days from Sept. 12th noon – Sept. 14th 5 pm, 2016<br class="">Immediately preceding and co-located in Manchester with First Conference of Research Software Engineers</div><div class="">(RSE Conference) (Sept 15-16 at Museum of Science and Industry, Manchester, UK)<br class=""><br class="">Follow @wssspe, tweet with #wssspe<br class=""><br class="">A nominal registration fee may be charged.<br class=""><br class=""><b class="">Abstract:</b></div><div class=""><br class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Progress in scientific research is dependent on the quality and accessibility of research software at all levels. It</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">is now critical to address many new challenges related to the development, deployment, maintenance, and</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">sustainability of open-use research software: the software upon which specific research results rely. Open-use</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">software means that the software is widely accessible (whether open source, shareware, or commercial). </div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Research software means that the choice of software is essential to specific research results; using different</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">software could produce different results.<br class=""><br class="">In addition, it is essential that scientists, researchers, and students are able to learn and adopt a new set of</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">software-related skills and methodologies. Established researchers are already acquiring some of these skills,</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">and in particular, a specialized class of software developers is emerging in academic environments who are an</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">integral and embedded part of successful research teams. WSSSPE provides a forum for discussion of these</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">challenges, including both positions and experiences, and a forum for the community to assemble and act.<br class=""><br class="">WSSSPE4 will consist of two separate tracks with some joint sessions:<br class=""><br class="">Track 1 – Building a sustainable future for open-use research software has the goals of defining a vision of the</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">future of open-use research software, and in the workshop, initiating the activities that are needed to get there. </div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">The idea of this track is to first think about where we want to be 5 to 10 years from now, without being too</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">concerned with where we are today, and then to determine how we can move to this future.</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br class="">Track 2 – Practices & experiences in sustainable scientific software has the goal of improving the quality of</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">today’s research software and the experiences of its developers by sharing practices and experiences. This</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">track is focused on the current state of scientific software and what we can do to improve it in the short term,</div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">starting with where we are today.</div><div class=""><br class=""></div><b class="">Topics of interest include but are not limited to:</b></div><div class=""><b class=""><br class=""></b><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Development and Community<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Best practices for developing sustainable software<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Models for funding specialist expertise in software collaborations<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Software tools that aid sustainability<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Academia/industry interaction<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Refactoring/improving legacy scientific software<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Engineering design for sustainable software<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Metrics for the success of scientific software<br class=""></div><div class=""> • Adaptation of mainstream software practices for scientific software</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Professionalization<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Career paths<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • RSE as a brand<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • RSE outside of the UK or Europe<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Increase incentives in publishing, funding and promotion for better software</div><div class="">• Training<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Training for developing sustainable software<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Curriculum for software sustainability<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Credit<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Making the existing credit and citation ecosystem work better for software<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Future credit and citation ecosystem<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Software contributions as a part of tenure review<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Case studies of receiving credit for software contributions<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Awards and recognition that encourage sustainable software<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Software publishing<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Journals and alternative venues for publishing software <br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Review processes for published software<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Software discoverability/reuse<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Proposals and case studies<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Reproducibility and testing<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Reproducibility in conferences and journals<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> • Best practices for code testing and code review<br class=""></div><br class=""><b class="">Important Dates:<br class=""></b><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Submission of lightning talks: July 10<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Submission of Track 1 idea papers: July 10</div><div class="">• Submission of Track 2 position papers, experience papers, presentations of previously</div><div class=""> published works, and demos: July 10<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Submission of travel support requests: July 10<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Lightning talk decisions announced: Aug 1<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Track 1 idea papers decisions announced: Aug 1</div><div class="">• Track 2 position papers, experience papers, presentations of previously published works,</div><div class=""> and demo decisions announced: Aug 1<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Travel support decisions announced: Aug 2<br class=""></div><br class=""><b class="">Submission types and formats:<br class=""></b><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Lightning talks: a short paper, up to 2 pages, that if accepted can be conveyed in a 5 to 7 minute talk,</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> either on Track 1: Building a sustainable future for open-use research software or Track 2: Practices & experiences</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> in sustainable scientific software. Lightning talks may be based on either novel or previously published work, but</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> must contain a core idea that will contribute to the discussion in the workshop.<br class=""></div><div class=""><div class="">• Idea papers: a longer paper, up to 8 pages, that presents implementable proposals related to Track 1: Building a</div><div class=""> sustainable future for open-use research software. Track 1 participants will build on the proposals and ideas in</div><div class=""> these papers, with the goal of initiating the planning, development, and execution of some of the ideas during the</div><div class=""> workshop itself. Given the magnitude and importance of the task at hand, the WSSSPE4 organizing committee</div><div class=""> encourages these proposals to be developed on an open, public, and inclusive basis. Submitters are invited to</div><div class=""> present a vision of some aspect of the future of open-use research software, and a plan of activities to gather and</div><div class=""> organize the resources needed to get there.<br class=""></div><div class=""> Example idea paper topics:</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Adaptation of industrial software engineering principles into the research software community with a plan to</div><div class=""> fund the work<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Funding and scaling software carpentry style training in advanced topics<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Infrastructure and funding for community maintenance of open use research software<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Scaling the SSI beyond the UK<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Specific proposals of how to bridging/network the various research software engineering communities in scalable</div><div class=""> manner without destroying independence and unique foci of each community</div></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Position papers: a longer paper, not previously published, up to 8 pages, that if accepted can be conveyed in</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> a 15 to 20 minute talk, on Track 2: Practices & experiences in sustainable scientific software, specifically discussing</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> what we can do to improve sustainable scientific software in the short term, starting with where we are today.<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Experience papers: a longer paper, not previously published, up to 8 pages, that if accepted can be conveyed</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> in a 15 to 20 minute talk, on Track 2: Practices & experiences in sustainable scientific software, specifically discussing</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> current practices and experiences and how they have been used to improve the quality of today’s research software</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> and/or the experiences of its developers.<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Presentation of previously published work: a short paper, up to 2 pages, that if accepted can be conveyed in</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> a 15 to 20 minute talk, describing a previous published work by the authors and its relevance to Track 2: Practices &</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> experiences in sustainable scientific software on the topic of improving the quality of today’s research software and</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> the experiences of its developers by sharing practices and experiences.<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Demos: a short paper, up to 2 pages plus 2 pages of screenshots, that if accepted can be conveyed in a 10 to</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> 15 minute demonstration, showing a tool or process relevant to Track 2: Practices & experiences in sustainable</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> scientific software, that improves the quality of today’s research software and/or the experiences of its developers.</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span> Demo submissions may be based on previously published work.<br class=""></div><br class=""><b class="">Submission process:<br class=""></b>All submissions should be created in PDF format. They should begin with a title, author names and affiliations, a short</div><div class="">abstract, then the body of the submission. The title should begin with “Lightning talk:” or “Position paper:” or</div><div class="">“Experience paper:” or “Idea paper:” or “Previously published:” or “Demo:”. Submissions should also include a statement</div><div class="">of their license, preferably CC BY 4.0. Submissions should be made via <a href="https://easychair.org/conferences/?conf=wssspe4" class="">https://easychair.org/conferences/?conf=wssspe4</a>.</div><div class="">WSSSPE4 accepted submissions (except presentations of previously published work) will be published by WSSSPE as a</div><div class="">special collection in <a href="http://ceur-ws.org/" class="">http://ceur-ws.org/</a>. Authors retain copyright to their work and are free to self-publish their submissions</div><div class="">or accepted papers elsewhere in addition.</div><div class=""><br class=""><br class=""><b class="">Preliminary Agenda:<br class=""></b><br class=""></div><div class="">Sept 12 pm – Joint session of both tracks<br class=""><br class=""> Introduction<br class=""> Keynote<br class=""> Lightning talks<br class=""> Updates on actions and activities from WSSSPE3 working groups<br class=""> Discussion and planning for the remainder of WSSSPE4<br class=""><br class="">Sept 13 (all day) and 14 (until 3 pm) – Parallel tracks<br class=""><br class=""> Track 1: This will be a set of working sessions with a facilitated discussion, breakout sessions, report backs, and active</div><div class=""> writing towards the track goal of defining a vision of the future of open-use research software, and a plan of activities that</div><div class=""> are needed to get there.<br class=""> Track 2: presentations of position papers, experience papers, previously published works, and demos; and breakout</div><div class=""> sessions or unconference sessions.<br class=""><br class="">Sept 14 (1:30 pm – 5 pm) – Joint session of both tracks<br class=""><br class=""> Panel on best practices<br class=""> Summary and discussion of each tracks’ progress<br class=""> Planning for future events<br class=""><br class=""><b class="">Organizing Committee:<br class=""></b><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Gabrielle Allen, University of Illinois Urbana-Champaign, USA<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Jeffrey Carver, University of Alabama, USA<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Sou-Cheng T. Choi, Illinois Institute of Technology, USA<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Tom Crick, Cardiff Metropolitan University, UK<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Michael R. Crusoe, Common Workflow Language project<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Sandra Gesing, University of Notre Dame, USA<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Robert Haines, University of Manchester, UK<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Michael Heroux, Sandia National Laboratory, USA<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Lorraine J. Hwang, University of California, Davis, USA<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Daniel S. Katz, University of Illinois Urbana-Champaign, USA<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Kyle E. Niemeyer, Oregon State University, USA <br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Manish Parashar, Rutgers University, USA<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• Colin C. Venters, University of Huddersfield, UK<br class=""></div><br class=""><b class="">Program Committee:</b></div><div class=""><div class=""><span class="Apple-tab-span" style="white-space: pre;"></span>• (in progress, see web site for additions)</div><div class="">• David Abramson, University of Queensland, Australia<br class=""></div><div class="">• Lorena A. Barba, George Washington University, USA<br class=""></div><div class="">• Ross Bartlett, Sandia National Laboratories, USA<br class=""></div><div class="">• Christoph Becker, University of Toronto, Canada<br class=""></div><div class="">• David Bernholdt, Oak Ridge National Laboratory, USA<br class=""></div><div class="">• Stefanie Betz, Karlsruhe Institute of Technology, Germany<br class=""></div><div class="">• Coral Calero, Universidad Castilla La Mancha, Spain<br class=""></div><div class="">• Ishwar Chandramouli, National Cancer Institute, National Institutes of Health, USA<br class=""></div><div class="">• Ruzanna Chitchyan, University of Leicester, UK<br class=""></div><div class="">• Neil Chue Hong, Software Sustainability Institute, University of Edinburgh, UK<br class=""></div><div class="">• Karen Cranston, Duke University, USA<br class=""></div><div class="">• Ewa Deelman, Information Sciences Institute, University of Southern California, USA<br class=""></div><div class="">• Dave De Roure, Oxford e-Research Centre, University of Oxford, UK<br class=""></div><div class="">• Charlie E. Dibsdale, O-Sys, Rolls Royce PLC, UK<br class=""></div><div class="">• Alberto Di Meglio, CERN, Switzerland<br class=""></div><div class="">• Anshu Dubey, Argonne National Laboratory, USA<br class=""></div><div class="">• Nadia Eghbal, Independent Researcher (via Ford Foundation), USA<br class=""></div><div class="">• Martin Fenner, DataCite, Germany<br class=""></div><div class="">• David Gavaghan, University of Oxford, UK<br class=""></div><div class="">• Mike Glass, Sandia National Laboratories, USA<br class=""></div><div class="">• Carole Goble, University of Manchester, UK<br class=""></div><div class="">• Joshua Greenberg, Alfred P. Sloan Foundation, USA<br class=""></div><div class="">• Michael K Griffiths, University of Sheffield, UK<br class=""></div><div class="">• James Hetherington, University College London, UK<br class=""></div><div class="">• Fred J. Hickernell, Illinois Institute of Technology, USA<br class=""></div><div class="">• Caroline Jay, University of Manchester, UK<br class=""></div><div class="">• Matthew B. Jones, University of California Santa Barbara, USA<br class=""></div><div class="">• Nick Jones, New Zealand eScience Infrastructure (NeSI), NZ<br class=""></div><div class="">• Jong-Suk Ruth Lee, National Institute of Supercomputing and Networking, KISTI (Korea Institute</div><div class=""> of Science and Technology Information), Korea<br class=""></div><div class="">• Sedef Akinli Kocak, Ryerson University, Canada<br class=""></div><div class="">• James Lin, Shanghai Jiao Tong University, China<br class=""></div><div class="">• Frank Löffler, Louisiana State University, USA<br class=""></div><div class="">• Gregory Madey, University of Notre Dame, USA<br class=""></div><div class="">• Ketan Maheshwari, University of Pittsburgh, USA<br class=""></div><div class="">• Steven Manos, University of Melbourne, Australia<br class=""></div><div class="">• Chris A. Mattmann, NASA JPL & University of Southern California, USA<br class=""></div><div class="">• Abigail Cabunoc Mayes, Mozilla Science Lab, USA<br class=""></div><div class="">• Robert H. McDonald, Indiana University, USA<br class=""></div><div class="">• Lois Curfman McInnes, Argonne National Laboratory, USA<br class=""></div><div class="">• Chris Mentzel, Gordon and Betty Moore Foundation, USA<br class=""></div><div class="">• Peter Murray-Rust, University of Cambridge, UK<br class=""></div><div class="">• Christopher R. Myers, Cornell University, USA<br class=""></div><div class="">• Jarek Nabrzyski, University of Notre Dame, USA<br class=""></div><div class="">• Cameron Neylon, Curtin University, Australia<br class=""></div><div class="">• Aleksandra Pawlik, New Zealand eScience Infrastructure (NeSI), NZ<br class=""></div><div class="">• Fernando Perez, Lawrence Berkeley National Laboratory & University of California, Berkeley, USA<br class=""></div><div class="">• Marian Petre, The Open University, UK<br class=""></div><div class="">• Marlon Pierce, Indiana University, USA<br class=""></div><div class="">• Andreas Prlic, University of California, San Diego, USA<br class=""></div><div class="">• Karthik Ram, University of California, Berkeley, USA<br class=""></div><div class="">• Morris Riedel, Juelich Supercomputing Centre, Germany<br class=""></div><div class="">• Norbert Seyff, University of Zurich, Switzerland<br class=""></div><div class="">• Arfon Smith, GitHub Inc, USA<br class=""></div><div class="">• Borja Sotomayor, University of Chicago, USA<br class=""></div><div class="">• Edgar Spalding, University of Wisconsin, USA<br class=""></div><div class="">• Maria Spichkova, RMIT University, Australia<br class=""></div><div class="">• Victoria Stodden, University of Illinois Urbana-Champaign, USA<br class=""></div><div class="">• Matthew Turk, University of Illinois Urbana-Champaign, USA<br class=""></div><div class="">• Ewout van den Berg, IBM Watson, USA<br class=""></div><div class="">• Nancy Wilkins-Diehr, San Diego Supercomputer Center, University of California, San Diego, USA<br class=""></div><div class="">• James Willenbring, Sandia National Laboratories, USA<br class=""></div><div class="">• Scott Wilson, Cetis LLP, UK<br class=""></div><div class="">• Theresa Windus, Iowa State University and Ames Laboratory, USA</div><div class=""><br class=""></div></div><div class="">
<div style="color: rgb(0, 0, 0); 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 style="color: rgb(0, 0, 0); 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 class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><span class="Apple-style-span" style="font-family: Courier; font-size: 12px;">-- </span></div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="font-size: 12px; orphans: 2; widows: 2; margin: 0px;" class=""><font class="Apple-style-span" face="Courier">Daniel S. Katz</font></div><div style="font-size: 12px; orphans: 2; widows: 2; margin: 0px;" class=""><font class="Apple-style-span" face="Courier">Assistant Director for Scientific Software and Applications, NCSA</font></div><div style="font-size: 12px; orphans: 2; widows: 2; margin: 0px;" class=""><font class="Apple-style-span" face="Courier">Research Associate Professor, ECE</font></div><div style="font-size: 12px; orphans: 2; widows: 2; margin: 0px;" class=""><font class="Apple-style-span" face="Courier">Research Associate Professor, GSLIS</font></div><div style="font-size: 12px; orphans: 2; widows: 2; margin: 0px;" class=""><font class="Apple-style-span" face="Courier">University of Illinois</font></div><div style="font-size: 12px; orphans: 2; widows: 2; margin: 0px;" class=""><font face="Courier" class="">(217) 244-8000</font></div><div style="orphans: 2; widows: 2; margin: 0px;" class=""><a href="mailto:d.katz@ieee.org" class="" target="_blank" style="font-family: Courier; font-size: 12px;">d.katz@ieee.org</a><span style="font-family: Courier; font-size: 12px;" class=""> or </span><font face="Courier" style="font-size: 12px;" class=""><a href="mailto:dskatz@illinois.edu" class="">dskatz@illinois.edu</a></font></div><div style="orphans: 2; widows: 2; margin: 0px;" class=""></div><div style="font-size: 12px; orphans: 2; widows: 2; margin: 0px; min-height: 14px;" class=""><a href="http://danielskatz.org/" style="font-family: Courier;" class="">http://danielskatz.org</a></div><div class=""><br class=""></div></div></div></div></div></div></div></div></div></div></div></div><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>