← Back to home
Comparison · Analytics

rphylopic vs spEDM

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

Shared themes:r-package

rphylopic vs spEDM: at a glance

FeaturerphylopicspEDM
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesphylogenetics, data-visualization, r-package, ggplot2causal-inference, spatial-analysis, empirical-dynamic-modeling, r-package
Last editorial update2h ago40m ago
WebsiteVisit →Visit →

What is rphylopic?

The R package that puts organism silhouettes on plots keeps widening where they can be drawn.

rphylopic fetches PhyloPic silhouettes and places them into R graphics — base plots, ggplot2 layers, legends, and now phylogenetic trees and igraph networks. The 1.x line has been consistent about two things: adding a new plotting context per release, and steadily replacing its early sizing vocabulary with explicit width and height arguments. Attribution handling is unusually developed for a package this size, with permalinks and per-image credit built into the retrieval functions.

Read the full rphylopic trajectory →

What is spEDM?

Spatial causal discovery in R, one exposed method per release

spEDM brings empirical dynamic modeling to spatial data — cross mapping, convergent cross mapping and pattern causality over spatial vector and raster inputs, with the numerics in C++ behind S4 generics. The recent releases have exposed geographical pattern causality and spatially convergent partial cross mapping at the R level with vignettes, and 1.12 turns to consolidating the API. It is part of the stscl family alongside the temporal-domain tEDM, with which it shares both its C++ core and its maintainer.

Read the full spEDM trajectory →

rphylopic vs spEDM: editorial side-by-side

R
rphylopic
ANALYTICS
0.0

The R package that puts organism silhouettes on plots keeps widening where they can be drawn.

◆ Current state

rphylopic fetches PhyloPic silhouettes and places them into R graphics — base plots, ggplot2 layers, legends, and now phylogenetic trees and igraph networks. The 1.x line has been consistent about two things: adding a new plotting context per release, and steadily replacing its early sizing vocabulary with explicit width and height arguments. Attribution handling is unusually developed for a package this size, with permalinks and per-image credit built into the retrieval functions.

◆ Where it's heading

Development is expanding the set of places a silhouette can appear rather than changing what the package does. Base plots came first, then ggplot2 aesthetics and legend glyphs, then trees, then network vertices via an igraph shape registered automatically when both packages load. The other running thread is defensive maintenance against upstream churn: retries on failed API calls, fixes for ggplot2 4.0.0, and now an in-memory cache so repeated calls stop hammering the PhyloPic API. The ysize and size deprecation, opened in 1.5.0, is now complete and the arguments are scheduled for removal.

◆ Prediction

The deprecated ysize and size arguments look set to be removed in the next release, and on the pattern of the last four, another plotting context is a likelier addition than a change to the retrieval layer.

S
spEDM
ANALYTICS
0.0

Spatial causal discovery in R, one exposed method per release

◆ Current state

spEDM brings empirical dynamic modeling to spatial data — cross mapping, convergent cross mapping and pattern causality over spatial vector and raster inputs, with the numerics in C++ behind S4 generics. The recent releases have exposed geographical pattern causality and spatially convergent partial cross mapping at the R level with vignettes, and 1.12 turns to consolidating the API. It is part of the stscl family alongside the temporal-domain tEDM, with which it shares both its C++ core and its maintainer.

◆ Where it's heading

The cadence is steady and predictable: each release surfaces one more EDM method as an R-level API with a vignette, then spends the rest of its notes on parameter-handling consistency across the generics. Breaking changes are frequent and deliberate — argument renames, parameter reordering, NA-handling defaults — which reads as a package still settling its interface while the method surface expands. Shared changes appear in tEDM within days, so interface churn lands on both packages at once.

◆ Prediction

Expect the next release to expose another causality variant at the R level with an accompanying vignette, and to continue renaming or reordering parameters toward consistency across the spatial and temporal packages.

Alternatives to rphylopic and spEDM

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 rphylopic or spEDM.

See all rphylopic alternatives → · See all spEDM alternatives →

Recent activity from rphylopic and spEDM

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

  1. 1mo agorphylopicSilhouettes become igraph vertices; API responses cached
  2. 4mo agospEDMData slicing for large-scale pattern causality, plus API breaks
  3. 6mo agospEDMspEDM 1.11
  4. 6mo agospEDMSpatially convergent partial cross mapping reaches the R API
  5. 8mo agospEDMRaster cross mapping with anisotropic embedding
  6. 8mo agorphylopicBase R phylogenies gain silhouette annotation
  7. 11mo agospEDMConfigurable distance metrics and multithreaded distance computation
  8. 1y agospEDMSpatial logistic map exposed at the R level
  9. 1y agorphylopicExplicit width and height replace the old sizing arguments
  10. 2y agorphylopicSilhouette legends and attribution permalinks
  11. 2y agorphylopicSilhouette resolution helper and safer colour defaults
  12. 2y agorphylopicRendering dependencies bumped for grImport2 and rsvg

Frequently asked questions

What is the difference between rphylopic and spEDM?

Both compete on the same themes — r-package — within Analytics. rphylopic and spEDM 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 rphylopic better than spEDM?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rphylopic and spEDM 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 rphylopic?

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

What are the best alternatives to spEDM?

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