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
Is your feature request related to a problem? Please describe.
Right now the data volume might get fairly big since we're not forcing any specific datatypes or bit depths and just relying on the 64-bit python default. We'd like to reduce this to lighten the burden on the SSC and future users, by (optionally) forcing the data types to be 32-bit floats for the image and error extensions, and a 16-bit integer for the DQ extension.
Describe the solution you'd like
In order to keep our options open, let's implement this with a drpconfig keyword that toggles us to force the bit-depth described above. We can leave it as True (i.e. forcing bit-depth) by default.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Right now the data volume might get fairly big since we're not forcing any specific datatypes or bit depths and just relying on the 64-bit python default. We'd like to reduce this to lighten the burden on the SSC and future users, by (optionally) forcing the data types to be 32-bit floats for the image and error extensions, and a 16-bit integer for the DQ extension.
Describe the solution you'd like
In order to keep our options open, let's implement this with a drpconfig keyword that toggles us to force the bit-depth described above. We can leave it as True (i.e. forcing bit-depth) by default.
The text was updated successfully, but these errors were encountered: