Closed nikosbosse closed 4 months ago
To make it more explicit what the function does (i.e. bundle all checks that are common to all forecast classes), we should rename the function. This was discussed in https://github.com/epiforecasts/scoringutils/pull/772.
Canidates:
validate_forecast_all()
validate_forecast_generic()
validate_forecast_general()
I think my preference order is .._generic > ..._general > .._all but I don't feel that strongly about it
.._generic
..._general
.._all
To make it more explicit what the function does (i.e. bundle all checks that are common to all forecast classes), we should rename the function. This was discussed in https://github.com/epiforecasts/scoringutils/pull/772.
Canidates:
validate_forecast_all()
validate_forecast_generic()
validate_forecast_general()