Content deleted Content added
m cat |
|||
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, with special coupling software created to transfer and transform data between the components. An additional challenge was that these models required [[supercomputers]] to run, and specialized software to address routine functions such as I/O, parallel data communications, and error handling.
In this context, the incentives for common modeling infrastructure included:
Line 12:
* 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:Computer libraries]]
|