1 / 16

Workshop Charge

Workshop Charge. J.C. Wells & M. Sato Park Vista Hotel Gatlinburg, Tennessee September 5-6, 2014. Workshop motivation.

Télécharger la présentation

Workshop Charge

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Workshop Charge J.C. Wells & M. Sato Park Vista Hotel Gatlinburg, Tennessee September 5-6, 2014

  2. Workshop motivation We believe the workshop can play a seminal role in understanding the issues and possible collaborative opportunities between Japan and US for application co-design for exascale computing systems.

  3. Major Workshop Goals & Outcomes • The outcome of this workshop is a list of computational science challenges around which Japan and the US may form collaborative, exascaleco-design research partnerships. • Solving these problems should have the potential to transform our understanding of science and its impacts and to improve our ability to apply knowledge in important applications. • This list should include challenge problems in the selected focus areas. • Life science, drug design, health science data • Materials by design • Global change prediction for disaster prevention & mitigation • Computational engineering • Fundamental nuclear science • Fusion energy sciences • Research outcomes should advance exascale co-design goals, that is, inform the architectural design of extreme-scale application software and the computing systems on which these applications run.

  4. Co-Design, from Wikipedia http://en.wikipedia.org/wiki/Co-design Co-design or codesign(CD) is a design process where professionals encourage, and guide users to develop solutions for themselves. CD is a development of systems thinking, which "begins when first you view the world through the eyes of another.” CD in the different research fields is tightly connected to the conception or creation of artifacts in communities context through a shared vision, social learning and mutual understanding among all key stakeholders… The phrase co-design is also used in reference to the simultaneous development of interrelated software and hardware systems.

  5. Difference of co-design between HPC andembedded apps, for example • In embedded field, co-design sometimes, includes "specialization" for a particular applications. • On the other hands, in HPC, the system will be shared by many applications. • The co-design of HPC must optimize and maximize thebenefits to cover many applications as possible. • Acknowledgment to Prof. M. Sato

  6. How to approach your breakout session? • The priority should be placed on identifying complementary, mutually beneficial science and engineering problems and research themes on which we can work together over the long term. • Also, make clear what software and hardware elements are important for co-design in each topical application area. • The elements may include cache (size and bandwidth), network (latency and bandwidth), memory technologies, (e.g., high-bandwidth or hybrid memory cube), some specialized hardware, etc. • They also may include programming and runtime environments, and libraries

  7. Overarching Questions (especially for Executive Breakout) • How shall we build sustainable, multidisciplinary teams and research collaborations, including vendor partners, necessary to achieve our workshop goals? • What are the appropriate collaborative agreements and organization to enable Japan and the US collaborate on exascale science application development in a mutually beneficial way? • How are we going to maintain these collaborations over time?

  8. Breakout Charge Questions: • Intend for each breakout to answer the following questions to identify and advance a domain-specific co-design agenda. • Identify questions to which the for co-design breakout members can contribute • Designate computer scientists from this group to participate with the 6 domain-science breakouts to assist in answering the questions and planning for a co-design research agenda.

  9. Breakout Charge Questions, continued • What technical breakthroughs in science and engineering research can be enabled by exascale platforms and are attractive targets for Japan-US collaboration over the next 10 years? • Please prioritize discussions around opportunities for collaborative Japan-US R&D relationships.

  10. Breakout Charge Questions, continued • What is the representative suite of applications in your research area, available today, which should form the basis of your co-design communication with computer architects? • How are these applications currently constrained by compute and data resources, programming models, or available software tools? • What are the gaps in available applications and application workflows, and requirements to fill these gaps? • Which of these are ripe for collaboration within the context of Japan-US cooperation?

  11. Breakout Charge Questions, continued • How can the application research community, represented by a topical breakout at this workshop, constructively engage the vendor community in co-design? • How should these various aspects of the application and architecture be optimized for effective utilization of exascale compute and data resources? • Consider all aspects of exascale application: formulation and basic algorithms, programming models & environments, data analysis and management, hardware characteristics.

  12. Breakout Charge Questions, continued • How can you best manage the “conversations” with computer designers/architects around co-design such that (1) they are practical for computer design, and (2) the results are correctly interpreted within both communities? • What are the useful performance benchmarks from the perspective of your domain? • Are mini-apps an appropriate and/or feasible approach to capture your needs for communication to the computer designers? • Are there examples of important full applications that are an essential basis for communication with computer designers? • Can these be simplified into skeleton apps or mini-apps to simplify and streamline the co-design conversation

  13. Breakout Charge Questions, continued • Describe the most important programming models and environment in use today within your community and characterize these as sustainable or unsustainable. • Do you have appropriate methods and models to expose application parallelism in a high-performance, portable manner? • Are best practices in software engineering often or seldom applied? • Going forward, what are the critically important programming languages? • On which libraries and/or domain-specific languages (DSL) is your research community dependent? • Are new libraries or DSL’s needed in your research domain? • Are these aspects of your programming environment sustainable or are new models needed to ensure their availability into the future?

  14. Breakout Charge Questions, continued • Does your community have mature workflow tools that are implemented within leadership computing environments to assist with program composition, execution, analysis, and archival of results? If no, what are your needs and is their opportunity for value added? • For example, do you need support for real-time, interactive workflows to enable integration with real-time data flows?

  15. Breakout Charge Questions, continued • What are the new programming models, environments and tools that need to be developed to achieve our science goals with sustainable application software?

  16. Breakout Charge Questions, continued Is there a history, a track record in your research community for co-design for HPC systems in the installed machines in the past, and is there any co-design study done for these systems to document the effectiveness of co-design?

More Related