[FEAT] Additional metrics for evaluating forecasting (RMSE+ MSE) #4178
Conversation
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
|
Any reason we can't add the others from darts.metrics? |
|
No reason, just figured I would add based on user input. I will add in more if you'd like. |
|
Thats fair. Only reason I ask is because I was going to try using the sdk for a kaggle comp that used SMAPE as the scoring metric, but I noticed it wasn't an option, so I didnt use it. Having as many is both helpful and overkill. |
|
@jmaslek Added smape for you :) |
jmaslek
approved these changes
Feb 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding in
RMSEandMSEmetrics for accuracy calculations when performing backtesting on models.Twitter
In terminal:
SDK:
