compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of kwb.geosalz and procs — release velocity, themes, recent moves, and the top alternatives to consider.
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.
An R package rebuilding SAS procedures one PROC at a time, now filling in their options.
procs reimplements SAS statistical procedures — FREQ, MEANS, TTEST, REG, SORT, TRANSPOSE — as R functions returning both datasets and report-ready output, as part of the r-sassy suite. The catalogue of procedures is largely assembled; recent releases concentrate on the parameters each one accepts rather than on adding new procedures. Validation documentation is maintained alongside the code, consistent with the regulated environments the suite targets.
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.
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.
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.
procs reimplements SAS statistical procedures — FREQ, MEANS, TTEST, REG, SORT, TRANSPOSE — as R functions returning both datasets and report-ready output, as part of the r-sassy suite. The catalogue of procedures is largely assembled; recent releases concentrate on the parameters each one accepts rather than on adding new procedures. Validation documentation is maintained alongside the code, consistent with the regulated environments the suite targets.
The work has shifted from breadth to fidelity: where earlier releases introduced whole procedures, recent ones add the options a SAS user expects to find on them, most visibly the where parameter spread across five functions at once and plotting support across three. Statistical output is being widened too, with AIC and adjusted Chi-Square appearing. The remaining gap is per-procedure option coverage rather than missing procedures.
Expect continued option-level parity work on the existing procedures, with new statistics added to their output tables, rather than a new proc_* function.
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 kwb.geosalz or procs.
An MLE package rebuilt around composable solvers, then renamed to match.
nabla dropped its C++ engine to chase exact derivatives at any order.
Eight months from first release to keyring caching and workload identity.
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
A package retired in 2017 just got rewritten against R's public C API.
See all kwb.geosalz alternatives → · See all procs alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. kwb.geosalz and procs 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. kwb.geosalz and procs 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.
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.
Top procs alternatives in Analytics are ranked by recent ship velocity. Browse the "procs alternatives" section above for the current picks, or visit /alternatives/procs for the full list with editorial commentary on each.