v2.3.0
Highlights
- Redesigned thresholds analytics API: threshold strategies now take typed per-strategy parameters and return multi-line responses, making the API easier to validate and consume (#539).
- Metric direction metadata: evaluation metrics now expose whether a higher or lower score is better, so clients can rank and colour results correctly (#586).
Features
- feat(analytics): redesign thresholds API with typed per-strategy params and multi-line responses (#539)
- feat: expose whether a higher or lower metric score is better (CLIM-1088) (#586)
Bug Fixes
- fix(validate): reject non-numeric required covariates and non-finite values (#583)
- fix: remove demonstration metrics from evaluation results (CLIM-1086) (#584)
- fix: describe MAPE as a percentage error, not Mean Absolute Error (CLIM-1087) (#585)
- fix: keep the broker and database off the network model services share (CLIM-977) (#579)
- fix: update percentile label (#589)
Internal
- refactor: extract backtest evaluation details into a BacktestSpecification (#572)
Full changelog: v2.2.0...v2.3.0