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

Consistent field names between CMEPS, MOM6 and CICE6 #1905

Closed
DeniseWorthen opened this issue Sep 14, 2023 · 3 comments · Fixed by #1906 or NOAA-EMC/CICE#69
Closed

Consistent field names between CMEPS, MOM6 and CICE6 #1905

DeniseWorthen opened this issue Sep 14, 2023 · 3 comments · Fixed by #1906 or NOAA-EMC/CICE#69
Assignees
Labels
enhancement New feature or request

Comments

@DeniseWorthen
Copy link
Collaborator

DeniseWorthen commented Sep 14, 2023

Description

Currently there is a mix of field names being used in MOM6 and CICE6, meaning some field names are specified CESM-style (F = flux, S = state) and some using descriptions (mean_xxx_flux). This was the result of unifying both the MOM6 and CICE6 caps at the same time that UFS was transitioning from the NEMS mediator to the CMEPS mediator. The CMEPS mediator in UFS uses only CESM-style field names.

It is clearer from a user perspective and for developing documentation if the naming convention is consistent. It also avoids the ambiguity around what "mean" means (spatial, temporal, both?). The "averaging" context can be provided in the description entry in the field dictionary if required.

Solution

Coupling field names in the MOM6 and CIE6 caps need to be changed to the CESM-style (S=state, F=flux) field names.
Note that for WW3, the only non CESM style field name will be resolved in NOAA-EMC/WW3/pull/1034

Alternatives

Related to

@DeniseWorthen DeniseWorthen added the enhancement New feature or request label Sep 14, 2023
@natalie-perlin
Copy link
Collaborator

@jkbk2004 -
Code modification required to address this suggested enhancement, assigning to a Code Management team

@jkbk2004 jkbk2004 removed their assignment Sep 14, 2023
@junwang-noaa
Copy link
Collaborator

@natalie-perlin may I ask why this is assigned to code management team?

@jkbk2004
Copy link
Collaborator

@natalie-perlin Please, don't assign randomly.

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