-
Notifications
You must be signed in to change notification settings - Fork 38
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
Dataset problem: Issues with hybrid height coordinate of UKESM1-0-LL (CMIP6) #543
Comments
@matthew-mizielinski is this something that is already on your to-do list for future releases of CDDS? 🍺 |
@valeriupredoi , this is a feature of CMOR and has been discussed before, see PCMDI/cmor/issues/177 and discussions within the CF community linked to therein. I'd suggest having a chat with your local CF standards person (e.g. David Hassell) about this to get a full understanding of this one. We can't change this without a corresponding change to CMOR and at the moment I don't see that happening on CMIP6 timescales. |
Brilliant! Cheers for the heads up, very helpful indeed! |
Hello, I think this file described by the CDL above is wholly CF-1.7 compliant. There is, however, an alternative encoding that names
This encoding, or the one at the top of the page, are, from a CF perspective, equally valid. I don't know if CMIP6/CMOR has a preference. |
cheers muchly @davidhassell - afraid these things are slowly getting above my paygrade and am getting more puzzlated by the interplay between CF and CMOR. Bottom lines: @matthew-mizielinski no chance we can fix this upstream in the data conversions? What do we do with the other models that behave the same way (bunch of them in the other issues) - do we contact the model providers? Ping @zklaus too |
@valeriupredoi -- without changes to CMOR we cannot change this. Given that the CF community are happy with the current expression of this data (noting @davidhassell's comment and Karl Taylor's on the CMOR issue I posted above) I suggest that ESMVal should handle this case. |
cool! Cheers, Matt 🍺 |
I agree that the original coding is actually correct when it comes to the connection between
So long-term we have to be able to understand the first method. Having said that, shortcomings in software, even CMOR can not be excuses for bad data. Many groups have fixed data after CMOR (just look for cdo in the history attributes). When that's necessary, it's necessary. |
Done, see SciTools/iris#3678. |
Fix for this exists. I am 99% sure that this data will not be fixed on ESGF (we are approaching CMIP7), so I am closing this now. |
Describe the dataset issue
Bounds of
b
not set (see #536). Not sure if allowed: Does only providealtitude
as vertical coordinate, notair_pressure
.Data file has been changed by you in any way/mnt/lustre02/work/bd0854/DATA/ESMValTool2/CMIP6_DKRZ/CMIP/MOHC/UKESM1-0-LL/historical/r1i1p1f2/Amon/cl/gn/v20190406/cl_Amon_UKESM1-0-LL_historical_r1i1p1f2_gn_200001-201412.nc
ncdump (without global attributes):
Fix provided in #529.
The text was updated successfully, but these errors were encountered: