Skip to content

temporary fix to an issue with cube intersection when cube has bounds #800

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.

Sign up for GitHub

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

Closed
valeriupredoi wants to merge 3 commits into from
Closed

temporary fix to an issue with cube intersection when cube has bounds #800

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d4598d9
temporary fix to an issue with cube intersection when cube has bounds
valeriupredoi Sep 30, 2020
a6e282b
that'll break Codacy but better to have the full link cheers
valeriupredoi Sep 30, 2020
f64a2a1
chop line
valeriupredoi Sep 30, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions esmvalcore/preprocessor/_area.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,11 @@ def extract_region(cube, start_longitude, end_longitude, start_latitude,
latitude=(start_latitude, end_latitude),
ignore_bounds=True,
)
# delete bounds: kluge for issue 799
# TODO remove the bounds handling after iris fix
region_subset.coord("longitude").bounds = None
region_subset = region_subset.intersection(longitude=(0., 360.))
region_subset.coord("longitude").guess_bounds()
return region_subset
# Irregular grids
lats = cube.coord('latitude').points
Expand Down