About ESMF Download Users Developers Management Work Plans Metrics Impacts

INTEGRATION OF EARTH AND SPACE FRAMEWORKS

Back to Projects

The space science and Earth science communities are engaged in a dialogue on how to develop interfaces that will allow emerging community frameworks - the Space Weather Modeling Framework (SWMF), the tools being used by the Center for Integrated Space Weather Modeling (CISM), and ESMF - to interoperate. This page includes materials from two initiatives.

Publications and Talks

Killeen, T., C. DeLuca, T. Gombosi, G. Toth, Q. Stout, C. Goodrich, A. Sussman, and M. Hesse, 2006: Integrated Frameworks for Earth and Space Weather Simulation. Preprint presented at the American Meteorological Society Meeting, Atlanta, GA, January 29-February 2, 2006. (Download PowerPoint file)

SWMF and ESMF

Sponsor: NSF

Abstract: We will integrate SWMF with ESMF and will make it possible to run SWMF as a stand-alone tool or as an ESMF component that provides input for Earth system models (such as cloud formation), or simply can be run through ESMF. We will provide a modest extension to the ESMF system that will simplify the SWMF/ESMF coupling, and will help to define a paradigm for future collaboration between the two projects.

The specific tasks are the following:

Developer files

CISM and ESMF

Sponsor: NASA

Abstract: We will explore the addition of a multiple executable, put/get data transfer paradigm to the ESMF framework using the CISM InterComm tool. The goals will be to create coupling interface for ESMF and CISM components, and to add flexibility to the ESMF framework. We plan to use InterComm to execute the inter-component data transfers, but to allow ESMF components to do this through interfaces that are ESMF-defined, and accept ESMF_State data structures.

Currently the ESMF framework is limited to coupling components by passing ESMF_State types through component argument lists. There are a number of situations in which this approach poses problems. The first case occurs when the changes made to a component version to run within a framework must be kept to an absolute minimum. The put/get paradigm generally involves changing fewer lines of code within the component version itself. The second case occurs when a coupling must be executed without returning control from the components involved.

In this demonstration, the specific tasks are: