NorESMhub
Update NorESM2.0 after module changes on Betzy
Is your feature request related to a problem? Please describe.
The Betzy upgrade scheduled for Aug. 2024 will remove modules that are used to build NorESM2.0 (up to and including release-noresm2.0.7). Specifically, the intel/2020a, iompi/2020a, netCDF-Fortran/4.5.2-iompi-2020a and NCO/4.9.7-iomkl-2020a modules will be unavailable after the upgrade, and will have to be replaced by tool chains from 2022aor later.
Describe the solution you would like to see
- Update
config_machines.xmlwith a suitable set of modules for betzy - Create a new release for cime (probably starting from
cime5.6.10_cesm2_1_rel_06-Nor_v1.0.7?) - Create a new
release-noresm2.0.8with the new machine settings for betzy.
Hi and thanks! Do we have a quick fix for those of us who want to run a simulation today? :-)
Ada
@adagj I will do soon; I did not notice that there are two issues one with NorESM2 and NorESM2.1 I sent pull request for NorESM2.1:- https://github.com/NorESMhub/NorESM/issues/539#event-13860843829
I see there is a tag cime5.6.10_cesm2_1_rel_06-Nor_v1.0.8 that continues from v1.0.7, but has not been included in any NorESM2.0 release. The cime5.6.10_cesm2_1_rel_06-Nor_v1.0.8 tags the same commit as cime5.6.10_NorESM2_1_r2, which is the ancestor for cime5.6.10_NorESM2_1_r4 used for NorESM2.1.1.
Most of the changes are in config_grids.xml and config_component.xml, with some minor changes in other files. The change from cime5.6.10_NorESM2_1_r2 to cime5.6.10_NorESM2_1_r4 includes an update on Python version from 2.7 to 3.8, which probably will be needed for NorESM2.0.8 as well.
Would it make sense to include some of theses later additions also for NorESM2.0? Is there anything that is not backwards compatible?
- diff : cime5.6.10_cesm2_1_rel_06-Nor_v1.0.7 -> cime5.6.10_cesm2_1_rel_06-Nor_v1.0.8
- diff : cime5.6.10_cesm2_1_rel_06-Nor_v1.0.8 -> cime5.6.10_NorESM2_1_r4
- diff : cime5.6.10_NorESM2_1_r4 -> cime5.6.10_NorESM2_3_r2
I think there was a change in the tagging scheme at some point (some point being last November).
cime5.6.10_NorESM2_1_r2 and cime5.6.10_cesm2_1_rel_06-Nor_v1.0.8 point to the same commit.
After that, the new scheme continues but then morphs into cime5.6.10_NorESM2_3_r2. The latest tag I see is cime5.6.10_NorESM2_3_r2. I think we can use this tag for NorESM2.0, NorESM2.1, and NorESM2.3 with the next tag being cime5.6.10_NorESM2_3_r3.
@mvdebolskiy, @mvertens do you agree with this reasoning?
@gold2718 if I am correct and understood correctly if I update compiler information in noresm2_1_develop branch which is same as noresm2_3_develop branch. We do not need to update any other branch. We can create a tag which can we used for NorESM2.0, NorESM2.1, and NorESM2.3.
@monsieuralok , yes, I think one CIME update and one new tag should work for all three NorESM versions. I would feel more confident if @mvdebolskiy or @mvertens could recall here why we might need different CIME branches for NorESM2.1 and NorESM2.3.
I am not sure about tagging, but the two branches were started since it was unclear if we need to update cime to 5.8 for NorESM2.3, if I recall correctly. But it never occurred, I guess, thus their are identical.
@monsieuralok , @mvertens , @gold2718 , @mvdebolskiy
cime PR: https://github.com/NorESMhub/cime/pull/78
I have created a new tag cime5.6.10_NorESM2_3_r3 on the cime noresm2_1_develop branch.
I have created draft release notes for a new release-noresm2.0.8 code release. The tag release-noresm2.0.8 will be created once the draft release is published.
Please comment here, or edit the draft release, if you have suggestions for changes or additions.