Describe the changes you've made

• predict_model displays the test metrics now when verbose is set to True (default)
• Note that this is slightly different from the regression.classification case. There are several corner cases such as:
  • If the model has not been finalized, prediction match y_test
  • If the model has been finalized, predictions will not match the indices from y_test (metrics display NaN in that case)
  • Also, the user can use a different fh length in predict compared to what was used in setup. In this case, only the common indices in prediction and test are used to compute the metrics.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, local variables)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Unit test has been added

Describe if there is any unusual behaviour of your code

Warnings are issued for all corner cases identified above

Checklist:

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.