-
Notifications
You must be signed in to change notification settings - Fork 73
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
Update Model Complexity Computations #171
Comments
|
Overall weighting (weights should be 1, each model uses its own weight and defines its own complexity)
|
antoinecarme
added a commit
that referenced
this issue
Jul 1, 2021
Overall weighting (weights should be 1, each model uses its own weight) Now, the complexity of a model is the sum of the complexities of all its components
New values
|
New weighting
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PyAF uses a notion of complexity for each component of the model (signal transformation, trend, cycle.seasonal, AR, ... )
The complexity value is used when two models have almost the same performance (MAPE) , the less complex model is kept in this case (Occam's razor).
By introducing new models (Croston, XGBoost, LightGBM), the notion of complexity has to be dependent of each component and the overall weighting is no longer relevant.
this change will not impact too much the output of PyAF as the complexity is not always used in the model selection.
The text was updated successfully, but these errors were encountered: