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

Remapping task #495

Open
forsyth2 opened this issue Sep 5, 2023 · 2 comments
Open

Remapping task #495

forsyth2 opened this issue Sep 5, 2023 · 2 comments
Labels
semver: new feature New feature (will increment minor version)

Comments

@forsyth2
Copy link
Collaborator

forsyth2 commented Sep 5, 2023

It may be useful to set up a zppy task for remapping and make it the dependency of qbo diags.

@forsyth2 forsyth2 added the semver: new feature New feature (will increment minor version) label Sep 5, 2023
@whannah1
Copy link

whannah1 commented Sep 5, 2023

For more context - for our SciDAC QBO project we were hoping to use the QBO diags output directly and take the different in the QBO amplitude between the model and reanalysis, but we can only do that if the datasets use the same levels. Furthermore, even though the stratospheric models levels will be nearly equal to pressure levels, it would be better to interpolate to a common set of pressure levels, or match whatever is used by reanalysis and add this pressure level array to the json files.

@chengzhuzhang
Copy link
Collaborator

chengzhuzhang commented Sep 5, 2023

@whannah1 thanks for providing the context. I will create an issue in E3SM diags to see if it can be more straightforward to address from e3sm diags side. I believe the level array is already included in the json files with @golaz 's recent fix https://github.com/E3SM-Project/e3sm_diags/pull/646/files. It will be available from the upcoming e3sm unified release...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver: new feature New feature (will increment minor version)
Projects
None yet
Development

No branches or pull requests

3 participants