Raise warning in QuantileForecast.mean
when mean is not there
#2843
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.
Issue #, if available:
Description of changes: The
QuantileForecast
class falls back to the median when asked for the mean but the mean is not among the stored values. This is motivated by some downstream evaluation metrics using the mean of the predicted distribution, but some models only producing quantiles as forecasts.To me this is pretty clearly not the right thing to do, and potential source of confusion: instead, it should be clear how to configure the evaluation to use the predicted median instead of the mean, if that's what the user wants.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup