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

Settle the question of SST definition in JEDI obs naming conventions #66

Open
twsearle opened this issue Jan 23, 2024 · 0 comments
Open

Comments

@twsearle
Copy link
Collaborator

Description

There is an open question about naming in the sea surface temperature processing. When we did the naming convention for JEDI we defined seaSurfaceTemperature as a variable. This is fine for our current processing as in situ temperature and potential temperature are identical at the surface. However, with the change to conservative temperature, the temperature is not the same as in situ temperature at the surface. Therefore we perhaps should add a seaSurfaceConservativeTemperature variable name.

In the SST configurations this is dealt with by overwriting the in situ temperatures with conservative temperature. This works adequately but is not particularly transparent. An alternative would be to not use seaSurfaceTemperature at all and just use waterTemperature and waterConservativeTemperature variable naming in the SST configurations, but this requires significant changes in the yaml.

This issue should be cross-referenced with a similar change in orca-jedi and jjdocs.

The issue was identified in http://fcm9/projects/utils/ticket/629

Acceptance Criteria (Definition of Done)

Settle a consistent approach to conservative sea surface temperature.

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