feat: support forecast_limit_lower_bound and forecast_limit_upper_bou…#1305
Merged
feat: support forecast_limit_lower_bound and forecast_limit_upper_bou…#1305
Conversation
…nd in ARIMA_PLUS (and ARIMA_PLUS_XREG) models
…es into b384509112-forecast-limit-bounds
…pis/python-bigquery-dataframes into b384509112-forecast-limit-bounds
…pis/python-bigquery-dataframes into b384509112-forecast-limit-bounds
tswast
approved these changes
Apr 2, 2025
| holiday_region="US", | ||
| clean_spikes_and_dips=False, | ||
| adjust_step_changes=False, | ||
| forecast_limit_upper_bound=2, |
Contributor
There was a problem hiding this comment.
I wonder if the failure on fit is because total_visits is greater than 2 in the training data? Maybe we need to pick a larger value for this?
Aternatively:
- Use different training data where we know it's between certain values
- Use a method like https://pandas.pydata.org/pandas-docs/version/1.0/reference/api/pandas.Series.clip.html to keep the training data between certain values.
shobsi
reviewed
Apr 3, 2025
bigframes/ml/forecasting.py
Outdated
| The forecasting limit ensures that forecasts stay within limits. | ||
|
|
||
| forecast_limit_lower_bound (float or None, default None): | ||
| The lower bound of the forecasting values where the minimum value allowed is 0. When you specify the FORECAST_LIMIT_LOWER_BOUND option, all of the forecast values must be greater than the specified value. |
Contributor
There was a problem hiding this comment.
we should use the param name being introduced here instead of the uppercase (which is documented in the BQML docs)
tswast
reviewed
Apr 16, 2025
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
4 participants
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.
…nd in ARIMA_PLUS (and ARIMA_PLUS_XREG) models
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> 🦕