search

cedadev / ccmi-2022

CCMI-2022 - in support of the WMO/UNEP Scientific Assessment of Ozone Depletion Report 2022
BSD 2-Clause "Simplified" License
0 stars 4 forks source link

akiyoshi ceda-cc report for CCSRNIES-MIROC32 v20210902 #48

Open charliepascoe opened 3 years ago

charliepascoe commented 3 years ago

FAILED:: Global attributes do not match constraints: [('frequency...

I apologise, I did not clearly explain the error with the frequency attribute in your last data upload.

Amon variables require the frequency attribute to be mon A10dayPt variables require the frequency attribute to be 10dayPt Aday variables require the frequency attribute to be dayPt AdayZ variables require the frequency attribute to be dayPt AmonZ variables require the frequency attribute to be mon

All files need the frequency attribute to be corrected. You can see the frequency attribute needed for each variable in the MIP tables which can be found here

charliepascoe commented 3 years ago

FAILED:: Variable XXX not in table AdayZ This error is found for bro_AdayZ_CCSRNIES-MIROC32_refD1_r1i1p1f1_gnz_196001-201812.nc clo_AdayZ_CCSRNIES-MIROC32_refD1_r1i1p1f1_gnz_196001-201812.nc noy_AdayZ_CCSRNIES-MIROC32_refD1_r1i1p1f1_gnz_196001-201812.nc

AdayZ only has 3 variables: ta, ua and zg https://github.com/cedadev/ccmi-2022/blob/main/Tables/CCMI2022_AdayZ.json

charliepascoe commented 3 years ago

[pressure_levels]: FAILED:: plev coordinate not found A plev error is found in the following data files: ta500_Aday_CCSRNIES-MIROC32_refD1_r1i1p1f1_gn_196001-201812.nc ua500_Aday_CCSRNIES-MIROC32_refD1_r1i1p1f1_gn_196001-201812.nc va500_Aday_CCSRNIES-MIROC32_refD1_r1i1p1f1_gn_196001-201812.nc zg500_Aday_CCSRNIES-MIROC32_refD1_r1i1p1f1_gn_196001-201812.nc

I had a look at the netCDF header for one of these and I can see that the plev attribute is there and has been described. So I had a look again at a comparable data file from ECCC /badc/ccmi/data/post-cmip6/ccmi-2022/ECCC/CMAM/refD1/r1i1p1f1/Aday/ua500/gn/v20210311/ua500_Aday_CMAM_refD1_r1i1p1f1_gn_19600101-20181231.nc 

    double plev ;
        plev:units = "Pa" ;
        plev:axis = "Z" ;
        plev:positive = "down" ;
        plev:long_name = "pressure" ;
        plev:standard_name = "air_pressure" ;

And compared it to /datacentre/arrivals/users/akiyoshi/ccmi-2022/v20210902/zg500_Aday_CCSRNIES-MIROC32_refD1_r1i1p1f1_gn_196001-201812.nc

    double plev(plev) ;
        plev:axis = "Z" ;
        plev:units = "hPa" ;
        plev:long_name = "Pressure" ;
        plev:standard_name = "air_pressure" ;
        plev:must_have_bounds = "no" ;
        plev:bounds = "N/A" ;
        plev:positive = "down" ;
        plev:GRIB_id = 100s ;
        plev:GRIB_name = "hPa" ;
        plev:actual_range = 0., 0. ;

I wonder if this error might have something to do with giving plev the coordinate (plev) when it is a single level variable?

charliepascoe commented 3 years ago

[height_levels]: FAILED:: height coordinate not found This error applies to the following file: tas_Aday_CCSRNIES-MIROC32_refD1_r1i1p1f1_gn_196001-201812.nc