Skip to content
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

Rename ufs related coupling modes; replace nems with ufs #418

Merged
merged 2 commits into from
Nov 7, 2023

Conversation

DeniseWorthen
Copy link
Collaborator

Description of changes

Includes changes recently committed to https://github.com/NOAA-EMC/CMEPS

Specific notes

The non-CESM coupling modes have been clarified and renamed to use "ufs" instead of "nems".
The esmFldsExchange_nems_mod has be renamed to esmFields_Exchange_ufs_mod
Documentation has been updated.

Contributors other than yourself, if any:

CMEPS Issues Fixed (include github issue #):

Are changes expected to change answers? (specify if bfb, different at roundoff, more substantial)

  • All changes should be B4B for CESM

Any User Interface Changes (namelist or namelist defaults changes)?

  • no

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

Changes have been tested and committed in UFS.

@@ -68,15 +68,15 @@ subroutine esmFldsExchange_nems(gcomp, phase, rc)
if (chkerr(rc,__LINE__,u_FILE_u)) return

! Set maptype according to coupling_mode
if (trim(coupling_mode) == 'nems_orig' .or. trim(coupling_mode) == 'nems_orig_data') then
if (trim(coupling_mode) == 'ufs.nfrac' .or. trim(coupling_mode) == 'ufs.nfrac.aoflux') then
maptype = mapnstod_consf
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you double check these. I see ufs.nfrac, ufs.nfrac.aoflux and ufs.frac.aoflux - are all of these correct?

@@ -47,7 +47,7 @@ module med_internalstate_mod
character(len=CS), public :: glc_name = ''

! Coupling mode
character(len=CS), public :: coupling_mode ! valid values are [cesm,nems_orig,nems_frac,nems_orig_data,hafs,nems_frac_aoflux,nems_frac_aoflux_sbs]
character(len=CS), public :: coupling_mode ! valid values are [cesm,ufs.nfrac,ufs.frac,ufs.nfrac.aoflux,ufs.frac.aoflux,hafs]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this answers my previous question.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the original names have just been replaced with more explicit names that reflect how or when a mode is used in ufs.

@jedwards4b jedwards4b merged commit 01bf411 into ESCOMP:main Nov 7, 2023
2 checks passed
@DeniseWorthen DeniseWorthen deleted the feature/emc_updates branch August 2, 2024 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

coupling mode definitions are poorly defined use ufs-appropriate named files and executables
4 participants