-
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
[refactor] Lighten forecaster.py #1255
Conversation
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 #1255 +/- ##
==========================================
+ Coverage 89.56% 89.66% +0.10%
==========================================
Files 35 38 +3
Lines 4830 4955 +125
==========================================
+ Hits 4326 4443 +117
- Misses 504 512 +8
... and 9 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
LGTM :)
Have you considered using the regular verb form e.g. split
over the progressive splitting
for the filenames? Would make it shorter, no hard feelings, just a personal preference to have it more compact.
Nice suggestion, will adapt that. |
Model Benchmark
|
Linked to #1133
🔬 Background
Currently, the
forecaster.py
is very large and contains many functions. We would like to lighten theforecaster.py
and move selected functions to other files🔮 Key changes
processing.py
,splitting.py
,transforming.py
test_unit.py
andtest_integration.py
, because they call the moved functions🔮 Future Recommendations
In a next step, the input varaibles of the moved functions should be adapted. Currently, the full model is passed as an input argument. However, for most functions the actual needed input argument can be further narrowed down.
📋 Review Checklist
Please make sure to follow our best practices in the Contributing guidelines.