-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ArrayTile: wrong argument order in combineDouble + ConstantTile #3257
Labels
Comments
jdries
added a commit
to Open-EO/openeo-geopyspark-driver
that referenced
this issue
Jun 17, 2020
jdries
added a commit
to Open-EO/openeo-geopyspark-driver
that referenced
this issue
Jun 19, 2020
soxofaan
added a commit
to soxofaan/geotrellis
that referenced
this issue
Jul 22, 2020
2 tasks
soxofaan
added a commit
to soxofaan/geotrellis
that referenced
this issue
Jul 22, 2020
soxofaan
added a commit
to soxofaan/geotrellis
that referenced
this issue
Jul 22, 2020
Signed-off-by: Stefaan Lippens <[email protected]>
pomadchin
added a commit
that referenced
this issue
Aug 4, 2020
Signed-off-by: Stefaan Lippens <[email protected]> Co-authored-by: Grigory <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In ArrayTile, combineDouble looks like:
case ct: ConstantTile => ct.combineDouble(this)(f)
compare to combine:
case ct: ConstantTile => ct.combine(this)((z1, z2) => f(z2, z1))
So the argument order in combineDouble is (z1,z2). When using this in combination with the non-commutative 'Subtract' function, results are simply wrong. (So I believe this can be considered a pretty major issue.)
The text was updated successfully, but these errors were encountered: