Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Prosed Plan:

...

Note

EAMxx is not yet officially supported. Use these pages at your own risk.

Background:

E3SM has developed the idiosyncratic but convenient habit of referring to specific humidity (=mass of water species divided by mass of total air) as wet mixing ratio and the actual mixing ratio (=mass of water species divided by mass of dry air) as dry mixing ratio.

Unlike EAMf90, the EAMxx atmospheric driver(AD) requires all variables passed to it to be wet mixing ratios. Each process called by AD can choose to use wet or dry mixing ratio, but must convert its variables (and - if required - the time tendencies it produces) back to wet mixing ratio. For processes which exclusively use wet mixing ratio, there is no need for any conversion however, for parameterizations which use dry mmr, following steps must be followed:

  1. Interface layer of parameterization should convert wet mmr to dry mmr

  2. Parameterization computes tendencies using the dry mmr internally

  3. Interface layer of the parameterization will then convert the dry mmr tendencies to wet mmr

  4. These wet mmr tendencies are then passed on to AD

. SCREAM provide following methods for converting dry mass mixing ratio (mmr) to wet mmr and vice versa via functions:

...

calculate_wetmmr_from_drymmr

Volume Mixing ratios (vmr)[units: kmol-of-specie/kmol-of-(dry or moist)-air]:

Some parameterizations may use vmr. For these parameterizationsThe same rules hold for volume mixing ratio (vmr). For processes requiring vmr, SCREAM provide the following functions to convert between mmr and vmr (and vice versa):

calculate_mmr_from_vmr

calculate_vmr_from_mmr

vmr can be dry or wet, appropriate . Appropriate conversion should be made based on parameterization requirements. Tendencies computed by the parameterization should be converted back to wet mmr before passing these back to AD.

Type of mixing ratios used by SCREAM parameterization:

  1. P3 - Dry mmr

  2. SCREAM - Dry mmr

  3. HOMME - Wet mmr

  4. RRTMGP - Wet vmr

Tasks:

P3 (uses dry mmr):

  •  Ensure that P3 converts wet mmr to dry mmr for all constituents in its interface layer
  •  Ensure that tendencies from P3 are converted back to wet mmr

SHOC [uses dry mmr]:

  •  Ensure that SHOC converts wet mmr to dry mmr for all constituents in its interface layer
  •  Ensure that tendencies from SHOC are converted back to wet mmr

RRTMGP [uses wet vmr]:

  •  Ensure that RRTMGP converts wet mmr to wet vmr
  •  Ensure that tendencies from RRTMGP are converted back from wet vmr to wet mmr

Explanation for why each process is wet or dry:

Dycore:wet mmr - The dycore interface is currently written for wet mixing ratios because internally, the dycore’s prognostic mass variable is total mass (not dry mass). Working with wet mixing ratios allows the dycore to simply compute tracer mass, without ever computing “dry mass”. Dry mass is an unusual quantity which would not normally be used within the dycore.

Atmosphere Driver:wet mmr - Because many variables passed to the AD are advected by the dycore, we decided to insist that all variables handled by the AD are wet.

P3:dry mmr - Microphysics contains a lot of empirical parameterizations. Empirical parameterizations tend to assume variables are couched in dry mixing ratio since that’s what’s usually measured observationally.

SHOC:wet mmr - I should re-read the SHOC overview paper before explaining this, but basically SHOC is derived from the Navier-Stokes equations which should be able to be adapted equally well for wet or dry variables.

RRTMGP:wet vmr - Ben Hillman ?