PRISM overview: from the FP5 project to a sustained effort

1. PRISM overview: from the FP5 project to a sustained effort • Scope and drivers • PRISM project: achievements and assessment • The PRISM sustained initiative (PSI) • The future ENES Meeting, Vienna, 2 April 2006 Eric Guilyardi IPSL/CNRS & CGAM Sophie Valcke CERFACS

2. Why a common software framework ? • Earth system modelling expertise widely distributed Geographically Thematically

3. Why a common software framework ? • Earth system modelling expertise widely distributed • Scientific motivation = facilitate sharing of scientific expertise and of models • Technical motivation = the technical challenges are large compared with available effort • Need to keep scientific diversity while increasing efficiency – scientific and technical • Need to coordinate with initiatives elsewhere: • The Earth System Modelling Framework, US • FLUME, GENIE, FMS,... • GO-ESSP, PCMDI

4. PRISM concepts PRISM is at interface between ES science needs and IT best practice • Share Earth System Modelling software framework across community • To bring experts together to: • share development, maintenance and support • aid performance on a variety of platforms • standardize model software environment • ease use of different climate model components

5. Benefits • High performance ESM software, developed by dedicated IT experts, available to institutes/teams at low cost: - helps scientists to focus on science - helps key scientific diversity (survival of smaller groups) • Easier toassemble ESMs based on community models • Shared software = increased scientific exchanges (AR4!) • Computer manufacturers inclined to contribute: - efficiency (porting, optimisation) on variety of platforms - next generation platforms optimized for ESM needs - easier procurements and benchmarking - reduced computing costs

6. Software framework of an Earth System Model Coupling & I/O layer Perl, ksh, python,.... Scientific core Where diversity is needed Supporting software Script tool F90, C = sources(ESM code, script tools) and processes

7. Using the software framework of an ESM Developer User Specific source + ancillary Binary exec Job flow Atmos. Ocean Land Coupler Metadata standards Running Configure ESM Compilation Analysis Visualisation Archiving Source/version control // library PMIOD Standard processes netCDF/CF = sources (ESM code, script tools) and processes Reference source

8. The long term view Towards standard ESM support library(ies) Tomorrow Today Climate science work multi-model, MIPs,... Earth System model (Science) Modeller Earth System model (Science + script tools + environment) Standard support Library IT expert Fortran Compiler Fortran Compiler Hardware Hardware

9. The PRISM FP5 project

10. The PRISM project • Program for integrated Earth System Modelling • 22 partners • 3 Years, from Dec 2001 - Nov 2004 • 5 Mill. € funding, FP5 of the EC (~80 py) • Coordinators: G. Brasseur and G. Komen

11. System specifications The modelers/users: - requirements - beta testing - feedback The science : - General principles - Constraints from physical interfaces,… PRISM The technical developments: The community models - Coupler and I/O - Compile/run environment - GUI - Visualisation and diagnostics - Atmosphere - Atmos. Chemistry - Ocean - Ocean biogeochemistry - Sea-ice - Land surface - … Let’s NOT re-invent the wheel !

12. System specifications - the people Reinhard Budich - MPI, Hamburg Andrea Carril - INGV, Bologna Mick Carter - Hadley Center, Exeter Patrice Constanza - MPI/M&D, Hamburg Jérome Cuny - UCL, Louvain-la-Neuve Damien Declat - CERFACS, Toulouse Ralf Döscher - SMHI, Stockholm Thierry Fichefet - UCL, Louvain-la-Neuve Marie-Alice Foujols - IPSL, Paris Veronika Gayler - MPI/M&D, Hamburg Eric Guilyardi - CGAM, Reading and IPSL Rosalyn Hatcher - Hadley Center, Exeter Miles Kastowsky ­ MPI/BCG, Iena Luis Kornblueh - MPI, Hamburg Claes Larsson - ECMWF, Reading Stefanie Legutke - MPI/M&D, Hamburg Corinne Le Quéré - MPI/BCG, Iena Angelo Mangili - CSCS, Zurich Anne de Montety - UCL, Louvain-la-Neuve Serge Planton - Météo-France, Toulouse Jan Polcher - LMD/IPSL, Paris René Redler, NEC CCRLE, Sankt Augustin Martin Stendel - DMI, Copenhagen Sophie Valcke - CERFACS, Toulouse Peter van Velthoven - KNMI, De Bilt Reiner Vogelsang - SGI, Grasbrunn Nils Wedi - ECMWF, Reading

13. PRISM project achievements: • Prototype software environment: a standard coupler and I/O software, OASIS3 (CERFACS) and OASIS4 a standard compiling environment (SCE) at the scripting level a standard running environment (SRE) at the scripting level a Graphical User Interface (GUI) to the SCE (PrepIFS, ECMWF) a GUI to the SRE for monitoring the coupled model run (SMS, ECMWF) standard diagnostic and visualisation tools • Adaptation of community Earth System component models (GCMs) and demonstration coupled configurations • A well co-ordinated network of expertise • Community buy-in and trust-building

