compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
Comparison · Analytics
hubPredEvalsData vs kwb.geosalz
A side-by-side editorial comparison of hubPredEvalsData and kwb.geosalz — release velocity, themes, recent moves, and the top alternatives to consider.
hubPredEvalsData vs kwb.geosalz: at a glance
What is hubPredEvalsData?
The pipeline turning hub forecasts into dashboard-ready evaluation data.
hubPredEvalsData generates the scored evaluation data that hubverse prediction dashboards read, driven by a predevals-config.yml and scoring through hubEvals underneath. It is the youngest package in this part of the stack and the fastest-moving in configuration terms, having already passed a breaking 1.0.0 and a schema-versioned feature addition. Its output contract is a scores.csv file consumed downstream, which shapes what its releases care about.
What is kwb.geosalz?
A research-project workflow package where the interesting work is in the plumbing.
kwb.geosalz documents the data workflows for GeoSalz, a groundwater salinisation project run by Kompetenzzentrum Wasser Berlin, packaging retrieval, checking and plotting steps as reproducible R code. The current release replaces an SFTP dependency with curl and reports listing files on the SFTP server running 50 to 100 times faster. Earlier releases added data-availability workflows against Berlin's open water portal and functions for well-field abstraction figures.
hubPredEvalsData vs kwb.geosalz: editorial side-by-side
hubPredEvalsData
0.0ANALYTICS
The pipeline turning hub forecasts into dashboard-ready evaluation data.
◆ Current state
hubPredEvalsData generates the scored evaluation data that hubverse prediction dashboards read, driven by a predevals-config.yml and scoring through hubEvals underneath. It is the youngest package in this part of the stack and the fastest-moving in configuration terms, having already passed a breaking 1.0.0 and a schema-versioned feature addition. Its output contract is a scores.csv file consumed downstream, which shapes what its releases care about.
◆ Where it's heading
Each release widens what the config file can express — round selection, then scale transformations with per-target overrides, then target labelling pulled from the hub's own task metadata. The pattern is consistent: capability that already exists in hubEvals gets a declarative surface here so hub maintainers configure it rather than write code. Recent attention to byte-stable output ordering shows the file is being treated as a reproducible artifact, not just a report.
◆ Prediction
Expect the config schema to keep absorbing hubEvals capabilities as declarative options, with continued attention to making scores.csv reproducible and diffable between runs.
kwb.geosalz
0.0ANALYTICS
A research-project workflow package where the interesting work is in the plumbing.
◆ Current state
kwb.geosalz documents the data workflows for GeoSalz, a groundwater salinisation project run by Kompetenzzentrum Wasser Berlin, packaging retrieval, checking and plotting steps as reproducible R code. The current release replaces an SFTP dependency with curl and reports listing files on the SFTP server running 50 to 100 times faster. Earlier releases added data-availability workflows against Berlin's open water portal and functions for well-field abstraction figures.
◆ Where it's heading
Releases track the project's own data-collection reality rather than a software roadmap: new data source appears, a workflow is added; a transfer library becomes a liability, it is swapped out. The measurement-chain pipeline is the recurring subject, appearing in plotting fixes at 0.7.1 and the transport rewrite at 0.7.2. Cadence is roughly annual and the changelog is written for project members, which makes external readability secondary by design.
◆ Prediction
Expect the next release to follow the measurement-chain data as it accumulates, most likely more plotting or availability-checking work rather than new infrastructure.
Alternatives to hubPredEvalsData and kwb.geosalz
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 hubPredEvalsData or kwb.geosalz.
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.
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.
lazyeval
A package retired in 2017 just got rewritten against R's public C API.
See all hubPredEvalsData alternatives → · See all kwb.geosalz alternatives →
Recent activity from hubPredEvalsData and kwb.geosalz
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agohubPredEvalsDataTarget names pulled from hub metadata; scores.csv made byte-stable
- 2mo agohubPredEvalsDataVersioned target data with an as_of column no longer fails scoring
- 2mo agohubPredEvalsDataScale transformations become configurable per target
- 4mo agohubPredEvalsDataMulti-round hub support via a required rounds_idx property (breaking)
- 5mo agokwb.geosalzSFTP transfers moved to curl, file listing 50-100x faster
- 1y agokwb.geosalzConductivity outliers filtered from measurement chain plots
- 2y agokwb.geosalzRelease rolling up vignette cleanup and well operation work
- 4y agokwb.geosalzWasserportal Berlin workflow and CRS conversion added
- 4y agokwb.geosalzAnnual well-field abstraction figures retrievable
- 7y agokwb.geosalzInitial release scaffolded from the in-house package template
Frequently asked questions
What is the difference between hubPredEvalsData and kwb.geosalz?
They serve adjacent needs but don't currently overlap on shipped themes. hubPredEvalsData and kwb.geosalz are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is hubPredEvalsData better than kwb.geosalz?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. hubPredEvalsData and kwb.geosalz are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to hubPredEvalsData?
Top hubPredEvalsData alternatives in Analytics are ranked by recent ship velocity. Browse the "hubPredEvalsData alternatives" section above for the current picks, or visit /alternatives/hubpredevalsdata for the full list with editorial commentary on each.
What are the best alternatives to kwb.geosalz?
Top kwb.geosalz alternatives in Analytics are ranked by recent ship velocity. Browse the "kwb.geosalz alternatives" section above for the current picks, or visit /alternatives/kwb-geosalz for the full list with editorial commentary on each.