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

Update Variable Names to be Consistent with Updated Jedi Hashes #26

Open
JingCheng-NOAA opened this issue Dec 10, 2024 · 3 comments
Open
Assignees

Comments

@JingCheng-NOAA
Copy link
Collaborator

Recent JEDI hashes update has multiple variable name changes.
A recent test with updated satwind yaml file indicates that tsea is no longer used inside JEDI. If remove this variable from state variable list, the an error Field_fail: Field water_area_fraction cannot be obtained from input fields..
However, if replace this name with sea_surface_temperature, JEDI will look for sst in restart file.
If replace this name with skin_surface_temperature, JEDI will look for ts in restart file. But none of sst or ts exist in restart file.

@JingCheng-NOAA JingCheng-NOAA self-assigned this Dec 10, 2024
@JingCheng-NOAA
Copy link
Collaborator Author

JingCheng-NOAA commented Dec 10, 2024

Fixed with two minor changes: 1) replace tsea with skin_temperature_at_surface in state variables; 2) add following in restart.yaml

- long name: skin_temperature_at_surface
  io name: tsfc
  io file: surface

Above changes will be included in the next HDASApp updates.

@JingCheng-NOAA
Copy link
Collaborator Author

According to GDASApp recent update, the variable tsea is replaced by tmpsfc, which is represent the skin_temperature_at_surface in history file. However, in HDASApp, we do not use history file but restart file, in which there is no variable named as tmpsfc.

@JingCheng-NOAA
Copy link
Collaborator Author

JingCheng-NOAA commented Dec 19, 2024

Modified the gfs-restart.yaml with following, and solve the warning issue.

- long name: skin_temperature_at_surface
  io name: tsea
  io file: surface

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

No branches or pull requests

1 participant