epiforecasts/scoringutils: scoringutils version 1.1.0

A minor update to the package with some bug fixes and minor changes.

• Removed the on attach message which warned of breaking changes in 1.0.0.
• Renamed the metric argument of summarise_scores() to relative_skill_metric. This argument is now deprecated and will be removed in a future version of the package. Please use the new argument instead.
• Updated the documentation for score() and related functions to make the soft requirement for a model column in the input data more explicit.
• Updated the documentation for score(), pairwise_comparison() and summaris_scores() to make it clearer what the unit of a single forecast is that is required for computations
• Simplified the function plot_pairwise_comparison() which now only supports plotting mean score ratios or p-values and removed the hybrid option to print both at the same time.

• Missing baseline forecasts in pairwise_comparison() now trigger an explicit and informative error message.
• The requirements table in the getting started vignette is now correct.
• Added support for an optional sample column when using a quantile forecast format. Previously this resulted in an error.

• Fix 223 issue with add_coverage by @seabbs in https://github.com/epiforecasts/scoringutils/pull/234
• Test explicitly on minimum supported R version by @Bisaloo in https://github.com/epiforecasts/scoringutils/pull/236
• use deparse instead of deparse1 by @nikosbosse in https://github.com/epiforecasts/scoringutils/pull/237
• Specify which column name clashes with metrics by @Bisaloo in https://github.com/epiforecasts/scoringutils/pull/239
• Fix separate results by @nikosbosse in https://github.com/epiforecasts/scoringutils/pull/243
• fix pit histogram plot in #240 by @nikosbosse in https://github.com/epiforecasts/scoringutils/pull/247
• Fix requirements table in getting-started vignette by @damonbayer in https://github.com/epiforecasts/scoringutils/pull/249
• Reformatting to comply with JSS requirements by @nikosbosse in https://github.com/epiforecasts/scoringutils/pull/251
• Fix ggplot2 update by @nikosbosse in https://github.com/epiforecasts/scoringutils/pull/252
• update test by @nikosbosse in https://github.com/epiforecasts/scoringutils/pull/254
• don't error if baseline model is not present by @sbfnk in https://github.com/epiforecasts/scoringutils/pull/250
• 1.1.0 by @seabbs in https://github.com/epiforecasts/scoringutils/pull/258
• add infra for develop branch by @seabbs in https://github.com/epiforecasts/scoringutils/pull/259
• Issue 248 by @seabbs in https://github.com/epiforecasts/scoringutils/pull/256
• Documentation: Update README by @seabbs in https://github.com/epiforecasts/scoringutils/pull/262
• Docmentation: update score and related documentation to mention the model column by @seabbs in https://github.com/epiforecasts/scoringutils/pull/260
• Feature: add enhanced treatment of sample as a protected column by @seabbs in https://github.com/epiforecasts/scoringutils/pull/261
• simplify plot_pairwise_comparison() by @nikosbosse in https://github.com/epiforecasts/scoringutils/pull/263
• Make forecast unit clearer by @nikosbosse in https://github.com/epiforecasts/scoringutils/pull/264

• @damonbayer made their first contribution in https://github.com/epiforecasts/scoringutils/pull/249

Full Changelog: https://github.com/epiforecasts/scoringutils/compare/v1.0.0...v1.1.0