compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
Comparison · Analytics
kwb.geosalz vs TrialEmulation
A side-by-side editorial comparison of kwb.geosalz and TrialEmulation — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
kwb.geosalz vs TrialEmulation: at a glance
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.
What is TrialEmulation?
Target trial emulation held steady by dependency maintenance, not new methods.
TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.
kwb.geosalz vs TrialEmulation: editorial side-by-side
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.
TrialEmulation
0.0ANALYTICS
Target trial emulation held steady by dependency maintenance, not new methods.
◆ Current state
TrialEmulation implements target trial emulation from observational data, using duckdb to handle the expanded per-period datasets that approach generates. Every release in the visible window is upkeep: two consecutive releases removing the archived parglm dependency, two fixing tests against testthat updates, and two tracking duckdb sampling changes. No methodological work appears in the feed since before February 2025.
◆ Where it's heading
The package is being kept installable rather than extended. Its dependency surface, duckdb for storage, parglm for fitting, testthat for checks, generates most of the release traffic, and CRAN archiving parglm forced two separate releases three months apart to fully excise it. The version numbering, still in the 0.0.4.x range after years, suggests the maintainers do not consider the API settled enough to promote.
◆ Prediction
Further releases will most likely be triggered by upstream dependency changes; the entries give no signal on when methodological work resumes.
Alternatives to kwb.geosalz and TrialEmulation
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 TrialEmulation.
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 kwb.geosalz alternatives → · See all TrialEmulation alternatives →
Recent activity from kwb.geosalz and TrialEmulation
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agoTrialEmulationDocumentation references to the archived parglm removed
- 5mo agokwb.geosalzSFTP transfers moved to curl, file listing 50-100x faster
- 7mo agoTrialEmulationparglm dependency dropped after CRAN archiving
- 9mo agoTrialEmulationTest fixes for updated testthat, plus link updates
- 9mo agoTrialEmulationCompatibility fixes ahead of testthat 3.3.0
- 1y agoTrialEmulationTests updated for duckdb 1.3.0 sampling; R 4.1 now required
- 1y agokwb.geosalzConductivity outliers filtered from measurement chain plots
- 1y agoTrialEmulationTests updated for duckdb 1.2.0 sampling changes
- 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 kwb.geosalz and TrialEmulation?
Both compete on the same themes — r-package — within Analytics. kwb.geosalz and TrialEmulation 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 kwb.geosalz better than TrialEmulation?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. kwb.geosalz and TrialEmulation 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 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.
What are the best alternatives to TrialEmulation?
Top TrialEmulation alternatives in Analytics are ranked by recent ship velocity. Browse the "TrialEmulation alternatives" section above for the current picks, or visit /alternatives/trialemulation for the full list with editorial commentary on each.