-
Notifications
You must be signed in to change notification settings - Fork 285
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
Problem with loading mask in iris 2 when missing_value
is wrong
#3269
Comments
As described this all sounds very odd - Iris 1.13 should on no account ignore
Unfortunately I can't get at that file with any particular immediacy .. Can you maybe just copy us an |
shoot! sorry @pp-mo hadn't realized about Jasmin access, so used to working on it it's like a second nature to me 😁 Here's the ncdump:
|
In order to maintain a backlog of relevant issues, we automatically label them as stale after 500 days of inactivity. If this issue is still important to you, then please comment on this issue and the stale label will be removed. Otherwise this issue will be automatically closed in 28 days time. |
This stale issue has been automatically closed due to a lack of community activity. If you still care about this issue, then please either:
|
Hi guys, here's one obscure one for you: we (the ESMValTool guys) are working with hundreds of models and a lot of them have metadata or data issues and we fix them internally, but we found one that albeit super easy to fix, it may uncover a hidden bug in
iris
. Here's the synopsys:/badc/cmip5/data/cmip5/output1/BNU/BNU-ESM/historical/mon/aerosol/aero/r1i1p1/files/od550aer_20120504/od550aer_aero_BNU-ESM_historical_r1i1p1_185001-200512.nc
cube.data.mask
structure correctly; iris 2.2.0 doesn't, it builds no mask and assigns 1e36 values as valid data points;_FillValue
andmissing_value
netcdf attributes both with 1e+20f values (CMOR standard); in effect the missing values' actual numeric values in the data array are 1e36 and are interpreted by iris 2.2.0 as valid valuesmissing_value
to 1e36 in the file (via saycdo setmissval
) then iris 2 will create the correct mask; this is a bit of a twisted situation because the_FillValue
's will then have to be reverted to 1e+20f at save point to comply with CMOR standards.My take on this would be if you guys reinstated the same approach to missing data as it was done in iris 1 it would be great! But I understand why the issues due to partial support of dask+masks, so if you could look into this case in particular case and see what can be done, that'd be awesome! Cheers muchly!
The text was updated successfully, but these errors were encountered: