-
Notifications
You must be signed in to change notification settings - Fork 128
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
recipe_perfmetrices crashes due to standard name error #1561
Comments
perfmetrics is a monster and would really not want to run it - can you pls tell us what's the offending dataset (full specs, so I can look it up on Jasmin too, might be that the actual data file changed in the meantime) 🍺 |
Investigating... 🔍 The variable should be |
It is a legal standard_name, so it looks like an Iris problem. Which version are you using? From last CF table:
|
|
Another hint:
|
It has the alias in its standard_names XML... Iris should accept it |
Apparently it is failing to apply a fix to |
It is the automatic one correcting the standard_name when it does not match the CMOR tables. But Iris is complaining it is not legal for some reason |
right so that dam file has got no
it has, however, an
and |
BTW where is the entry for |
Line 1847 |
nevermind I'm blind 🙈 |
Iris issue because it is a legal standard_name and should not be treated as invalid. |
we battling in legalities @jvegasbsc 😁 is that |
But it used to work, were there changes in the fix files? |
I am actually using |
This means you could reproduce the issue? |
yes, outside esmvaltool, see #1561 (comment) |
Iris uses that attribute when it detects a standard_name that is not part of the valid list, so is Iris not the CMOR who is using it. In our case, this is wrong because it is a valid standard_name, search it here http://cfconventions.org/Data/cf-standard-names/71/build/cf-standard-name-table.html. We can also reproduce the error without any file: >>> import numpy as np
>>> import iris.cube
>>> cube = iris.cube.Cube(np.arange(10))
>>> cube.standard_name = 'atmosphere_optical_thickness_due_to_pm1_ambient_aerosol'
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/Earth/jvegas/.conda/envs/esmvaltool/lib/python3.6/site-packages/iris/_cube_coord_common.py", line 206, in standard_name
self._standard_name = get_valid_standard_name(name)
File "/home/Earth/jvegas/.conda/envs/esmvaltool/lib/python3.6/site-packages/iris/_cube_coord_common.py", line 58, in get_valid_standard_name
name))
ValueError: 'atmosphere_optical_thickness_due_to_pm1_ambient_aerosol' is not a valid standard_name
>>> cube.standard_name = 'atmosphere_optical_thickness_due_to_pm1_ambient_aerosol_particles'
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/Earth/jvegas/.conda/envs/esmvaltool/lib/python3.6/site-packages/iris/_cube_coord_common.py", line 206, in standard_name
self._standard_name = get_valid_standard_name(name)
File "/home/Earth/jvegas/.conda/envs/esmvaltool/lib/python3.6/site-packages/iris/_cube_coord_common.py", line 58, in get_valid_standard_name
name))
ValueError: 'atmosphere_optical_thickness_due_to_pm1_ambient_aerosol_particles' is not a valid standard_name
>>> cube.standard_name = 'latitude'
>>> |
yep, same here, assigning it to the GFDL-CM3 cube:
@jvegasbsc is correct and I have to retract my support for |
funny thing is that name is actually present in |
ok the problem is in
|
@jvegasbsc have a look at SciTools/iris#3677 (comment) and then my cheeky comment SciTools/iris#3677 (comment) - do you mind taking care of it? 🍺 |
Setting an Iris development environment right now... |
Any news here? |
@mattiarighi Just merged @jvegasbsc PR SciTools/iris#3679 on Thanks Javier 🍻 This change will be included in the forthcoming We're aiming to get Cheers 😄 |
Thanks @bjlittle |
Remove from the milestone, since we will not get Iris 3 before ESMValTool v2.0 release. |
I think this problem has been fixed by now. Is any work on this still needed? |
@remi-kazeroni have you seen this happen in @bouweandela's last run of all the recipes from yesterday? |
The recipe_perfmetrics_CMIP5.yml was not fully ran in #2354 since the automoatic download didn't work due to the unavailable ESGF node (see comment). I have made a few attempts to run the recipe enabling the automatic download feature:
So I guess we could uncomment the "Needs Iris3.0" bit to close this issue. But I'm not sure what to do with the error related to the mmm. |
@remi-kazeroni, ESMValGroup/ESMValCore#1372 has been resolved. Could you try again? Don't forget to re-create the environment to get the second release candidate of the core. |
I have just recreated an environment with ESMValCore 2.4.0rc2 and rerun the |
Sounds good! |
Not sure what is causing the problem.
The last successfull test with this recipe was on Feb 18.
The text was updated successfully, but these errors were encountered: