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

Dataset problem: UKESM1-0-LL missing years in Tasmin and Tasmax r14i1p1f1 #2592

Open
Karen-A-Garcia opened this issue Nov 28, 2024 · 0 comments
Assignees

Comments

@Karen-A-Garcia
Copy link
Contributor

After looking at the metadata for UKESM1-0-LL r14i1p1f1 from NIMS-KMA for both tasmin and tasmax in CMIP historical, seems to be that there is a time jump from Dec 30, 1927 to Jan 1, 1946. This brings up the CMORCheckError message:

esmvalcore.cmor.check.CMORCheckError: There were errors in variable tasmin:
 time: Frequency day does not match input data
in cube:
air_temperature / (K)               (time: 29520; latitude: 144; longitude: 192)
    Dimension coordinates:

There should 36000 values time values for the amount of time and frequency that is described by the file name and if you look at the time between 28078 and 28082 index of the you'll see the time discrepancy.

with xr.open_dataset(file_error_tasmin) as ds:
    ds = ds.isel(lat=143, lon=191)
    display(ds.time.values[28078:28082])

array([cftime.Datetime360Day(1927, 12, 29, 12, 0, 0, 0, has_year_zero=True),
       cftime.Datetime360Day(1927, 12, 30, 12, 0, 0, 0, has_year_zero=True),
       cftime.Datetime360Day(1946, 1, 1, 12, 0, 0, 0, has_year_zero=True),
       cftime.Datetime360Day(1946, 1, 2, 12, 0, 0, 0, has_year_zero=True)],
      dtype=object)

  • Full dataset description (fill out as many as you know, please):
CMIP/NIMS-KMA/UKESM1-0-LL/historical/r14i1p1f2/day/tasmin/gn/v20201019/tasmin_day_UKESM1-0-LL_historical_r14i1p1f2_gn_18500101-19491230.nc
CMIP/NIMS-KMA/UKESM1-0-LL/historical/r14i1p1f2/day/tasmax/gn/v20201019/tasmin_day_UKESM1-0-LL_historical_r14i1p1f2_gn_18500101-19491230.nc

I write this issue purely to bring awareness to this as I will not be trying to write a fix for this.

Cheers 🍺

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

3 participants