Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed Martin Company, for the United States Department of Energy's National Nuclear Security Administration under Contract DE-AC04-94AL85000.

CSRI Overview

Computer Science Research Institute Goals: –Collaborative computer science research –Strong Sandia participating in research community –Impact on national security problems –Recruiting Activities –Collaborative projects –Student and faculty programs –Workshops A “co-laboratory” for computer science research

CSRI Leaders David Womble (1410), Director, CSRI S. Scott Collis (1414), Executive Manager, CSRI Executive Board: –Heidi Ammerlahn (8962) –Neil Pundit (1423) –Martin Pilch (1221) –Prof. Danny Sorensen, Comput’l & Applied Math, Rice University –Prof. Deepak Kapur, Chairman Comp. Sci., UNM Deanna Ceballos, CSRI Administrator Bernadette Watts, CSRI Administrator

Opportunities for Collaborations Faculty sabbaticals lasting between a semester and a year, Summer faculty positions, Graduate fellowships through the NPSC and HPCS (Krell Institute) programs, Summer student positions, Technical visits of lengths between one week and three months, Post-doctoral positions lasting up to two years, Conference sponsorships, A CSRI colloquium series, Visits by laboratory staff to universities.

Thanks CSRI: –David Womble, Scott Collis. –Deanna Ceballos, Bernadette Watts Organizing: –Doug Kothe, Trey White, Ricky Kendall –Doug Doerfler, Carter Edwards, Alan Williams.

Workshop Overview

Background & Motivation MPI-only: –Present: Foundation for scalable applications. –Future: Part of the answer, but not the whole? Why not the whole: –Near-term: Multicore nodes: homo/heterogeneous. MPI+something, but what? –Long-term: Near-term + Core types, counts and organization. Memory organization. New programming models. Bottom line: How do we develop next-generation scalable applications?

Workshop Goals 1.Understand the limitations of MPI as the scalable API for future applications. 2.Identify complementary approaches or replacements, and discuss strategies for transitioning. 3.Identify algorithmic challenges and directions to enable scalable applications.

Subgroups Four subgroups: –Applications. –Libraries. –Programming Environments. –Architectures. Each subgroup has: –Lead –Liaison from each of the other three subgroups. Responsibilities are: –Lead: Lead subgroup discussion, assign writers/presenters, bring subgroup to consensus. –Liaison: Act as liaison to subgroup in case questions arise.

Subgroup Assignments AppsLibsProg EnvsArchitectures Lead D. KotheJ. DongarraR. KendallK. Underwood Apps Liaison A. RobinsonH. EdwardsD. Bader Libraries Liaison M. KnepleyR. VuducG. Henry Prog Envs Liaison S. DietzR. NumrichD. Norton Arch Liaison A. RodriguesK. PedrettiS. Hemmert All others self-assign to subgroups

Key Questions: Scrum-inspired Scrum and XP from the trenches, Henrik Kniberg

39 Questions Sent by this morning. Broken down by workshop goal, and others. In subgroups vote on –Priority: Which are most important to your subgroup. Which should be answered by other subgroups (next round). What additional questions should be added. –Choice: Pick number of questions you think you can answer in allotted time. Adjust number, as needed, next time.

Workshop Objectives Goals Understand the limitations of MPI as the scalable API for future applications. Identify complementary approaches or replacements, and discuss strategies for transitioning. Identify algorithmic challenges and directions to enable scalable applications. Address workshop goals as best we can via key questions. –As questions resolve, assign writers (majority, minority as needed). –As issues are identified as outside workshop scope, assign writer. Your questions get answered, or issues clarified. Product: Final workshop report for wide dissemination. Ultimate: See paths to next-generation scalable apps.

Miscellaneous Workshop atmosphere: –Structure intended to stimulate conversation. –Not stifle it. –Flexibility is possible. Introductions…