-
Notifications
You must be signed in to change notification settings - Fork 487
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
Seasonality modularization #1141
Conversation
Model Benchmark
|
Hey @karl-richter |
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #1141 +/- ##
==========================================
+ Coverage 90.17% 90.24% +0.06%
==========================================
Files 30 33 +3
Lines 4966 5000 +34
==========================================
+ Hits 4478 4512 +34
Misses 488 488
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Good call @alfonsogarciadecorral , I adressed your comment and create a Global and Local class of Seasonality. |
self.season_params = nn.ParameterDict( | ||
{ | ||
# dimensions - [no. of quantiles, num_seasonalities_modelled, no. of fourier terms for each seasonality] | ||
name: init_parameter(dims=[len(self.quantiles)] + [self.num_seasonalities_modelled] + [dim]) | ||
for name, dim in self.season_dims.items() | ||
} | ||
) |
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.
In a future PR, we may want to have a seasonality object per period instantiated - thus a class should not need know the num_seasonalities_modelled
.
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.
Great work!
🔬 Background
🔮 Key changes
📋 Review Checklist
Please make sure to follow our best practices in the Contributing guidelines.