Fix LocScaleReparam, log params in backtest() #2365
Merged
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.
Fixes a naming bug in
LocScaleReparam
whereby all loc-scale-reparameterized sites shared a single centeredness parameter. After this PR each such site learns a separate centeredness parameter (as originally intended).Also adds param logging to
contrib.forecast.evaluate.backtest()
, which logging led me to discover the loc-scale bug. After this PR all scalar params will be printed and saved (as floats) to backtest results. My immediate motivation is to inspect global parametersstability
,skew
anddf
ofStable
andStudentT
distributions.Tested