14. Community collaborations Active collaborations: • ESMF(supporting software, PMIOD, MOM4) • FLUME(PRISM software) • PCMDI (visualisation, PMIOD) • CF group (CF names) • NERC (BADC & CGAM) (meta-data, PMIOD) • ... PRISM has put Europe in the loop for community-wide convergence on basic standards in ES modelling Earth System modelling framework recognised as core activity of WCRP's newly established Modelling Panel (WMP)

15. 1. Sustainability 2. Review of specifications/user needs PRISM sustained initiative PRISM user survey Post-FP5 project steps (done in 2005):

16. PRISM community meeting 2005 CERFACS, Toulouse, 17-18 Nov 2005 Inform community of PRISM team activities (Session 1) Review community use (User Survey – 19/22 inst.) (Session 2) Define ES science needs/priorities (Session 3) Capture suggestions/ideas on organisation of PSI (Session 4) • Outcome: • Set up User Group • Launched metadata standards activity • Proposed strategy and work plan to PRISM Steering Board and community

17. PSI role (from US05 and CM05) • organise and promotesoftware tool development, sharing, maintenance and support (not only FP5 tools); • organise forums of discussion and collaborations in the community to solve common technical problems; • define and promote community standards (and in particular meta-data standards) where needed (BUT experience shows that successful standards emerge and are not enforced); • be Earth System Modelling (ESM) science driven but not to do or coordinate ESM science; • be a visible entry point of the European ESM software infrastructure community for international coordination (WCRP, EU projects, Japan -Earth Simulator, US –ESMF, …); • coordinate associated funding.

18. Need for meta-data standards • Model meta-data (basic meta-data, needed for model intercomparison) • outputs (CF +CMOR-like library, file names,…), model description, grids, … • Coupling+I/O layermeta-data • component coupling+I/O description (PMIOD,...) • Process meta-data • Source control, model configuration, compiling,... • Discussion at community level

19. PRISM Sustained Initiative (PSI) = Organisational structure of PRISM

20. PRISM areas of expertise • Previous analysis has shown that: • Networking activities are a prerequisite to community tool development • The PSI structure should not be FP5 tools focused • Contribution from groups outside PRISM can be valuable (“best of breed” approach) • Hence, PSI is now organised around a few “PRISM areas of expertise” (PAEs)design to foster exchanges and development in key areas

21. PRISM areas of expertise (PAE) • Five PAE: • Code coupling and I/O (S. Valcke, CERFACS) • Integration and modelling environments (M. Carter, Met Office) • Data processing, visualisation and management (M. Lautenschlager MPI-M/M&D) • Meta-data (cross-cutting PAE) (L. Steeman-Clarck, CGAM) • Computing issues (cross-cutting PAE) (R. Redler, CCRLE & M-A Foujols, IPSL) • Remits of each PAE: • Encourage/organise network of experts & technol. watch • Promote and coordinate related tools & beta testing • Coordinate with other PAEs and international activities

22. PSI structure

23. PSI partners • 7 Partnerscontribute significant effort, form the PSI Steering Board CERFACS, CGAM, CNRS, ECMWF, Met Office, MPI-M&D, NEC-CCRLE Associate Partners: CRAY, MPI-M, NEC, SGI, SMHI, SUN, (IBM) • PRISM Steering Board (PSB): • reviews annually PRISM activities and defines priorities • helps promote PRISM and organise funding

24. The PRISM Core Group • PRISM core group (PCG): • General coordination of PRISM activities • Coordination of common funding activities • External representation • Composed of: • General coordinator(s) • PAE leaders and other proposed members • PUG leader • One rep. per major institute involved in PAEs • PCG 2006: • E. Guilyardi(CNRS, co-coord.),S. Valcke(CERFACS, co-coord.),R. Budich(MPI-M),M. Carter(UK Met Office),M-A Foujols(IPSL),M. Lautenschlager(MPI-M&D),R. Redler(NEC-CCRLE),L. Steenman-Clark(CGAM),N. Wedi(ECMWF)

25. Funding • Networking activities(small and long term) • Communication (meetings, web, teleconferences, visits...) • PAE networking and User Group support • Source: • long term support: EU FP7 (post-ENSEMBLES IP, ERA-net) • Developments activities(larger and project type) • First identify what is needed within PAEs • Source: • National/institute funding when local interest joins community goals • Coordinated EU FP7 (infrastructure, post-ENSEMBLES IP,...)

26. Summary • PRISM FP5 project legacy ensured via the PSI • Organise and promote shared software tool development • Encourage and organise network of experts & technology watch • Coordinate related European contribution to internationalprojects • Strong institutional involvement and support • PRISM areas of expertise • Code coupling and I/O • Integration and modelling environments • Data processing, visualisation and management • Meta-data • Computing issues • WCRP Modelling Panel (WMP) endorsement • Funding: prepare for FP7

27. Thank you

28. PRISM project developments SCE SRE Analyis Visu Atmos. Ocean Land Coupler Configure ESM Running Compilation Analysis Visualisation Archiving Source/version control to SCE/SRE & PMIOD PMIOD Standard API, GUI netCDF/CF Script tools: Reference source Binary exec Job flow Specific source Process: