Fix major basins behavior #708
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The choice of major basins is performed on main, on an extended grid that is used to compute the connectivity in case of a Periodic direction. It might be, therefore, that large basins such as the Caspian sea are repeated within the extended grid, and are removed from the extended grid without changing the interior of the bottom height which is what we actually want to mask out.
In this PR we still compute the connectivity (the labels) using an extended grid, but we rank the basins only on the labels in the interior of the grid, correcting the behavior of
major_basins.For example the output of this script:
on main:

on this PR:

cc @taimoorsohail