hubEvals 0.3.0
-
score_model_out()now handles single-model input gracefully when relative metrics are requested. Previously this errored viascoringutils("not enough comparators"); now the relative-skill columns are filled with1, matching the trivial fact that a model has skill1relative to itself. If abaselineis supplied that does not match the lone model,score_model_out()errors with a clear message (#75). -
New "Getting started with hubEvals" vignette walking through the main scoring workflows for each supported output type (quantile, mean, median, pmf nominal/ordinal, sample marginal/compound), the
relative_metricsandbaselinearguments for relative-skill scoring, and thetransformandtransform_appendarguments for scoring on transformed scales (#38). -
Fix
score_model_out()so that requestingtransform_append = TRUEwith defaultsummarize = TRUEnow correctly returns one row perscale(natural and transformed) per model, instead of silently averaging across scales (#122). -
score_model_out()now errors with a clear hubEvals message when"bias"is requested as a relative metric, instead of lettingscoringutilsfail downstream with a cryptic "all values must have the same sign" error. Bias is a signed quantity, so a geometric-mean pairwise ratio has no clean interpretation (#119). -
score_model_out()now returns a tibble (inheriting from scoringutils'scoresclass) instead of adata.table. This gives more predictable user-facing behaviour (e.g. with$access, printing, and dplyr) while keeping thescoresclass so downstream scoringutils helpers likeget_metrics()continue to work (#70). -
score_model_out()now errors when no requested metric produces a score. -
Fix
transform_quantile_model_out(),transform_point_model_out(), andtransform_sample_model_out()to handle oracle outputs that carry anoutput_type_idcolumn without anoutput_typecolumn. Previously, this combination causedas_forecast_*()to error on a strayoutput_type_id(#73).