-
Notifications
You must be signed in to change notification settings - Fork 3
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
Floating point constants get interpreted as doubles #287
Comments
jdries
added a commit
that referenced
this issue
May 2, 2024
jdries
added a commit
that referenced
this issue
May 2, 2024
jdries
added a commit
that referenced
this issue
May 3, 2024
jdries
added a commit
that referenced
this issue
May 6, 2024
jdries
added a commit
to Open-EO/openeo-geopyspark-driver
that referenced
this issue
May 6, 2024
jdries
added a commit
to Open-EO/openeo-geopyspark-driver
that referenced
this issue
May 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Python always works in float64 by default, so when a user uses a constant like 1.0 in a computation, the result ends up in float64, even if this is not required by the precision provided.
To save memory, it seems better to be more conservative and try to stay in float32 if possible.
Part of the problem is also caused by the implementation of array_create, which does not force datatypes to something constant.
The text was updated successfully, but these errors were encountered: