hubEvals 0.3.1
-
score_model_out()now handles disaggregated relative-skill scoring where some comparison groups (thebycolumns other thanmodel_id) cannot be compared, instead of aborting the whole call with a crypticscoringutilserror (“Baseline comparator … missing”). A group containing only one model is treated like the global single-model case, with relative skill filled as1(a model has skill1relative to itself). A group from which a requestedbaselineis absent has its relative and scaled relative skill reported asNA, with a warning naming the affected groups; the absolute scores for those groups are still returned unchanged. Abaselinethat is absent from the data entirely remains an error (#135).
hubEvals 0.3.0
CRAN release: 2026-06-29
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).
hubEvals 0.2.0
Add support for scoring sample output types via
transform_sample_model_out()and the"sample"case inscore_model_out(). Marginal scoring produces metrics such as CRPS, bias, and DSS; compound scoring (via the newcompound_taskid_setargument) produces multivariate scores such as energy score and variogram score for joint forecasts (#94).score_model_out()now errors with a clear message when a scale transformation produces non-finite values (NaN or Inf), instead of silently returning invalid scores (#99).
hubEvals 0.1.0
- Add
transform,transform_append, andtransform_labelarguments toscore_model_out()for computing scores on transformed scales (e.g., log, sqrt). Supported for quantile, mean, and median output types (#48, #91).
hubEvals 0.0.1
- Export functions
transform_pmf_model_out(),transform_point_model_out(), andtransform_quantile_model_out()used to transform hubverse model outputs into ascoringutilsforecast object - Update package dependencies to use CRAN releases when available
- Update README to include simple examples of package functions
hubEvals 0.0.0.9001
- Add
score_model_out()function for evaluating model outputs - Add tests to package
- Update organisation name to hubverse-org
