update to ESCOMP cmeps1.1.23#44
Conversation
* add hflx_fire, evap_fire, cpl_fire Co-authored-by: Grant Firl <[email protected]>
* restart_fh using shr_is_restart_fh_mod * Use is_restart_fh revised to avoid thread-local storage inter-component conflicts
add connection between xml and fortran
Add arbitrary restart hour for UFS
* add consf_uv3d option, needed by UFS
add ATM_NCPL entry for POLARCAP
…ping Add explicit RH creation for uv3d mapping
In CESM we ran into a funny issue where the ocean component was taking significantly longer to write output at the end of the run than the other components, and somehow the other components convinced the mediator that the model had finished successfully even though the ocean component was still doing stuff. This barrier makes everyone wait to catch up.
Add one more barrier at end of run
…odules_escomp new atmocn flux modules to replace shr_flux_mod and removal of water isotope references
ERR test needs to be added back in here so that the correct history files are copied back for the restart. This was original added in ESCOMP#582, but accidently removed in ESCOMP#597.
|
@matsbn - with this PR the ocean albedo scheme is always 1 - for fully coupled as well as stand-alone BLOM configurations. Is this the correct behavior you wanted? |
|
We have started to run with ocean albedo 1 as standard namelist option (setting it manually), so it would be good to have this in as default. Would be good to have confirmation from @matsbn as well, but I don't think we need to put this on hold if he doesn't chime in on this PR. |
As @TomasTorsvik, ocean_albedo_scheme = 1 has been used for all coupled simulations lately and should now be default for them. I cannot recall that the albedo specification is part of the OMIP protocol and probably it will not matter much since SST is quite constrained. I think we should proceed with this PR and change behaviour for OMIP later if necessary. |
Description of changes
This PR updates NorESMHub CMEPS to ESCOMP CMEPS 1.1.23.
There are still numerous differences at this point between the two repositories and it's not clear that NCAR will want many of the changes we currently have in the NorESMhub repo.
Specific notes
Contributors other than yourself, if any:
CMEPS Issues Fixed: This PR is dependent on the upcoming CTSM PR from @mvdebolskiy (this needs to be filled in).
Are changes expected to change answers? Yes
The update to shr_megan_mod.F90 will change answers for compsets that use megan. Otherwise bfb is expected.
Any User Interface Changes (namelist or namelist defaults changes)?
Testing performed
Please describe the tests along with the target model and machine(s)
If possible, please also added hashes that were used in the testing
No testing has been done yet.