Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
Comparison · Analytics
mev vs tulpa
A side-by-side editorial comparison of mev and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
mev vs tulpa: at a glance
What is mev?
An extreme-value toolkit reorganised its whole API into prefixed families and tripled its estimator count.
mev provides likelihood-based inference for univariate and multivariate extreme value models — threshold selection, shape estimation, tail dependence and max-stable simulation. Version 2.0 was a deliberate reorganisation: every threshold-selection routine now carries a thselect. prefix, every stability plot a tstab. prefix, and every extremal-dependence measure an xdep. prefix, with the old names deprecated but mostly still working. The same release added a large batch of estimators — Stein-weighted GPD, roughly a dozen shape estimators, second-order regular variation, L-moment GPD and Weissman quantiles.
What is tulpa?
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
mev vs tulpa: editorial side-by-side
mev
0.0ANALYTICS
An extreme-value toolkit reorganised its whole API into prefixed families and tripled its estimator count.
◆ Current state
mev provides likelihood-based inference for univariate and multivariate extreme value models — threshold selection, shape estimation, tail dependence and max-stable simulation. Version 2.0 was a deliberate reorganisation: every threshold-selection routine now carries a thselect. prefix, every stability plot a tstab. prefix, and every extremal-dependence measure an xdep. prefix, with the old names deprecated but mostly still working. The same release added a large batch of estimators — Stein-weighted GPD, roughly a dozen shape estimators, second-order regular variation, L-moment GPD and Weissman quantiles.
◆ Where it's heading
The package is consolidating into a reference implementation of the extreme-value literature rather than a collection of one-off routines. Sixteen threshold-selection methods now share standardised arguments and their own plot and print methods with automatic selection, which is the tell: the goal is comparability across methods, not just availability. Dependency reduction runs alongside, with distribution functions written in-package to drop evd and Rsolnp replacing nloptr in earlier releases.
◆ Prediction
Version 2.1 continued adding threshold-selection routines within the new naming scheme, so the next release most likely follows the same pattern — more estimators fitted to the established prefixes, plus fixes to the 2.0 renaming. The entries give no sign of a further structural change.
tulpa
7.5ANALYTICS
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
◆ Current state
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
◆ Where it's heading
Two moves in nine days point at the same destination: the generics conversion made tulpa extensible by downstream packages, and CRAN admission makes it installable by them. The current cadence — several tags a week, some existing only to record a measurement that produced no code change — does not survive CRAN's submission overhead, so the release rhythm has to slow whether or not the project intends it. The correctness work still clusters on the joint nested-Laplace driver, and 0.1.0 extends the same diagnostics habit with .NL_AXIS_SD_REASONS, a closed vocabulary for an outer axis whose grid does not contain its own posterior mode.
◆ Prediction
Expect tulpaObs to follow tulpa onto CRAN, since it is the consumer whose registrations the engine has spent this window unblocking, and expect the version line to move in larger, less frequent steps now that each one carries a submission.
Alternatives to mev and tulpa
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 mev or tulpa.
RStudio
RStudio ships through release branches, and the notes are commit messages
dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
Recent activity from mev and tulpa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21h agotulpaFirst CRAN release: engine surface unchanged from 0.0.198 ⚡
- 4d agotulpatulpa_re_aghq() exposes the mode/theta cross-Hessian
- 8d agotulpaDense batched joint path could silently drop a grid cell
- 8d agotulpaCalibration and goodness-of-fit entry points become S3 generics ⚡
- 9d agotulpaCUDA backend had two definitions; link order decided if it ran
- 9d agotulpaHyperparameter bounds now flag when they leave the node range
- 9mo agomevTwo more threshold-selection routines slot into the new scheme
- 10mo agomevThreshold, stability and dependence functions regrouped under prefixes ⚡
- 2y agomevBoundary-case likelihood fixes, bundled with the prior release's notes
- 3y agomevGEV and GP distribution functions brought in-house to drop evd
- 4y agomevFour max-stable families, fixed parameters and threshold diagnostics
Frequently asked questions
What is the difference between mev and tulpa?
They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 mev better than tulpa?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 mev?
Top mev alternatives in Analytics are ranked by recent ship velocity. Browse the "mev alternatives" section above for the current picks, or visit /alternatives/mev for the full list with editorial commentary on each.
What are the best alternatives to tulpa?
Top tulpa alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpa alternatives" section above for the current picks, or visit /alternatives/tulpa for the full list with editorial commentary on each.