-
Notifications
You must be signed in to change notification settings - Fork 93
Last minute "above_surface_pressure below_surface_pressure" coord removal #1839
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1839 +/- ##
=======================================
Coverage 98.30% 98.30%
=======================================
Files 107 107
Lines 10598 10598
=======================================
Hits 10418 10418
Misses 180 180 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
11396a8
to
100bf52
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Needs a unit test at least though.
except CoordinateNotFoundError: | ||
coord = None | ||
|
||
if coord: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add at least one unit test showing that this section does what it should. I don't understand why Codacy hasn't picked up on this too, but that's a separate issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because it's private?
I have pushed up a unittest. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks fine. Just one tiny suggestion.
Co-authored-by: Stephen Moseley <stephen.moseley@metoffice.gov.uk>
Thanks Stephen. The fresh suite run looks good too 👍 (I wanted to double check) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy that this fixes the issue 👍
Thanks both :) |
@cpelley: You should have waited for the second accepting review before merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy with this change, although as it has already been merged, there isn't a tick-box to document this any more.
* master: Mobt411 sphinx (metoppv#1837) Add option to suppress use of ECC-bounds when converting to realizations (metoppv#1838) Last minute "above_surface_pressure below_surface_pressure" coord removal (metoppv#1839)
Removal of "above_surface_pressure below_surface_pressure" coord by re-introducing the original NaN values. This is done within the standardise plugin.
Closes https://github.com/MetOffice/improver_suite/issues/1523
Background
impr_engl_temp_plev_standardise
task is now failing in fpostest (release) with out of memory (OO Killer). This is due to a change in how the data is now represented via stage.Below that of the surface altitude we used to set to NaNs in the data. Now a flag (kind of a mask) is used instead to indicate which values are above/below the surface level pressure.
The file size has then doubled due to this 4D flag coordinate.
At int8 of dimension (18, 33, 960, 1280), that's an extra 730MB
The easiest thing to do last minute might be to reduce the pool size to say half (with data being ~twice the size).
This was attempted in https://github.com/MetOffice/improver_suite/pull/1519
Unfortunately we suspect dask might be at play here as the memory overhead doesn't correspond to what we might expect (doesn't reflect the increase in file size). This is to be confirmed (in slower, less priority timescales).
Given time constraints, we hope to now instead remove this coordinate by re-applying it to the data as its previous NaN value representation.
Flag values background in cf conventions here