Closed ledm closed 1 year ago
This was changed 2019-11-15 in the tables. The original change in the CV was on 2019-10-22 and released as 6.2.39.2.
we can probably fix this with a temporary mapping in config-developer.yml
but really, it's a bad case of old ESGF data structure - I will email @agstephens and Ruth Petrie about it
OK email sent to Ag and Ruth (and you two troublemakers too) :beer:
OK email sent to Ag and Ruth (and you two troublemakers too) beer
nevermind, I'm being silly - yes, the (new) table is correct and in line with the Jasmin path :beer:
As a workaround for this issue (once there is a new release of the CMIP6 CMOR tables and we've updated our copy to use it) you can specify the correct institute in the dataset definition in the recipe.
We are now using the latest release of the CMOR tables (6.9.33),
The CMIP6 model dataset for the model
ACCESS-CM2
is stored on jasmin under the institude ID:CSIRO-ARCCSS
, but recorded asCSIRO-ARCCSS-BoM
in ESMValCore inCMIP6_CV.json
.ie the paths to this model are:
However, in
esmvalcore/cmor/tables/cmip6/Tables/CMIP6_CV.json
, we record the institude ID for this model to be :So ESMValTool is looking for this dataset in the non-existant folder: