Presentation is loading. Please wait.

Presentation is loading. Please wait.

SWIM Meeting, Tech-X, October 2010 The Fusion Simulation Program presented at the SWIM meeting on October 28, 2010 JR Cary Tech-X on behalf of the FSP.

Similar presentations


Presentation on theme: "SWIM Meeting, Tech-X, October 2010 The Fusion Simulation Program presented at the SWIM meeting on October 28, 2010 JR Cary Tech-X on behalf of the FSP."— Presentation transcript:

1 SWIM Meeting, Tech-X, October 2010 The Fusion Simulation Program presented at the SWIM meeting on October 28, 2010 JR Cary Tech-X on behalf of the FSP Team Terminology The Fusion Simulation Program is expected to start in FY12 We are currently in the FSP Definition Project What will FSP be? How will it be run?

2 SWIM Meeting, Tech-X, October 2010 The purpose of this meeting is to ●Provide a status report for the FSP Definition Project, which is about 2/3 through its two-year life ●Engage the community for feedback ●Most information can be found starting from www.pppl.gov/fsp.

3 SWIM Meeting, Tech-X, October 2010 Where for information? ●Input welcome, a purpose of this meeting ●FAQ: http://www.pppl.gov/fsp/FAQS/FSP_FAQ_Jan8 _2010.pdf ●Science Drivers: http://fspscidri.web.lehigh.edu/index.php/Main_ Page ●Components http://fspcomp.web.lehigh.edu/index.php/Main_ Page ●Frameworks: https://ice.txcorp.com/trac/fspfrmwrkplan/wiki ●Validation: http://www.psfc.mit.edu/FSP- Validation/index.php/Main_Page

4 SWIM Meeting, Tech-X, October 2010 Where do you go with questions? ●FSP PLANNING TEAM: *W. Tang (PPPL/PU). D. Batchelor (ORNL), H. Berk (IFS), J. Brooks (Purdue U.), J. Cary (Tech-X/U. Colorado), V. Chan (GA), C.S. Chang (NYU), P. Colella (LBNL), L. Diachin (LLNL), P. Diamond (UCSD), M. Greenwald (MIT), D. Keyes (Columbia U.), D. Kothe (ORNL), A. Kritz (Lehigh U.), W. Nevins (LLNL), A. Siegel (ANL/U.Chicago), X. Tang (LANL), G. Tynan (UCSD) ●FSP MANAGEMENT TEAM: Director (W. Tang, PPPL), Deputy Director for Plasma Science (M. Greenwald, MIT), Deputy Director for Advanced Computing (D. Kothe, ORNL) ● Science Drivers (Lead, A. Kritz, Lehigh U.) with Supporting Team ● Frameworks/Physics Integration (Lead, J. Cary, Tech-X) with Supporting Team ● Experimental Validation (Lead, M. Greenwald, MIT, co-Lead, V. Chan, GA) with Supporting Team ● Advanced Physics Modules (Lead, X. Tang, LANL, Verification Lead, L. Diachin, LLNL) with Supporting Team ● Project Management (D. Hudson, ORNL, R.Strykowsky, PPPL)

5 SWIM Meeting, Tech-X, October 2010 The FSP is envisioned to go for 15 years, so needs ●Planning ●Management ●Governance ●Continuation with members coming and going

6 SWIM Meeting, Tech-X, October 2010 Our place in the time line ●PAC review (Sep 10) highly favorable ●Science driver reports in ● http://fspscidri.web.lehigh.edu/index.php/Main_Page (final reports) ●Next step: comment, improve, prioritize. Management team to start discussing in November. ●Possible management plans presented to PAC ●Next steps:  Comment, improve  Select persons for management positions  Present to community (Feb 7-11)  Select IA heads and teams

