Added check to catch masked constants in read_interpolated_variable #247
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.
This is a fix for PR #82 :
The problem is that if for any reason the
test_variable
used inread_interpolated_variable
is masked,isinstance(test_variable, Iterable)
will returnTrue
butvalue_length=len(test_variable)
will throw the errorTypeError: len() of unsized object
. This is because the masked value is of typenp.ma.core.MaskedConstant
, which inherits the property ofIterable
from somewhere, but it's actually not iterable.This PR adds an additional check for
np.ma.core.MaskedConstant
and setsvalue_length=1
if the value is masked.