← Back to home
Comparison · Analytics

aniprocess vs probmed

A side-by-side editorial comparison of aniprocess and probmed — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r package

aniprocess vs probmed: at a glance

Featureaniprocessprobmed
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, signal processing, breaking changes, api designcausal mediation, effect size, semiparametric inference, cross-fitting
Last editorial update54m ago47m ago
WebsiteVisit →Visit →

What is aniprocess?

aniprocess rebuilt its filter API into three tiers and removed the old one outright.

aniprocess is the signal-processing half of the animovement ecosystem for animal movement data — smoothing, outlier flagging and gap handling for tracking coordinates. Version 0.3.0 restructured the entire public interface into three tiers: bare functions over a vector or a frame of coordinate columns, *_with() to select a method by name, and *_across() to apply one to a whole aniframe. Two functions were removed rather than deprecated, and argument names were normalized across the package.

Read the full aniprocess trajectory →

What is probmed?

probmed went from one probabilistic effect size to a family of them in sixteen days.

probmed computes P_med, a scale-free probabilistic effect size for causal mediation, as part of the Data-Wise mediationverse alongside medfit, medsim and RMediation. Three releases in three weeks took it from a single estimator to four additional families built on a shared cross-fitted corner-EIF core, covering gauge-calibrated, incremental-elasticity and Sobol variance-share versions of the proportion mediated. Distribution is GitHub and r-universe rather than CRAN, with a load-bearing Remotes pin on medfit.

Read the full probmed trajectory →

aniprocess vs probmed: editorial side-by-side

A
aniprocess
ANALYTICS
3.8

aniprocess rebuilt its filter API into three tiers and removed the old one outright.

◆ Current state

aniprocess is the signal-processing half of the animovement ecosystem for animal movement data — smoothing, outlier flagging and gap handling for tracking coordinates. Version 0.3.0 restructured the entire public interface into three tiers: bare functions over a vector or a frame of coordinate columns, *_with() to select a method by name, and *_across() to apply one to a whole aniframe. Two functions were removed rather than deprecated, and argument names were normalized across the package.

◆ Where it's heading

The redesign pushes aniframe metadata into the processing layer — *_across() reads sampling rate and the time column off the object instead of asking the caller, which is the division of labour aniframe's own class work assumes. Defaults are shifting toward not destroying information: filters preserve gaps unless inferring across them is the point, and a missing confidence score now warns rather than being read as a poor one. The bug fixes tell a consistent per-group story, with speed computed within each track so a step never forms across a track boundary.

◆ Prediction

With the across-style API landed and issue #29 (filter_by_pose) still open, the next release most likely extends the same three-tier pattern to pose data rather than adding more filters.

P
probmed
ANALYTICS
0.0

probmed went from one probabilistic effect size to a family of them in sixteen days.

◆ Current state

probmed computes P_med, a scale-free probabilistic effect size for causal mediation, as part of the Data-Wise mediationverse alongside medfit, medsim and RMediation. Three releases in three weeks took it from a single estimator to four additional families built on a shared cross-fitted corner-EIF core, covering gauge-calibrated, incremental-elasticity and Sobol variance-share versions of the proportion mediated. Distribution is GitHub and r-universe rather than CRAN, with a load-bearing Remotes pin on medfit.

◆ Where it's heading

The pace is manuscript-driven — estimators arrive with their citations attached and vignettes alongside, and the 0.1.0 notes correct the estimand itself against a manuscript definition rather than fixing a bug in code. Each release adds inference machinery as well as point estimates: percentile-bootstrap intervals and Fieller sets in 0.3.0, a deterministic MBCO interval in 0.2.0 that avoids resampling entirely. The gauge residual and the pmed_sensitivity() helper suggest a growing concern with when the estimand does not decompose at all.

◆ Prediction

0.3.0 shipped a sensitivity helper for shared mediator-outcome confounding and a diagnostic that flags non-decomposability, so the next release most likely extends that diagnostic side rather than adding a fifth estimator family.

Alternatives to aniprocess and probmed

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 aniprocess or probmed.

See all aniprocess alternatives → · See all probmed alternatives →

Recent activity from aniprocess and probmed

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoaniprocessThree-tier filter API; filter_aniframe() removed
  2. 1mo agoprobmedFour estimator families on a cross-fitted corner-EIF core
  3. 2mo agoprobmedParallel mediators and a resampling-free MBCO interval
  4. 2mo agoprobmedFirst release: pmed() with the estimand corrected
  5. 3mo agoaniprocessCCMA, excursion and Gaussian filters; FFT passband fix

Frequently asked questions

What is the difference between aniprocess and probmed?

Both compete on the same themes — r package — within Analytics. aniprocess is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 aniprocess better than probmed?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aniprocess is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 aniprocess?

Top aniprocess alternatives in Analytics are ranked by recent ship velocity. Browse the "aniprocess alternatives" section above for the current picks, or visit /alternatives/aniprocess for the full list with editorial commentary on each.

What are the best alternatives to probmed?

Top probmed alternatives in Analytics are ranked by recent ship velocity. Browse the "probmed alternatives" section above for the current picks, or visit /alternatives/probmed for the full list with editorial commentary on each.