Fix typo in print statement (FORWARD example) #62
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.
Description
The sample code for showcasing FORWARD computation (in the K axis) calls
mult_upward
withorigin=(nhalo,nhalo,1)
. The print statement differs in the z-value and showsorigin=(nhalo,nhalo,0)
. This can be confusing for developers which just skim the output and don't read the code that is actually executed. The subsequent white-space change is only for consistency.How Has This Been Tested?
I ran this notebook locally.
Checklist:
@FlorianDeconinck isn't there automatic linting for PRs?