Common modeling infrastructure: Difference between revisions

Revision as of 03:31, 27 May 2009

Latest revision as of 11:26, 15 August 2021

(36 intermediate revisions by 15 users not shown)

Line 1:

'''Common modeling infrastructure''' refers to software libraries that can be shared across multiple institutions in order to increase software reuse and interoperability in complex modeling systems. Early initiatives were in the [[climate]] and [[weather]] ___domain, where [[software component]]s representing distinct physical domains (for example, [[ocean]] or [[atmosphere]]) tended to be developed by ___domain specialists, often at different organizations. In order to create complete applications, these needed to be combined together, withusing specialfor couplinginstance softwarea created[[general tocirculation transfermodel]], andthat transformtransfers data between thedifferent components. An additional challenge wasis that these models requiredgenerally require [[supercomputers]] to run, to account for the collected data and specializedfor softwaredata analyses. Thus, it was important to addressprovide routinean functionsefficient suchmassively asparallel I/Ocomputer system, paralleland datathe communicationsprocessing hardware and software, to account for all the different workloads and errorcommunication handlingchannels.<ref name=Dickinson02>{{cite journal

| author = Dickinson, R. E. |author2=S. E. Zebiak |author3=J. L. Anderson |author4=M. L. Blackmon |author5=C. DeLuca |author6=T. F. Hogan |author7=M. Iredell |author8=M. Ji |author9=R. B. Rood |author10=M. J. Suarez |author11=K. E. Taylor

| year = 2002

In this context, the incentives for common modeling infrastructure included:

| title = How Can We Advance Our Climate and Weather Models as a Community?

* the need for physical consistency across components, such as using the same physical constants and [[calendar]]s

| journal = Bulletin of the American Meteorological Society

* the need for clear, standard [[software interface]]s so components could be exchanged and introduced easily

| volume = 83

* the desire to create systems in which the components of complex models were separable, so that [[controlled experiment]]s could be performed in which only specific components were changed

| pages = 431–434

* the desire to share as many of the libraries handling non-scientific modeling functions as possible

| doi = 10.1175/1520-0477(2002)083<0431:hcwaow>2.3.co;2

| url =http://climateknowledge.org/openclimate/docref/Dickinson_Community_Software_BAMS_2002.pdf

}}</ref>

==General ==

In the late 1990s and early 2000s, a series of journal papers and government reports described common modeling infrastructure as necessary to the competitiveness and evolution of the U.S. Earth science modeling community. These reports resulted in a number of new community projects. The Earth System Modeling Framework ([[ESMF]]) in the U.S. and the PRogramme for Integrated Earth System Modeling (PRISM) in Europe were the two largest. Similar projects were initiated in related domains, including the Space Weather Modeling Framework and the Center for Integrated Space Weather Modeling in the [[space weather]] community.

Common modeling infrastructure projects include the Network Common Data Form ([[NetCDF]]) library, the Spherical Coordinate Remapping and Interpolation Package (SCRIP), the Flexible Modeling System (FMS),<ref>{{cite web|url=http://www.gfdl.noaa.gov/fms|title=Flexible Modeling System (GFDL)}}</ref> the OASIS coupler developed at CERFACS, and the multi-agency Earth System Modeling Framework ([[ESMF]]).

The [[Earth System Modeling Framework]] (ESMF) is considered a technical layer, integrated into a common modeling infrastructure. Other aspects of interoperability and shared infrastructure include: common experimental protocols, common analytic methods, common documentation standards for data and data [[provenance]], shared workflow, and shared model components.<ref>{{cite web|url=http://cpo.noaa.gov/sites/cpo/MAPP/Webinars/2014/03-31-14/Balaji.pdf|title=Scientific Basis for Common Infrastructure|author=NOAA/CPO MAPP|date=March 31, 2014|page=15}}</ref>

== History ==

In the late 1990s and early 2000s, a series of journal papers and government reports described common modeling infrastructure as necessary to the competitiveness and evolution of the U.S. Earth science modeling community. These reports resulted in a number of new community projects. The [http://www.earthsystemmodeling.org/ Earth System Modeling Framework] ([[ESMF]]) inand the U[http://science.Senergy. and the PRogramme for Integratedgov/ber/research/cesd/earth-system-modeling-program/ Earth System Modeling] (PRISMESM) inare Europetwo wereof the twolargest largestmodeling approaches. Similar projects were initiated in related domains, including the [http://csem.engin.umich.edu/tools/swmf/ Space Weather Modeling Framework] and(SWMF/CESM), to study conditions including the CenterSun, forsolar Integratedwind, Spacemagnetosphere, Weatherionosphere, Modelingand inthermosphere thethat potentially can influence performance and reliability of [[space-borne weather]]and ground-based technological systems or can endanger human life or communityhealth.

== See also ==

* [[Climate model]]

* [[Earth System Modeling Framework]]

==References==

{{reflist|30em}}

{{Atmospheric, Oceanographic and Climate Models}}

{{Computer modeling}}

[[Category:Computer libraries]]

* Dickinson, R.E., S. E. Zebiak, J. L. Anderson, M. L. Blackmon, C. DeLuca, Timothy F. Hogan, Mark Iredell, Ming Ji, Ricky B. Rood, Max J. Suarez, and Karl E. Taylor, "How Can We Advance Our Climate and Weather Models as a Community?", Bulletin of the American Meteorological Society, 2002, pp. 431-434.

[[Category:Numerical climate and weather models]]

{{uncategorized|date=May 2009}}