-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update submodules to ones that are based on cesm3_0_alpha04a #2853
base: cesm3_0_beta04_changes
Are you sure you want to change the base?
Update submodules to ones that are based on cesm3_0_alpha04a #2853
Conversation
…requires PIO and NetCDF as a result
…ated beyond it as needed by PF UNIT testing, and ccs_config just updated to one beyond the previous one used by CTSM
…cesm30b04submodules
…nd share forward, and remove mct
@billsacks and @jedwards4b could you review this for the cmake changes I made for the PF unit testing? I learned more about cmake as a result of getting this to work, but I'd like to have it reviewed by the two of you with more knowledge/skill in using cmake. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would remove the lines in CMakeLists.txt that you have commented out, but otherwise LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for getting this working @ekluzek! A couple of questions here....
OK, my suspicion about LILAC was correct, running the LILAC test I get a fail:
|
… what's going on based on code review
I've fixed the LILAC problem between a minor update, and something I need to add to cime: Now, I'm wondering what will happen with run_neon? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your explanations to my questions, @ekluzek ! I'm satisfied with this now.
Answers for aux_clm were identical on Derecho, but 36 tests on Izumi show answer changes that appear to be roundoff, but propagate in some fields: ERI_D_Ld9_P48x1.f10_f10_mg37.I2000Clm50BgcCru.izumi_nag.clm-reduceOutput The mpi-serial tests are failing at the build step as well: ERS_D_Ld5_Mmpi-serial.1x1_vancouverCAN.I1PtClm50SpRs.izumi_nag.clm-CLM1PTStartDate (SHAREDLIB_BUILD NLCOMP) |
It looks like mpi-serial works up to the following set of submodules: ccs_config_cesm1.0.0 Beyond that it starts breaking. The set I should use together to get working are the cesm3_0_alpha02a externals: ccs_config_cesm1.0.0 cesm3_0_alpha03b has the next set of important updates for ccs_config and cime. The next set of updates are the recent ones that were important in getting PFunit tests to work. NOTE: The top set is still showing changes to answers on Izumi, so the change in answers must be between the ctsm5.3.009 externals and the ones listed above. |
Hi Erik, I found that the configure script was not included in the mpi-serial distribution, I have added it in ESMCI/mpi-serial#30. I think that this will allow you to update to the latest tags. |
Excellent, thanks @jedwards4b! Yeah, that is one of the things I saw, I thought it might be generated as part of the build process. But, obviously not. Thanks for figuring that out. I"ll try with that branch and make sure it works. |
Description of changes
Update the submodules to something close to cesm3_0_alpha04a. I needed to update cime and ccs_config beyond to get the PF Unit testing working.
Specific notes
Remove mct from submodules
Add mpi-serial to submodules
Update the PF unit testing to use the full ESMF library (which will enable wider testing), this also required bringing in NetCDF and PIO libraries which we shouldn't actively use but may allow us to do fewer stub modules for I/O.
Contributors other than yourself, if any: @jedwards4b
CTSM Issues Fixed (include github issue #):
Fixes #2640
Fixes #2375
Finishes resolving #2294
Are answers expected to change (and if so in what way)?
I'm actually not sure yet, I think possibly compsets with active CISM might
Any User Interface Changes (namelist or namelist defaults changes)? No
Does this create a need to change or add documentation? Did you do so? No No
Testing performed, if any: will do regular and ctsm_sci
So far done PF UNIT testing and testing of two simple cases
I haven't tested this for LILIC and I wonder if it will fail