compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
Comparison · Analytics
hubEvals vs querychat
A side-by-side editorial comparison of hubEvals and querychat — release velocity, themes, recent moves, and the top alternatives to consider.
hubEvals vs querychat: at a glance
What is hubEvals?
Forecast-hub scoring that learned to handle joint, sample-based predictions.
hubEvals scores model output from collaborative forecasting hubs, wrapping scoringutils and translating hubverse formats into forecast objects it can evaluate. The package has moved quickly from a thin translation layer to something that handles every output type the hubverse defines — quantile, mean, median, nominal and ordinal pmf, and samples. The most recent releases are almost entirely about the failure modes of relative skill scoring rather than about new metrics.
What is querychat?
Natural-language data querying that outgrew both single tables and Shiny.
querychat puts a natural-language chat interface over a data source, translating questions into SQL and filtering a dashboard from the result. It ships as parallel Python and R packages from one repository, with the Python side consistently ahead and the R side receiving ported features in batches — so the feed interleaves two version series that should not be read as one. Recent releases have expanded both what it can be embedded in and what it can be asked.
hubEvals vs querychat: editorial side-by-side
hubEvals
2.5ANALYTICS
Forecast-hub scoring that learned to handle joint, sample-based predictions.
◆ Current state
hubEvals scores model output from collaborative forecasting hubs, wrapping scoringutils and translating hubverse formats into forecast objects it can evaluate. The package has moved quickly from a thin translation layer to something that handles every output type the hubverse defines — quantile, mean, median, nominal and ordinal pmf, and samples. The most recent releases are almost entirely about the failure modes of relative skill scoring rather than about new metrics.
◆ Where it's heading
Two threads dominate. The first is coverage of output types, which reached its widest point with sample-based and compound scoring. The second, and the one occupying every recent release, is making relative skill degrade gracefully: single-model input, comparison groups with one model, and groups missing the requested baseline have each been converted from a cryptic upstream abort into a defined result. That pattern — inherited scoringutils errors being caught and given hub-specific meaning — is the clearest signal of where this package adds value.
◆ Prediction
Expect continued work smoothing scoringutils error surfaces into hub-aware behaviour, and performance attention on relative skill, which was explicitly optimised in the latest release.
querychat
0.0ANALYTICS
Natural-language data querying that outgrew both single tables and Shiny.
◆ Current state
querychat puts a natural-language chat interface over a data source, translating questions into SQL and filtering a dashboard from the result. It ships as parallel Python and R packages from one repository, with the Python side consistently ahead and the R side receiving ported features in batches — so the feed interleaves two version series that should not be read as one. Recent releases have expanded both what it can be embedded in and what it can be asked.
◆ Where it's heading
Two expansions define this window. The package broke out of Shiny to support Gradio, Dash and Streamlit, and broke out of the single-table model to reason across related tables with joins and cross-table aggregation. Alongside those, the answer format widened from tables to inline charts through ggsql. The remaining work visible here is polish on the chat experience itself — cancellation, suggestion cards, deferred initialisation for per-user credentials — which suggests production deployment rather than demo use is now driving the roadmap.
◆ Prediction
Expect the R package to continue absorbing Python-side features on a lag, with multi-table support the most likely next port given it is the largest capability the two now differ on.
Alternatives to hubEvals and querychat
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either hubEvals or querychat.
nabla
nabla dropped its C++ engine to chase exact derivatives at any order.
snowflakeauth
Eight months from first release to keyring caching and workload identity.
kwb.geosalz
A research-project workflow package where the interesting work is in the plumbing.
cyclocomp
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
revdbayes
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
See all hubEvals alternatives → · See all querychat alternatives →
Recent activity from hubEvals and querychat
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 24d agohubEvalsScored-forecast counts and faster relative skill
- 1mo agohubEvalsDisaggregated relative skill no longer aborts the whole call
- 1mo agoquerychatquerychat reasons across multiple related tables ⚡
- 1mo agohubEvalsSingle-model scoring returns relative skill of 1 instead of erroring
- 2mo agoquerychatStream cancellation and a clearer name for the filtering tool
- 2mo agoquerychatggsql visualization tool and deferred chat client initialization
- 2mo agoquerychatR package gains inline charts and stream cancellation
- 5mo agohubEvalsSample output types and multivariate compound scoring ⚡
- 6mo agohubEvalsScoring on transformed scales via transform arguments
- 6mo agoquerychatDeferred data source initialization for per-user connections
- 7mo agoquerychatGradio, Dash and Streamlit join Shiny as supported frameworks ⚡
- 11mo agohubEvalsFirst release: score_model_out() and the scoringutils bridge
Frequently asked questions
What is the difference between hubEvals and querychat?
They serve adjacent needs but don't currently overlap on shipped themes. hubEvals is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is hubEvals better than querychat?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. hubEvals is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to hubEvals?
Top hubEvals alternatives in Analytics are ranked by recent ship velocity. Browse the "hubEvals alternatives" section above for the current picks, or visit /alternatives/hubevals for the full list with editorial commentary on each.
What are the best alternatives to querychat?
Top querychat alternatives in Analytics are ranked by recent ship velocity. Browse the "querychat alternatives" section above for the current picks, or visit /alternatives/querychat for the full list with editorial commentary on each.