v1.9.1
In this version
- 5 packages built with Spack for use on compute nodes:
- esmf 8.4.2
- moab 5.5.1
- nco 5.1.9
- tempestextremes 2.2.1
- tempestremap 2.2.0
- A few packages have been updated. In addition to
moab
andnco
listed above, notable updates include:- mpas_tools 0.27.0
- zppy 2.3.1
- zstash 1.4.1
New and improved
-
MOAB:
- New ESMF format NC reader support
- Improved support for reading MPAS files directly
- Improved API documentation now available
- Fix several outstanding issues in
mbtempest
tool- Propagate
grid_dims
correctly for RLL grids - Store
history
metadata as attributes for provenance
- Propagate
- A new halo-exchange example to measure performance of nearest-neighbor halo-exchange communication kernels
- Several configuration and build updates for running on ALCF and OLCF systems
-
NCO:
- See full release notes at https://github.com/nco/nco/blob/5.1.9/doc/ANNOUNCE
- ncremap now, by default, fills with 0.0 (instead of FillValue) gridcells where sub-gridscale fraction is zero. Previous behavior (filling with FillValue) can be restored with new
--mpt_mss
option. - ncremap supports new TR bilinear and integrated bilinear algorithm types
- ncremap supports new standard names for old algorithms, e.g.,
esmfaave
,traave
,ncoaave
- ncra, ncrcat fix behavior of dimension interleave (ILV) parameter NCO 5.1.9 User Guide
- All operator fix possible path separator issue in MS Windows
- Improved inferral of MALI grids (radians rather than degrees automatically detected)
- Support for attributes stored as NC_STRING rather than NC_CHAR
-
zppy: A new parameter
keep_mvm_case_name_in_fig
enables turning on and offref_name
in e3sm_diags figure names in model vs model case. The current IICE comparison viewer will work seamlessly again with e3sm_diags output generated withkeep_mvm_case_name_in_fig=False
for model vs model runs. Additionally, the default set order for E3SM Diags has been returned to its original order, and the machine name can now be discovered on compute nodes while using E3SM Unified. -
zstash: Globus endpoints are beginning to require extra consents. This latest version of
zstash
addresses this issue by automatically prompting the user for authentication credentials to provide these consents, if required.