-
Notifications
You must be signed in to change notification settings - Fork 80
Fix BasePipeline.forecast
when prediction intervals are estimated on history data with presence of NaNs
#1291
Conversation
🚀 Deployed on https://deploy-preview-1291--etna-docs.netlify.app |
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## master #1291 +/- ##
==========================================
+ Coverage 87.74% 88.08% +0.34%
==========================================
Files 187 187
Lines 10859 10886 +27
==========================================
+ Hits 9528 9589 +61
+ Misses 1331 1297 -34
... and 3 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
f"There are NaNs in target on time span from {min_timestamp} to {max_timestamp}. " | ||
f"It can obstruct prediction interval estimation on history data." | ||
) | ||
if np.any(non_nan_counts < 2): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is it exactly 2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is the minimal value that can give non-zero result.
Before submitting (must do checklist)
Proposed Changes
Look #899.
Closing issues
Closes #899.