-
Notifications
You must be signed in to change notification settings - Fork 48
feat: support forecast_limit_lower_bound and forecast_limit_upper_bou… #1305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
@@ -107,6 +107,8 @@ def test_arima_plus_model_fit_params(time_series_df_default_index, dataset_id): | |||
holiday_region="US", | |||
clean_spikes_and_dips=False, | |||
adjust_step_changes=False, | |||
forecast_limit_upper_bound=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.
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.
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. |
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.
we should use the param name being introduced here instead of the uppercase (which is documented in the BQML docs)
…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> 🦕