Repository navigation
E3SM v3.2.0 #9205
rljacob
announced in
Announcements
E3SM v3.2.0
#9205
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
E3SM V3.2 Description
Version 3.2 of the Energy Exascale Earth System Model.
Description and New Features
Version 3.2 includes all capabilities of v3.1 and adds updated high-resolution defaults, expanded coupled human and wave capabilities, additional online processing for emulation workflows, and a broad set of scientific and technical improvements across the model.
Some changes alter the climate of standard v3 configurations relative to v3.1.0 and v3.0.0.
The default grid configuration for the low-resolution configuration of v3 remains a “trigrid” consisting of:
The high-resolution coupled configuration introduced in v3.1 remains part of v3.2:
Additional coupled capabilities and configurations were added for v3.2:
CRYO2010-WW3andWCYCL2010-WW3.Planned Simulations
Data from the following simulations will be made available:
Watch E3SM Data Docs for information.
Climate-Changing and Answer-Changing Updates
Several changes in v3.2 are expected to change answers relative to v3.1, including changes that affect the climate of standard configurations:
nlmaps_atm2srf_conserve.Other answer-changing or scientifically important changes include:
Atmosphere
The atmospheric component remains EAM. EAM in v3.2 includes focused high-resolution support and continued infrastructure and forcing updates:
HOMME updates include:
pm-gpu.phys_grid_mod.HOMME2SCRIP.pyNetCDF output typing.eam-thetahy_sl_pg2_masspasses.EAMxx remains an optional atmosphere component and is not yet supported in production configurations. Development in v3.2 continued rapidly, with substantial model, diagnostics, and infrastructure advances:
Field::updatefor masked affine transformations.Field::aliasoverloads for dimension tag renaming and support for copying selected data and metadata in a field clone.PIO_TYPEoptions in I/O configuration.Fielda shallow-const container and preserved allocation properties in process tendency fields.test-all-eamxx.NODE_EXTRA_CA_CERTShandling.Land
The land component remains ELM. In v3.2, land development focused on FATES updates, metadata improvements, and coupled human-system support:
long_namemetadata to restart file variables.FATES updates in v3.2 include:
GCAM coupling was expanded in v3.2:
River
The river model remains MOSART. In v3.2, updates are limited but include answer-changing behavior for selected configurations:
qgwlis redirected in low-resolution wave-enabled configurations through namelist default changes.Ocean
The ocean component remains MPAS-Ocean. v3.2 includes climate-changing fixes, new physical options, biogeochemistry support, and high-resolution tuning:
SOwISC12to30E3r3to enable Langmuir mixing, latitude-dependent Southern Ocean background diffusivity, and one-step congelation freezing.lateral_wallsnamelist section andconfig_wall_slip_factor.Sea Ice
The sea-ice component remains MPAS-Seaice. Major v3.2 changes include an updated Icepack base and several answer-changing default adjustments:
Land-Ice
The land-ice component remains MALI. The land-ice component is still not yet supported in production configurations, but v3.2 includes further capability and configuration updates:
MALI-Dev/developwith a spatially varying crevasse-depth calving law.Waves
The optional wave component remains WAVEWATCH III. WW3 is still not yet supported in production simulations, but v3.2 expands coupled wave capability:
CRYO2010-WW3andWCYCL2010-WW3compsets for repeating 2010 conditions.Coupler & Driver
The default coupler remains cpl7/MCT through driver-mct, while driver-moab continued substantial development in v3.2.
driver-mct changes include:
nlmaps_atm2srf_conservewhich helps with conservation in tri-grid cases near coastlines (nlmaps is always conservative).driver-moab changes include:
rpointerrobustness.cplcomp_moab_Initwith shared helpers.AI/ML and Infrastructure
v3.2 adds further infrastructure for emulation, diagnostics, build portability, and tooling:
EXTRA_DEBUGXML setting.MOAB_ROOTon several machines so driver-moab cases can run.This discussion was created from the release E3SM v3.2.0.
All reactions