fix(mfdatastorage): use appropriate fill_value for data type #1689
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 resolves a RuntieWarning from flopy doing something like this:
which shows a warning summary:
and looking at a big trace shows where/how it was raised:
pytest trace
which shows that
np.full
has an int32 type with a fill value NaN, which is not possible. This PR evaluates the numpy data type, and chooses an appropriate fill value. I'm not 100% sure what these should be, so I've chosen 0 for integer, False for boolean, and None for other types.