Fix x, y order with numpy.mgrid usage #2121
Merged
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.
As discussed in #2038 with @larrybradley and illustrated here, the correct way to use np.mgrid to create coordinate arrays
x
andy
isy, x = np.mgrid[0:100, 0:200]
.For np.meshgrid it is
X, Y = np.meshgrid(x, y)
for the defaultindexing='xy'
order.This PR fixes a few cases in the modeling tests and docs where the wrong order was used.