RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of camtrapdp and modeltime.ensemble — release velocity, themes, recent moves, and the top alternatives to consider.
camtrapdp has become a full read-edit-write toolkit for camera trap datasets, then went quiet
camtrapdp reads, filters and writes Camera Trap Data Packages in R, with export paths to Darwin Core and EML for GBIF publication. The round trip closed at 0.4.0, when write_camtrapdp() joined the existing reader; everything since has been standard-version upkeep and dependency alignment. The latest release does no user-facing work at all — it raises the R floor to 4.1.0, switches to base pipes, and pins {frictionless} >= 1.3.0.
modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.
modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.
camtrapdp reads, filters and writes Camera Trap Data Packages in R, with export paths to Darwin Core and EML for GBIF publication. The round trip closed at 0.4.0, when write_camtrapdp() joined the existing reader; everything since has been standard-version upkeep and dependency alignment. The latest release does no user-facing work at all — it raises the R floor to 4.1.0, switches to base pipes, and pins {frictionless} >= 1.3.0.
Development tracks two things it does not control: the Camtrap DP specification and the frictionless package underneath it. Each release so far has absorbed a spec bump (1.0.1, then 1.0.2) or an upstream API change, with the package's own surface largely settled since contributors(), individuals() and taxa() landed. The metadata-scope logic — filters rewriting spatial, temporal and taxonomic scope automatically — is the one genuinely opinionated piece and it has not been revisited.
The next release is most likely another spec-tracking one, upgrading datasets to whatever Camtrap DP version follows 1.0.2, since that has been the trigger for every release after the write path closed.
modeltime.ensemble builds average, weighted and stacked ensembles over modeltime forecast models. After a four-year gap it shipped twice in a fortnight during August and September 2025, both releases devoted to tracking breaking changes in tidymodels' tune package — new resampling column conventions, key uniqueness across resamples, recipe preparation. The tidyverse dependency was dropped in the same pass.
This is a package whose forecasting capability was settled by 2021 — recursive ensembles, per-series calibration — and whose recent life is dictated entirely by upstream tidymodels churn. New contributors did that compatibility work, including one from the tidymodels side. It now requires tune 2.0.0 and modeltime.resample 0.3.0, pinning it to the current tidymodels generation rather than straddling versions.
Expect the next release to follow the next tune or modeltime.resample breaking change rather than to introduce new ensembling methods.
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 camtrapdp or modeltime.ensemble.
RMVMR is being tidied in lockstep with MVMR, the package it wraps
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
See all camtrapdp alternatives → · See all modeltime.ensemble alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. camtrapdp 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. camtrapdp 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.
Top camtrapdp alternatives in Analytics are ranked by recent ship velocity. Browse the "camtrapdp alternatives" section above for the current picks, or visit /alternatives/camtrapdp for the full list with editorial commentary on each.
Top modeltime.ensemble alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime.ensemble alternatives" section above for the current picks, or visit /alternatives/modeltime-ensemble for the full list with editorial commentary on each.