scoringutils

scoringutils copied to clipboard

## Description This PR closes #824. Not quite sure whether the lifecycle svgs should go as well? 🤷 We're not using them at the moment. [Describe the changes that you...

nikosbosse

Create forceast super class

2

## Description This PR closes #. As discussed in #791, this PR adds an additional forecast super class and replaces the current `print` method with it. I also slightly updated...

nikosbosse

Should `score()`/`apply_metrics()` return warning about failed metrics in a batch?

1

Should we also print the warnings in a batch instead of eagerly at the time of occurrence? They could easily get lost in the other warnings as the functions are...

jamesmbaazam

Consider the following example: `observed

nikosbosse

Implement ways to immediately warn when a forecast object becomes invalid

6

> I see it has been discussed a bit in but I am uncomfortable with the fact we re-validate the class in the `print()` method. Not just because it’s inefficient...

nikosbosse

Reduce number of `try()`, `suppressMessages()`, `suppressWarnings()` used in the package

1

> scoringutils codebase contains a lot of try(), suppressMessages(), suppressWarnings(). This is likely the symptoms that a refactoring or redesign is necessary. In particular, one potential cause can be the...

nikosbosse

Package scaffolding

1

> The Metrics R package doesn’t seem actively maintained and may present a risk to the long-term sustainability of the project. From what I can tell, we only use it...

nikosbosse

Update `plot_heatmap()` to be a table instead of a plot

1

I believe I mentioned it in the past but I am still uncomfortable with the `plot_heatmap()` function. The output here should be a table, not a plot. This comes with...

nikosbosse

> Am I correct that most figures in `man/figures/` are no longer used? If so, they should be removed. _Originally posted by @Bisaloo in https://github.com/epiforecasts/scoringutils/pull/791#pullrequestreview-2003401135_

nikosbosse

> I wonder if there should be a `forecast` [abstract class](https://en.wikipedia.org/wiki/Abstract_type), from which `forecast_binary`, `forecast_point`, etc. would inherit. In the docs and exported functions (e.g., `is_forecast()`, `validate_forecast()`), things appear as...

nikosbosse