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

[ERROR] cmorized ocean vertical velocity #280

Closed
YanchunHe opened this issue May 21, 2021 · 6 comments
Closed

[ERROR] cmorized ocean vertical velocity #280

YanchunHe opened this issue May 21, 2021 · 6 comments
Assignees
Labels
error error in the dataset

Comments

@YanchunHe
Copy link
Collaborator

Quote A. Gjermundsen

I wonder if there is something wrong with the cmorized wo variables.
when looking at wo in gn grid the values range from -0.0012 to 0.001 m/s. For the same variable, experiment and time period in the cmorized gr files, wo values range from -0.0016 to 1.88e8. It seems to me that all bottom values (or where there is bathymetry) are given in the range 1e7 to 1.9e8 instead of nan-

E.g.
/nird/projects/NS9034K/CMIP6/CMIP/NCC/NorESM2-LM/piControl/r1i1p1f1/Omon/wo/gn/latest/wo_Omon_NorESM2-LM_piControl_r1i1p1f1_gn_160001-160912.nc

/nird/projects/NS9034K/CMIP6/CMIP/NCC/NorESM2-LM/piControl/r1i1p1f1/Omon/wo/gr/latest/wo_Omon_NorESM2-LM_piControl_r1i1p1f1_gr_160001-160912.nc

@YanchunHe YanchunHe added the error error in the dataset label May 21, 2021
@YanchunHe
Copy link
Collaborator Author

You are right, @adagj . The noresm2cmor tool uses the surface grid to mask the ocean grid of missing values, so that it fails to identify the missing value points in vertically interpolated data of marginal seas.

It is hard to redo the cmorization of wo for all the experiments, but should be possible to report an issue at ESGF, that resetting all values larger than 1 should be a quick fix.

Alok, could you report this issue at ESGF for all the published wo on gr grid (data on gn grid are OK). @monsieuralok

I can reprocess wo on gr for all CMIP and SenarioMIP experiments, if you find useful, Ada!

@adagj
Copy link
Collaborator

adagj commented May 21, 2021

@YanchunHe
For my sake, you don't need to reprocess anything. I set all wo larger than 1 to nan (as you also suggested) in my scripts and the results seem reasonable. I just wanted to let you know :)

(ps. these large wo values are not just marginal seas, but all "bottom" values)

Ada

@YanchunHe
Copy link
Collaborator Author

Alok, could you report this issue at ESGF for all the published wo on gr grid (data on gn grid are OK). @monsieuralok

A quick fix is to set wo to NaN when it is larger than 1.

@monsieuralok
Copy link
Collaborator

monsieuralok commented Jun 28, 2021

@YanchunHe would this issue will be fixed in future version? or if already some data are published with fixed?

@monsieuralok
Copy link
Collaborator

@YanchunHe
Copy link
Collaborator Author

YanchunHe commented Jun 29, 2021

Thanks Alok! Cmorized datasets (after version v20210521) in the future will not have this issue. Already published data will be not changed. This errata should be enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
error error in the dataset
Projects
None yet
Development

No branches or pull requests

3 participants