Repository for MPAS models and shared framework releases.
Fortran C Python Makefile PHP C++ Other
Latest commit ef684ba Jan 7, 2017 @mgduda mgduda Merge branch 'release-v5.0'
This merge introduces v5.0 of all MPAS models.

* release-v5.0: (964 commits)
  Fix issue with 'dzs' when running r8 model with r4 initial conditions
  This merge fixes a restartability error in the new Tiedtke scheme.
  Avoid bit-reproducibility errors in GWDO scheme due to 'kpblmin' and 'kpblmax' computation
  Fix incorrect assignment of 'xlamdd', 'frh', and 'mentrd_rate' in Grell-Freitas scheme
  * In ./src/core_atmosphere/Registry.xml, corrected typo (description instead of   decription) in the definition of the variable nr.
  * In ./src/core_atmosphere/physics/mpas_atmphys_control.F, modified inquiring   about the Thompson microphysics tables in the subroutine physics_table_init.   The modified logic now allows the different tables to be read for each MPI   task.
  * In ./src/core_atmosphere/physics/physics_wrf/module_mp_thompson.F, in subroutine mp_gt_driver,   moved the initialization of variables Nt_c and mu_c before initialization of local mixing ratios   and number concentrations. This change allows a proper initialization of the local variable nc   when is_aerosol_aware is false.
  Add exit messages at the end of core_finalize routines
  Update "possible_values" for physics schemes
  * In ./src/core_atmosphere/physics/mpas_atmphys_control.F, modified checking the   config_gwdo_scheme option to allow bl_ysu_gwdo to be run when the MYNN pbl and   surface layer options are chosen.
  Fix bug in storage and application of IAU tendency contributions
  Update to physics suites: New Tiedtke and YSU GWDO
  Change suite name 'convection_scale_aware' to 'convection_permitting'
  Simplify IAU calls from atm_srk3( )
  Rename 'zz_rtheta_pp_old' to 'rtheta_pp_old'
  Fix bug in location of call to get IAU tendency contributions
  Remove unused variable 'rtheta_pp_old' from atmosphere Registry.xml file
  Final corrections to namelist and variable attributes for MPAS-Atmosphere v5.0
  Initialize t_oml_200m_initial field when climatological OML depth is used
  Add lower bound of 1.0e-8 to vapor pressure in dewpoint calculation


The Model for Prediction Across Scales (MPAS) is a collaborative project for developing atmosphere, ocean, and other earth-system simulation components for use in climate, regional climate, and weather studies. The primary development partners are the climate modeling group at Los Alamos National Laboratory (COSIM) and the National Center for Atmospheric Research. Both primary partners are responsible for the MPAS framework, operators, and tools common to the applications; LANL has primary responsibility for the ocean model, and NCAR has primary responsibility for the atmospheric model.

The MPAS framework facilitates the rapid development and prototyping of models by providing infrastructure typically required by model developers, including high-level data types, communication routines, and I/O routines. By using MPAS, developers can leverage pre-existing code and focus more on development of their model.


This README is provided as a brief introduction to the MPAS framework. It does not provide details about each specific model, nor does it provide building instructions.

For information about building and running each core, please refer to each core's user's guide, which can be found at the following web sites:


MPAS-Land Ice


Code Layout

Within the MPAS repository, code is laid out as follows. Sub-directories are only described below the src directory.

└── src
    ├── registry -- Code for building Registry.xml parser (Shared)
    ├── driver -- Main driver for MPAS in stand-alone mode (Shared)
    ├── external -- External software for MPAS (Shared)
    ├── framework -- MPAS Framework (Includes DDT Descriptions, and shared routines. Shared)
    ├── operators -- MPAS Opeartors (Includes Operators for MPAS meshes. Shared)
    ├── inc -- Empty directory for include files that Registry generates (Shared)
    └── core_* -- Individual model cores.

Model cores are typically developed independently. For information about building and running a particular core, please refer to that core's user's guide.