akiyoshi ceda-cc report for CCSRNIES-MIROC32 v20211026

[charliepascoe]

I am going to ingest this the ta500, ua500, va500 and zg500 data files as they are consistent with simliar NIES data e.g. ta50_Aday_CCSRNIES-MIROC32_refD1_r1i1p1f1_gn_196001-201812.nc which has already been ingested.

However, I recommend that new versions of the single level data at specified pressure levels be submitted with the following metadata corrections:

1. remove the plev dimension attribute
2. add a plev coordinate attribute to the variable.

A new version of the data should be provided for the following variables:
ta10, ta50, ta100, ta1000,
ua10, ua50, ua100, ua1000,
va10, va50, va100, va1000,
zg10, zg50, zg100, zg1000.
which can be found in /badc/ccmi/data/post-cmip6/ccmi-2022/NIES/CCSRNIES-MIROC32/refD1/r1i1p1f1/Aday/

[charliepascoe]

I think the ceda-cc checks missed some errors with the potential vorticity metadata for the vorpot480 and vorpot840 variables.
These should be submitted as new versions with the following metadata corrections:

1. remove the lev dimension attribute
2. remove the lev variable
3. add a theta variable
4. make theta the coordinate attribute for the variable

An example of how the vorpot metadata should appear can be found in this file:
/badc/ccmi/data/post-cmip6/ccmi-2022/ECCC/CMAM/refD1/r1i1p1f1/Aday/vorpot480/gn/v20210311/vorpot480_Aday_CMAM_refD1_r1i1p1f1_gn_19600101-20181231.nc

[charliepascoe]

This comment from Martin explains why the ceda-cc code detects the vertical coordinate error in some of the data files but not others: #51 (comment)

[charliepascoe]

So the root of this issue is an inconsistency between the rules as set out in the Aday MIP table and the conventions that we actually expect the metadata to follow.
#55

[charliepascoe]

I have ingested the tas data file (tas_Aday_CCSRNIES-MIROC32_refD1_r1i1p1f1_gn_196001-201812.nc).
However I recommend that this file should also be submitted as a new version with the height dimension removed.