Closed WilliamJamieson closed 4 years ago
@WilliamJamieson You are correct. We have not yet updated CTM to be compatible with the latest version of GEOSchem_GridComp. When that is complete (and tested), a new CTM release will be issued. Is this time-critical for you?
@mmanyin This is not time-critical. I just noticed this issue when I began work to start refactoring part of the GEOSchem_GridComp as a part of a proof of concept that we can start using HEMCO pulled from the new HEMCO repository: https://github.com/GEOS-ESM/HEMCO, instead of using what was copied directly into GEOSchem_GridComp from Harvard.
@WilliamJamieson Sounds good. Since I am tracking CHEM changes in both the CVS (Icarus) and GIT (Jason) versions, for both GCM and CTM, there are times when one gets ahead of the others. Thanks for understanding.
@mmanyin I went ahead and submitted a PR to resolve this, its a zero-diff minor change and it works with the current configuration and with GEOSchem_GridComp develop as well.
The CTM will not build when
GEOSchem_GridComp
is checked out to the master branch.One gets error messages of the following form:
This is likely related to the following cleanup commit: https://github.com/GEOS-ESM/GEOSchem_GridComp/commit/dbcc7fbf2e48fdf4fda4349681234e9af58cad8e#diff-b8425f43f47b5b8b76d182087d4e9d50
It is likely fixed by changing form
rcEsmfReadLogical
toESMF_ConfigGetAttribute
.