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

use ufs-appropriate named files and executables #1756

Closed
DeniseWorthen opened this issue May 18, 2023 · 0 comments · Fixed by NOAA-EMC/CMEPS#101, #1932 or ESCOMP/CMEPS#418
Closed

use ufs-appropriate named files and executables #1756

DeniseWorthen opened this issue May 18, 2023 · 0 comments · Fixed by NOAA-EMC/CMEPS#101, #1932 or ESCOMP/CMEPS#418
Assignees
Labels
enhancement New feature or request

Comments

@DeniseWorthen
Copy link
Collaborator

Description

There are multiple legacy references to "NEMS" and references to standalone fv3 that are still used with the current UFS.

Solution

We need to gradually transition away from the legacy terms to a naming convention appropriate to the current UWM. This will have RT impacts (but should not change any baseline) as well as G-W impacts.

A partial list includes:

CMEPS: references to nems in the field exchange modules and coupling types
Scripts/tests: references to nems.configure
Executables: all executables are named fv3.exe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment