You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... WARNING /work/bd0854/b309059/utils/mambaforge/envs/esmvaltool/lib/python3.11/site-packages/iris/fileformats/netcdf/saver.py:2670: IrisDeprecation: Saving to netcdf with legacy-style a
180
+
ttribute handling for backwards compatibility.
181
+
This mode is deprecated since Iris 3.8, and will eventually be removed.
182
+
Please consider enabling the new split-attributes handling mode, by setting 'iris.FUTURE.save_split_attrs = True'.
183
+
warn_deprecated(message)
184
+
180
185
... CMORization of dataset FLUXCOM finished!
181
186
... Formatting successful for dataset FLUXCOM
187
+
182
188
~~~
183
189
{: .output}
184
190
@@ -629,17 +635,23 @@ If we now run the test recipe on our newly 'CMORized' data,
629
635
esmvaltool run recipe_check_fluxcom.yml --config_file <path to config-user.yml> --log_level debug
630
636
```
631
637
632
-
it should be able to find the correct file, but it does not succeed yet. The first
633
-
thing that the ESMValTool CMOR checker brings up is:
638
+
it should be able to find the correct file, but it does not succeed yet. The ESMValTool CMOR checker
639
+
brings up is:
634
640
635
641
~~~
636
-
iris.exceptions.UnitConversionError: Cannot convert from unknown units. The
637
-
"units"attribute may be set directly.
642
+
esmvalcore.cmor.check.CMORCheckError: There were errors in variable GPP:
643
+
GPP: units should be kg m-2 s-1, not unknown
644
+
lon: standard_name should be longitude, not None
645
+
lat: standard_name should be latitude, not None
646
+
lon: units should be degrees_east, not unknown
647
+
lon: has values < valid_min = 0.0
648
+
lat: units should be degrees_north, not unknown
649
+
GPP: does not match coordinate rank
638
650
~~~
639
651
{: .error}
640
652
641
-
If you look closely at the error messages, you can see that this error concerns
642
-
the units of the coordinates. ESMValTool tries to fix them automatically,
653
+
If you look closely at the error messages, you can see that these error concern
654
+
e.g. the units of the coordinates. ESMValTool tries to fix them automatically,
643
655
but since no units are defined on the coordinates, this fails.
644
656
645
657
The cmorizer utilities also include a function called `fix_coords`, but before
@@ -696,7 +708,7 @@ The next error is:
696
708
697
709
~~~
698
710
esmvalcore.cmor.check.CMORCheckError: There were errors in variable GPP:
699
-
Variable GPP units unknown can not be converted to kg m-2 s-1 in cube:
0 commit comments