Skip to content
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

Understanding fourier_order #409

Closed
Utsav2 opened this issue Jan 10, 2018 · 2 comments
Closed

Understanding fourier_order #409

Utsav2 opened this issue Jan 10, 2018 · 2 comments

Comments

@Utsav2
Copy link

Utsav2 commented Jan 10, 2018

Thanks for making the package!

As a beginner, i'm not sure what the fourier_order parameter can help with. Could someone shed some light on it in the docs?

@bletham
Copy link
Contributor

bletham commented Jan 23, 2018

We should put some examples of this in the documentation.

In short, a higher order means we have higher frequency terms and so will be able to fit more quickly-changing and complex seasonality patterns.

This figure from Wikipedia shows a Fourier series approximation to a square wave, with 1, 2, 3, and 4 components: https://en.wikipedia.org/wiki/Fourier_series#/media/File:Fourier_Series.svg . You can see that as the order is increased, the Fourier series is able to better represent the quick change of the square wave. The downside of using a very high order is just that it is more terms in the model and so overfitting becomes a risk.

The default of 10 typically is appropriate for seasonality on the scale of a year. If it looks like your seasonality effect changes very quickly and the Prophet seaosnality estimate is lagging and not able to capture it all, then try increasing the order.

@bletham
Copy link
Contributor

bletham commented Jun 7, 2018

Now described in documentation here: https://facebook.github.io/prophet/docs/seasonality,_holiday_effects,_and_regressors.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants