Configuration Management and Version Control in Earth System Modelling

Chapter
Part of the SpringerBriefs in Earth System Sciences book series (BRIEFSEARTHSYST)

Abstract

This section discusses the process of developing and constructing Earth System Models (ESMs). The construction of an ESM is fundamentally an action of configuration management (CM), the process of handling change in software systems which may be large and complex. Essentially, configuration management involves identifying, at a level suitable for management, the components of a software system, controlling changes to components over time (i.e. version control), providing traceability of changes made and supporting the maintenance of auditable versions of the software system. Configuration management typically uses the language of trunks, branches, commits, merging and releases and we assume the reader has some familiarity with these terms.

Keywords

Unify Model Code Base Earth System Model Code Change Configuration Management 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

References

  1. Matthews D, Wilson G, Easterbrook S (2008) Configuration management for large-scale scientific computing at the UK Met Office. IEEE Comput Sci Eng 10(6):56–64 http://doi.ieeecomputersociety.org/10.1109/MCSE.2008.144Google Scholar
  2. Pilato C, Collins-Sussman B, Fitzpatrick B (2008) Version control with subversion. http://svnbook.red-bean.com
  3. Valcke S (2006) Oasis4 user guide (oasis4_0_2). Technical report TR/CMGC/06/74, CERFACS, 42 Avenue G. Coriolis, 31057 Toulouse Cedex 1, FranceGoogle Scholar

Copyright information

© The Author(s) 2012

Authors and Affiliations

  1. 1.Met Office Hadley CentreExeterUK
  2. 2.Met OfficeExeterUK

Personalised recommendations