← Back to home
Comparison · Analytics

aniprocess vs medrobust

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

Shared themes:r package

aniprocess vs medrobust: at a glance

Featureaniprocessmedrobust
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, signal processing, breaking changes, api designcausal mediation, partial identification, misclassification, sensitivity analysis
Last editorial update53m 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 medrobust?

medrobust made its partial-identification bounds usable by giving them confidence intervals.

medrobust computes partial-identification bounds for mediation effects when exposure or mediator is differentially misclassified, part of the Data-Wise mediationverse. Its 0.2.0 release corrected three estimator defects against population oracles and added Imbens-Manski confidence intervals for the bounds; the two releases since have paired each identification path with a real public-domain dataset and a worked vignette. CRAN is deferred, with distribution through GitHub and r-universe.

Read the full medrobust trajectory →

aniprocess vs medrobust: 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.

M
medrobust
ANALYTICS
0.0

medrobust made its partial-identification bounds usable by giving them confidence intervals.

◆ Current state

medrobust computes partial-identification bounds for mediation effects when exposure or mediator is differentially misclassified, part of the Data-Wise mediationverse. Its 0.2.0 release corrected three estimator defects against population oracles and added Imbens-Manski confidence intervals for the bounds; the two releases since have paired each identification path with a real public-domain dataset and a worked vignette. CRAN is deferred, with distribution through GitHub and r-universe.

◆ Where it's heading

The pattern is deliberate and symmetric: 0.3.0 shipped the mediator-side example on NCHS natality data, 0.4.0 its exposure-side mirror on NHANES, each demonstrating what the bounds do when reporting accuracy is allowed to depend on the outcome. Alongside that runs a consistent concern with failing usefully rather than loudly — bound_ne() returns NA bounds with a machine-readable reason and a typed condition instead of aborting, so a simulation replicate is recorded rather than lost, and non-finite endpoint standard errors produce a documented NA rather than a silent one. That is a package expecting to be run thousands of times inside someone else's loop.

◆ Prediction

Both identification paths now have a dataset, a vignette and interval coverage, so the next release is most likely the deferred CRAN submission rather than new methodology.

Alternatives to aniprocess and medrobust

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 medrobust.

See all aniprocess alternatives → · See all medrobust alternatives →

Recent activity from aniprocess and medrobust

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

  1. 2d agoaniprocessThree-tier filter API; filter_aniframe() removed
  2. 2mo agomedrobustNHANES exposure-side misclassification example dataset
  3. 2mo agomedrobustNatality example dataset; bounds degrade instead of aborting
  4. 2mo agomedrobustBounds corrected against oracles; Imbens-Manski intervals added
  5. 3mo agoaniprocessCCMA, excursion and Gaussian filters; FFT passband fix

Frequently asked questions

What is the difference between aniprocess and medrobust?

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 medrobust?

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 medrobust?

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