1 / 14

ECOOP WP2 overview “A community modelling framework”

ECOOP WP2 overview “A community modelling framework”. Jason Holt For Roger Proctor ECOOP Consensus and planning meeting 16-17 March 2005. Rational: exploiting diversity. There is a diversity of modelling approaches in existing systems: Solving the equations of motion

fathia
Télécharger la présentation

ECOOP WP2 overview “A community modelling framework”

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. ECOOP WP2 overview“A community modelling framework” Jason Holt For Roger Proctor ECOOP Consensus and planning meeting 16-17 March 2005

  2. Rational: exploiting diversity • There is a diversity of modelling approaches in existing systems: • Solving the equations of motion • Imposing forcing/boundary conditions • Representing the ecosystem, sediments…. • Data sources/Assimilation schemes • Infrastructure

  3. Hydrodynamic Components of a coastal-model • Free surface • Resolves the boundary layers • Turbulence closure for multiple boundary layers • Feature preserving advection • Surface fluxes and downwelling irradiation • Scale selective horizontal diffusion • Accurate horizontal pressure calculation with steep topography • Lateral boundary conditions/nesting • Coastal boundary condition - Flooding/drying • etc. just for hydrodynamics there many model systems: POM, ROMS, MOM, HAMSOM COHERENSE, GETM , POLCOMS….., often with extensive ‘local’ variations

  4. Why model diversity • No consensus on best practice • Lack of constraints and many arbitrary choices • Regional variation • Different processes dominant in different regions (but ideally this should be an emergent property) • Institutional expertise • Historical • Massive resource

  5. The Challenge • Develop a community framework of model systems that allows practical integration and exchange of • Model components (compatible with NEMO & MERSEA) • Scientific/technical developments • Define common model quality standards: • Accuracy • Solution • Conservation (mass, momentum, energy, vorticity…) • Observations • Stability • Efficiency

  6. The Benefits • Rapid knowledge transfer operational <-> research systems • Improved model systems • Shared best practice • Standards to direct/constrain development • Traceable model-model-data inter-comparison • Traceable multi-model ensemble simulations

  7. ECOOP WP2 AIMS AND OBJECTIVES • Design minimum threshold and standard for ECOOP Ver0 • Upgrade existing forecast systems to this standard • Establish standards for exchanging software and knowledge • Establish modelling and data assimilation code library • Establish library of key research priorities

  8. ECOOP WP2 Task 2.1 Design minimum threshold and standard for ECOOP Ver0 This task aims to establish the minimum modelling requirements to address each coastal region’s specific needs. It also will ensure that the standards and protocols adopted in ECOOP conform to, and are complementary to, the NEMO framework. Task 2.1.1 – evaluate complexity of physical/biogeochemical processes in each region Task 2.1.2 – evaluate modelling requirements to resolve this complexity, including assessment of computing requirements Task 2.1.3 – define minimum thresholds (and acceptable error) for accurate simulations Task 2.1.4 – determine the requirements for data assimilation and establish the appropriate methodology (dep. accuracy and frequency of datasets?) Task 2.1.5 – specify standards for ECOOP Ver0 to ensure compatibility with MERSEA NEMO framework Task 2.1.6 – establish forward look group to identify requirements for ECOOP Ver1

  9. ECOOPWP2 Task 2.2 Upgrade existing forecasting systems to reach the minimum threshold This module will identify where existing models are deficient and establish procedures for raising standards. It will also define the methodology for multi-model forecasts Task 2.2.1 – Examine existing forecasting systems and define error statistics Task 2.2.2 – Identify components of existing systems which fail acceptance criteria Task 2.2.3 – Implement upgrade procedure Task 2.2.4 – Design multi-model systems criteria and implementation methodology

  10. ECOOP WP2 Task 2.3 Standards for exchanging software and knowledge This module will identify the data requirements for inputs to models, including the exchange (initially one-way, subsequently two-way) between MERSEA regional models and ECOOP coastal models. It will establish the software standards required to ensure module compatibility between models. It will establish the output parameters and formats for model data to ensure consistency and compatibility between models. It will invoke a forum for exchange of ideas and knowledge on coastal processes and modelling techniques to ensure all ECOOP partners have the latest information on ECOOP models, and the latest developments in operational oceanographic models worldwide (interacts strongly with Task 2.6). It is also important for ECOOP to make use of the latest GRID and MIDDLEWARE technology and we will specifically investigate how this will best be utilised to link input, outputs and models (links to WP3 in particular). Task 2.3.1 – Identify exchange requirements between ECOOP modules and between ECOOP and MERSEA models Task 2.3.2 – Develop standards for process module exchange Task 2.3.3 – Develop protocol for ECOOP-MERSEA exchange (requirements for couplers e.g. PRISM) Task 2.3.4 – Develop protocol for ECOOP nesting exchange Task 2.3.5 – Develop protocol for ECOOP database access Task 2.3.6 – Establish knowledge transfer forum Task 2.3.7 – Establish transfer protocols for GRID exchange.

  11. ECOOP WP2 Task 2.4 A modelling and data assimilation library To construct and maintain the library of model modules and data assimilation routines required for implementation Task 2.4.1 – Establish online structure for library Task 2.4.2 – Construct library of modules and associated documentation Task 2.4.3 – Implement version control system and maintain library

  12. ECOOP WP2 Task 2.5 A library of key research priorities The purpose of this task is to identify the key research priorities for each domain and process (e.g. WFD requirements on eutrophication, nutrient status). Also to identify the modelling components which require the most urgent need of improvement to satisfy prescribed criteria. Outputs from Task 2.6 will contribute to this module. Task 2.5.1 – Establish online structure for library Task 2.5.2 – Construct library of priorities for domains and processes Task 2.5.3 – Construct library of priorities for model process improvements

  13. ECOOP WP2 Task 2.6 Expert groups, e.g., in physical, ecosystem, model coupling and data assimilation… To ensure that ECOOP has available the latest, state of the art information on all processes and their interactions in coastal seas and has the capability to model these processes in the most accurate and efficient manner. To ensure ECOOP is aware of, and understands, the necessary legislation and socio-economic considerations for forecasting and operational oceanography in coastal seas. The outputs of these groups are seen as fundamental in prioritising ECOOP developments. Task 2.6.1 – establish expert process groups in modelling physics, biogeochemistry including sediments, ecosystem processes, air-sea interaction; in modelling techniques of data assimilation, boundary conditions, coupling and nesting, data analysis, gis, socio-economic outputs. Task 2.6.2 – establish program of discussion group interaction and online structure for dissemination Task 2.6.3 – produce expert documents prioritising ECOOP requirements for ver0 and ver1

More Related