MAPL 2.60.0 #4052
mathomp4
announced in
Announcements
MAPL 2.60.0
#4052
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.
-
This release of MAPL has fixes and updates. Among the fixes are ones for NRL solar constant reads (when cycling over Cycle24) and fixes for NVHPC builds.
There are also two major changes. First, the default
VERSIONforHISTORY.rcis now1instead of0. Nearly all GEOS History RC files have hadVERSION: 1at the top for many years and rely on functionality from it (e.g., usingGRID_LABELSto specify grids). However, it was found that when this was accidentally left off by a user, the resulting run behavior was confusing as the symptoms were not obvious.The other change is an enhancement of the MAPL Automatic Code Generator (ACG) which also fixes a bug in the Python. However, this bugfix can have an effect if a gridded component had a StateSpecs file that could trigger the bug. The issue was one of the "columns" a StateSpecs file can have is for how to handle fields restarts. MAPL has options like
MAPL_RestartOptionalandMAPL_RestartSkipthat tell MAPL if a field is optional (if not present, that's okay) or skippable (if not present, okay, and do not write).The ACG has allowed two ways for users to specify these options. You could use
OPTorMAPL_RestartOptionalandSKIPorMAPL_RestartSkip. The bug was that if a user didn't use the abbreviated option, the ACG did not emit the corresponding line.An exemplar StateSpecs would be:
Here we have two fields one,
SSisMAPL_RestartOptional, andDEEP_LAKES_MASKisMAPL_RestartSkip. The difference in emitted code between MAPL 2.59 (and earlier) and MAPL 2.60 is:MAPL 2.60 now correctly emits the
restart=line. Now, for fields that useMAPL_RestartOptionalinstead ofOPTthe bug was a no-op. In MAPL, if there is norestart=line, the default to do isMAPL_RestartOptional. But the otherMAPL_Restart*options would be affected.For GEOSgcm, the only StateSpecs file that is affected is
SS2G_StateSpecs.rc. So for GEOSgcm, when you compare a run with MAPL 2.59 to MAPL 2.60, thess_internal_checkpointwill not have theDEEP_LAKES_MASKvariable since it is now correctly skipped.NOTE: The presence of
DEEP_LAKES_MASKdoes not affect the state of the model. This mask is recomputed on each run and is constant.This version of MAPL was tested with:
ifort) 2021.6.0 and 2021.13ifx) 2025.0The libraries this version of MAPL is currently tested with are below.
-DBUILD_WITH_FARGPARSE=YES, default=YES)-DBUILD_WITH_PFLOGGER=YES, default=YES)Also, if you build with Baselibs and/or
-DUSE_F2PY=ON, you should use (at least):We recommend most external users set
-DUSE_F2PY=OFFWe also require CMake 3.24 or higher.
From
CHANGELOG.mdFixed
MAPL_MaskModfrom submodule to moduleChanged
VERSIONin History to1(which has been the effective default inHISTORY.rcfor some time)components.yamlESMA_envv5.13.0ESMA_cmakev3.63.0/v4.20.0 or higherESMA_cmakev3.64.0FindISSM.cmakeWhat's Changed
Full Changelog: v2.59.0...v2.60.0
This discussion was created from the release MAPL 2.60.0.
Beta Was this translation helpful? Give feedback.
All reactions