You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: