The PRISM Support Initiative (PSI): scope and structure
description
Transcript of The PRISM Support Initiative (PSI): scope and structure
1
The PRISM Support Initiative (PSI):scope and structure
Version summer 2005
Eric Guilyardi
LSCE/CNRS & CGAM/Reading
2
PRISM concept
Share the development, maintenance and support of an
Earth System Modelling software environment
• ease everyday life of climate scientists• provide latest technology, practice• ease procurements, optimization of codes
• hence reduce related personnel/computing costs for institutes
• no climate science issues, no hardware issues (ENES)• no management of CPU/model/data access services
3
a) PRISM software infrastructure (“tool box”):
1. standard coupler and I/O software, OASIS3, OASIS42. standard compiling environment (SCE) at the scripting level3. standard running environment (SRE) at the scripting level4. Graphical User Interfaces (GUIs) to SCE and SRE5. GUI for an end-to-end monitoring of climate experiments6. standard diagnostic and visualisation tools
b) Demonstration:
1. 12+ model components adapted to PRISM standards (PSMILe interface, SCE, SRE, GUI), 15+ coupled combinations as demos
2. PRISM SCE and SRE are configured for 9 European sites 3. GUIs installed in two sites (MPI, ECMWF)
c) A well coordinated network of experts
PRISM FP5 project achievements
4
Infrastructure = long term commitment
How to organise sustainability ?
1. EU not really helpful (requires already existing sustainability)
2. Earth system modelling institutes and partners: requires coordination
PRISM project has shown that solution 2 can work (as a distributed team of experts)
Community launch of “PRISM sustained team”, Paris 27/10/04
5
PRISM community
1.
Community
Associate Partners
Partners
Associate PartnersAny Institution, Centre or Vendor who contributes effort coordinated by the PRISM Support Initiative (PSI)
PartnersContribute significant effort coordinated by the PSI (+0.5 py/y)Constitute the PSI Steering Board
6
PSI structure
PRISM Team
from Partners and Associate Partners
Invited Technical Advisors
PSI Technical Coordinator
High levelrequirements
PRISM User Group
PUG Chair
PSI Steering Board (ownership of process)
PSI-SB Chair
- SD Process -Standards Definition and
Technical Decision Making Process
Report
Request for changes to or new standards
Has final decision
Organise
Provide technical Requirements
Set directions
PSI Management Coordinator
Support
Coordination
7
PSI Steering Board role
• Coordinate and provide effort to fulfil (in priority order): 1. Software maintenance and service support, 2. Support for adaptation of models to PRISM, 3. Development against current requirements of adapted models,4. Development against future requirements.
• Further sub-divided to meet the needs of (in priority order):• Partners• The Associates Partners• The Community
1. To help resolve disagreements (technical or structural)
Initial members: Met Office, Model & Data, CNRS, NEC-CCRLE, CERFACS, ECMWF
8
PRISM Team tasks
• PT technical coordination (Lead: S. Valcke, CERFACS):• PT coordination, system integration• System specifications based on PUG requirements • Organise work of Standards definition process• Technical audit coordination
• PRISM software technical developments • Coupler (Lead: S. Valcke, CERFACS)• SCE/SRE (Lead: S. Legutke, M&D)• GUI (Lead: C. Larsson & N. Wedi, ECMWF)• Versioning control / CM (Lead: M. Carter, Met Office )• Diags and visualisation (Lead: J. Wegner, M&D)• Data management (Lead: M. Lautenschalger, M&D)
9
• Support to PSI-SB activities• Coordinattion of non-technical activities such as:
• General PSI coordination• Coordination of bids for external funding• Community outreach & coordination, relations with other projects (ESMF, FLUME, etc)• PSI internal services (WEB, collaborative tools, …)
PRISM User Group (PUG)
PRISM Management Coordinator(E. Guilyardi, CNRS)
(Chair: R. Budich, MPI-M)
• Open to all• Organise capture of community requirements:
• changes to or new standards and interface definitions• additional features to PRISM software (e.g. data assimilation,…)
• Participation in system specifications• Community audit
10
PSI next milestones
• Organise first SB meeting to endorse proposals• Establish 3 years detailed work plan • Organise technical and community audits