7 SWIM Meeting, Tech-X, October 2010 Current view of responsibilities Software Integration Integ Science Apps Software and tools Workflow tools On-HPC integration Advanced components Quality Assurance Operational Support Developer support User support Systems support? Testing Validators UQ, methodologies QA, OS support all other areas and users. Decisions which boxes have technical managers? How large are the teams? Does there need to be an IA head? Core Profiles Wave -Particle Interactions Boundary Layer Pedestal Whole Device Modeling Disruptions Science Drivers Dep Dir for Architecture Dep Dir for Physics Director IA 1 IA 2 IA 3

8 SWIM Meeting, Tech-X, October 2010 First assignments Software Integration Integ Science Apps Software and tools Workflow tools On-HPC integration Advanced components Quality Assurance Operational Support Developer support User support Systems support? Testing Validators UQ, methodologies QA, OS support all other areas and users. Decisions which boxes have technical managers? How large are the teams? Does there need to be an IA head? Core Profiles Wave -Particle Interactions Boundary Layer Pedestal Whole Device Modeling Disruptions Science Drivers Dep Dir for Architecture Dep Dir for Physics Director IA 1 IA 2 IA 3 Filling by Jan

9 SWIM Meeting, Tech-X, October 2010 Presentation to Community, Feb 7-11 ●Working out what we want out of this ●Informative of decisions to date ●Notification of openings for IA heads and teams ●What else?

10 SWIM Meeting, Tech-X, October 2010 Integrated application team heads/teams selected in March/April ●Proposals to FSP Definition Team ●Evaluation based on  Credibility to deliver on Science Driver  Team making use of those in community

11 SWIM Meeting, Tech-X, October 2010 Must be a balance between early deliverables and common infrastructure ●Further development of common infrastructure goes under DD for Architecture (examples: monitoring, tools) ●IA teams should bring to the party whatever they need for early deliverables ●As FSP proceeds, Integration should be pulling out commonly useful software from ISAs and providing it in generally useful form

12 SWIM Meeting, Tech-X, October 2010 How will Software Integration work with other teams? ●Short term success will be made by modifying existing community software to address science drivers. This is likely to be less invasive on legacy software and more one-offs. ●Software integration liaisons will study the efforts, extract common tools, and make them more broadly applicable and available ●Software Integration will also be identifying and developing tools for tighter couplings, such as common data structures ●All of this will be maintained for public download

13 SWIM Meeting, Tech-X, October 2010 Development of robust, integrated apps on long term will require continuous interaction Software Integration Integ Science Apps Software and tools Workflow tools On-HPC integration Integration ideas flow from integrated apps to the Integration team Integration team creates robust, reusable integration software Advanced components

14 SWIM Meeting, Tech-X, October 2010 Timeline for all teams User support Developer support Quality assurance 20122014 Mission refine, hiring Maintenance System support? Integrated Science Application 1 Integrated Science Application 2 Integrated Science Application 3 First release Software integration First release (ext tools, viz, …) Tightly integrated app release Second release (tight coupling infrastructure) 2016 2019

15 SWIM Meeting, Tech-X, October 2010 Charge 1)FSP Science Goals -- Regarding the current set of science drivers and associated science program plans, please comment on the current vision and plans for: a)development of the integrated software products that flow from the science goals in the nearer-term (<5 years) and the longer term time frames (5-15 years); In the first five years, integrated software products will come from stripped, augmented, and reorg'd protoFSPs. After first release of tight-integration products, new integrated applications will come from refactoring to make use of common infrastructure b)prioritizing and scheduling the program elements identified in the individual science program plans; and c)the cross-disciplinary engagement of communities representing FES theory/computations & experiments and ASCR computer science and applied math. New integration products will make heavy use of AppMath libs and development will be with joint teams involving ASCR personnel.

16 SWIM Meeting, Tech-X, October 2010 END


Download ppt "SWIM Meeting, Tech-X, October 2010 The Fusion Simulation Program presented at the SWIM meeting on October 28, 2010 JR Cary Tech-X on behalf of the FSP."

Similar presentations


Ads by Google