Add TimeSeries.has_nan property to check for NaN values - #3195
Open
webzuweb wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Partial contribution towards #1278.
Summary
Adds a
has_nanproperty toTimeSeriesthat indicates whether the series contains any NaN values. This was explicitly suggested in #1278 ("Might be also useful to create a TimeSeries property which indicates if there are some nan in the time series") and is useful for users deciding whether a series can be passed to models/historical forecasts that don't handle NaNs.Changes
darts/timeseries.py: newhas_nanproperty (np.isnan(self._values).any()), placed alongside the otherhas_*properties.darts/tests/test_timeseries.py: newtest_has_nancovering univariate with NaN, clean univariate, integer series, and multivariate with NaN.Verification