-
Notifications
You must be signed in to change notification settings - Fork 66
[ML] Implements an absolute goodness-of-fit test to accept a change #21
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
Merged
tveasey
merged 9 commits into
elastic:feature/forecast-enhancements-part-2
from
tveasey:feature/change-modelling-part-3
Mar 26, 2018
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
9b91ed5
Implement an absolute test for suitability of change hypotheses
tveasey 0dbf15b
Remove debug
tveasey 628eb53
Fix restore
tveasey a9531fa
Merge branch 'feature/forecast-enhancements-part-2' into feature/chan…
tveasey c388c9b
Smooth decision to accept change over various factors
tveasey a87b74e
Merge branch 'feature/forecast-enhancements-part-2' into feature/chan…
tveasey 030d613
Merge branch 'feature/forecast-enhancements-part-2' into feature/chan…
tveasey fbb511f
Bad merge
tveasey d1e466e
Explicitly initialise likelihoods
tveasey File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Going forward I think it would be best practice to use the 'override' keyword in cases such as this.
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.
Visual Studio 2013 doesn't support
override
, so bear in mind this will create a backporting headache. I agree for 7.0-only code we should use it though.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.
I noticed using
override
on one method generates warnings for every other virtual function that is not markedoverride
(-Winconsistent-missing-override) in the compilation unit. It should probably be done in a single commitThere 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.
I'm inclined to agree. I think this is something we should adopt, but also let's make this in a single change and target at 7.0 only as there would be no need to back port.