Fix dask compatibility in blackbody functions #74
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was writing the MERSI-2 L1B reader and needed to use the rad2temp function. I noticed that when dask arrays were passed they were being converted to a numpy array. This PR fixes the usage with the least amount of changes possible.
The biggest difference is that in the
planck
function a masked array was being used with-9
as the original sentinel value. As far as I could tell the masked array was being used for two reasons: to makemin/max
calls ignore the masked values and to later use the.mask
to replace masked values with NaN. I switched this to use NaN right away instead of-9
and to only print out min/max debug information when the input is an numpy array.I'm marking this as a bug fix because although its a feature, it is more about fixing a working function so it returns what I want.
git diff origin/master **/*py | flake8 --diff