-
Notifications
You must be signed in to change notification settings - Fork 57
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
Can't merge ECMWF perturbed and control forecast together as xarray since release 0.10 #33
Comments
I see. I reproduced the issue, thanks for the detailed report. The reason is that your grib files (from mutiple sources) are not compatible. Previous versions of (0.9.9 and below), we were sending each grib separately to cfgrib. Nevertheless, we do want to support this use case nicely. I will work on it during the next few days. |
We would like to make cfgrib ignore the value of the inconsistent key (namely "dataType" which is sometimes 'pf' and sometimes 'cf'). This is not yet implemented in cfgrib. I added it in climetlab and opened an issue to have it implemented in cfgrib. Would you mind checking that this solves the issue?
|
Yes, the current default behaviour of cfgrib is to raise an error when the GRIB are not consistent. The rationale is that we really do not want to change the grib file on the fly without the user deciding it explicitly. |
Ok thanks, I think that this issue can be closed when there is a new release with the fix then. |
version 0.10.3 released. |
to align with the new default in climetlab and cfgrib See ecmwf/climetlab#33 for more details
After implementing this modification, everything seems fine and I will release a new version of the plugin. Thanks for your help. |
Hi there,
Since the release 0.10.1, the EUMETNET benchmark plugin is partly broken because apparently cfgrib does not accept anymore to merge the control and perturbed ECMWF forecasts together.
I use the multi source to do that (see here), but when calling
to_xarray
, I get the following issue:So the problem seems to be that it has become more strict about the multiple values for keys, using this function
enforce_unique_attributes
.cfgrib version is
0.9.10
.How can I resolve this issue? Can I tell him to be more forgiving about the attributes uniqueness?
Thank you in advance.
To reproduce, simply install the plugin
pip install climetlab climetlab-eumetnet-postprocessing-benchmark
and run the notebook https://github.com/Climdyn/climetlab-eumetnet-postprocessing-benchmark/tree/main/notebooks/demo_ensemble_forecasts.ipynb .
The text was updated successfully, but these errors were encountered: