-
Notifications
You must be signed in to change notification settings - Fork 904
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
Fix/metrics #129
Merged
Merged
Fix/metrics #129
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
aac629d
fix(metrics/mase): fix MASE. The scale use insample data instead of o…
Droxef 845709a
docs(metrics/mase): Add definition of insample in docs. Add check for…
Droxef 18f6ccb
test(metrics/mase): Modify mase test and test insample date
Droxef dd6c9b1
fix(metrics/mase): Change seasonality test on correct series
Droxef 61ec34f
style(metrics/smape): Fix lint issues
Droxef 40adc66
docs(metrics/smape): correct docs for smape and add raise for mase
Droxef b9247bb
test(metrics/smape): Add tests for the new smape metrics
Droxef dc18afc
Merge branch 'develop' of https://github.com/unit8co/darts into fix/m…
Droxef 2e1c04f
docs(MASE): better explanation of insample
Droxef 46fffa8
docs(sMAPE): correct the raises explanation
Droxef c217082
Merge branch 'develop' of https://github.com/unit8co/darts into fix/m…
Droxef e997440
docs(mase): more precise description for insample series
Droxef 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 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 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.
Similarly to my comment on @pennfranc PR I believe that we should split these tests and try to keep a single test for a single assert or at least a single test for a single failure reason. (each test method name should describe what it is testing). The problem with the current tests is that if mape is failing we have no idea if it is only mape or other methods will also fail like smape also I believe the reason for failing is not very clear each time. Let me know what you think :)