Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Account for job start/end time not exactly matching forecast data points #54
Account for job start/end time not exactly matching forecast data points #54
Changes from all commits
2bb2a01
8b3b5fe
f6251b3
d876e4f
b2d5488
1158bad
60a29f0
1c14f0c
93be87c
22bb8b7
925e6c9
51bc336
b7dc142
50ff2cc
9f61ba8
02ed744
afe12b4
b26841e
62d1255
a223b1d
6930399
db76c19
50319ee
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
One potential downside of doing all the calculations in the
__getitem__
method is that it requires redoing calculations every time (I think?): as in,min
already calculates all windows, but thenw[0]
does it again etc.. An alternative would be to calculate all windows once, store it in self and only access it after that. Or are there performance benefits to doing everything 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.
Overall I think performance should not be a concern here. Even then, only the the first window is computed twice. But yes, if you were to run
min
twice, you'd compute all windows twice.