The sample code for showcasing FORWARD computation (in the K axis) calls mult_upward with origin=(nhalo,nhalo,1). The print statement differs in the z-value and shows origin=(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:
[ ] My code follows the style guidelines of this project
@FlorianDeconinck isn't there automatic linting for PRs?
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules
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: