You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@jagoldstein and @nadinetrahan both reported seeing this bug. Jesse believes that a bug might have been introduced in InVEST 3.8.9, as earlier InVEST results seemed okay.
Jesse:
I noticed mine looks buggy in my latest run with v3.14.1. It doesn't match my ArcPro raster math result (summing the 12 monthly QFs... which looks good).
QF outputs from the previous times I used this model look good with earlier versions of InVEST, so I'm wondering if a bug was introduced. Otherwise, something must be off with my inputs.
the range of values is way too high too: 5.4e7 - 4.2e5 versus the range of sums I calculated 0 - 4156
[ QFi summed via ArcGIS | QFi summed from InVEST | QFi summed from InVEST]
The text was updated successfully, but these errors were encountered:
I haven't looked into verifying when this bug might have been introduced, but the current problem was with a numpy.sum call used by pgp.raster_map. Without specifying the axis for the numpy.sum call, it was summing across the whole array for the block and not doing a pixelwise sum.
@jagoldstein and @nadinetrahan both reported seeing this bug. Jesse believes that a bug might have been introduced in InVEST 3.8.9, as earlier InVEST results seemed okay.
Jesse:
[ QFi summed via ArcGIS | QFi summed from InVEST | QFi summed from InVEST]
The text was updated successfully, but these errors were encountered: