Closed benbovy closed 8 years ago
This issue appears to only be linked to 0.5_0.666 resolution. I now have GEOS-Chem nested running at 0.25_0.3125 and PyGchem/Iris has no issues reading outputted ctm.bpch files. Issue with 0.5*0.666 ctm.bpch files remains apparent.
Actually, the issue seems to appear when loading a bpch file in which the 1st datablock is a 2-dimensional field with origin != (1, 1, 1).
When loading a bpch file into iris cubes, the 1st datablock in the file was taken as reference in order to avoid creating new (duplicate) iris coordinates for each datablock.
It should now be fixed in fa0d2e59ea4d666a416751ba16fbcf110c8294f5. I implemented a basic cache system to create and assign coordinates to new created cubes.
Can you tell me if it is working with your data (use the pygchem's master branch) before I close the issue?
Thanks for taking a look.
On updating to the latest PyGChem master branch. The previous error message no longer appears, however a new error is present ( see output below).
The script being used to test this: https://github.com/tsherwen/AC_tools/blob/master/bpch2netCDF.py
Traceback (most recent call last):
File "species_surface_mean_val_3D.py", line 21, in
Oups, fixed typo in ba8976bab9bfd7b9f61bf3c80f7cefb8bf48307c. Sorry!
Great. Everything seems to be working for 0.5*0.666 now. Thanks Ben.
Loading nested data from bpch (using the iris backend) gives the following error: