rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of ipeaplot and mpactr — release velocity, themes, recent moves, and the top alternatives to consider.
An institutional chart theme whose recent releases are all vignette repair.
ipeaplot supplies Ipea's house style to ggplot2 — theme_ipea(), matching colour and fill scales, and export helpers that write the formats the institute's publications need. The feature line has been quiet since October, when save_ipeaplot() consolidated the format-specific savers. Both July releases exist to get the package building again, not to change it.
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
mpactr filters mass-spectrometry peak tables — removing contaminants, ion duplicates and low-reproducibility features before downstream metabolomics analysis — with a data.table and Rcpp core. Development is slow and the recent releases are small. The May pair both address the same friction: column names and imported table names arriving in inconsistent case and failing to match.
ipeaplot supplies Ipea's house style to ggplot2 — theme_ipea(), matching colour and fill scales, and export helpers that write the formats the institute's publications need. The feature line has been quiet since October, when save_ipeaplot() consolidated the format-specific savers. Both July releases exist to get the package building again, not to change it.
The package has been converging on a smaller, more uniform surface: separate save_eps() and save_pdf() helpers gave way to one save_ipeaplot() covering vector and raster formats with sensible defaults, and the Frutiger font dependency was dropped for a default sans-serif. What consumes releases now is downstream breakage — two consecutive patches in ten days, the second traced to geobr, both in vignettes rather than package code.
The palette line has grown one colour set at a time and is the most likely place for the next addition, but nothing in these entries commits to it. On current evidence the near term is more compatibility patching against the geobr and ggplot2 packages the vignettes depend on.
mpactr filters mass-spectrometry peak tables — removing contaminants, ion duplicates and low-reproducibility features before downstream metabolomics analysis — with a data.table and Rcpp core. Development is slow and the recent releases are small. The May pair both address the same friction: column names and imported table names arriving in inconsistent case and failing to match.
The package is stabilizing its input contract rather than growing its filtering methods. Metadata column names are now forced lowercase inside import_data() regardless of how the file was written, imported peak_tables names not present in the injection column are lowercased too, and get_meta_data() was renamed to get_metadata() in the same pass. Before that the work was infrastructural — Rcpp introduced to speed up filtering, data.table moved from Depends to Imports, and memory errors cleared so the package passes Valgrind and both sanitizers. Note the earliest entry compares against a v1.0.0 tag that precedes 0.1.0 in the repository, so version ordering in this feed is not reliable.
The case-normalization work has now touched both metadata columns and peak table names across two consecutive releases, which suggests the input-matching problem is not fully closed and a third pass is plausible. Nothing in these entries points to new filtering methods.
Other Infra & APIs 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 ipeaplot or mpactr.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all ipeaplot alternatives → · See all mpactr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-packages — within Infra & APIs. ipeaplot and mpactr 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ipeaplot and mpactr 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 Infra & APIs products to evaluate alongside.
Top ipeaplot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ipeaplot alternatives" section above for the current picks, or visit /alternatives/ipeaplot for the full list with editorial commentary on each.
Top mpactr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "mpactr alternatives" section above for the current picks, or visit /alternatives/mpactr for the full list with editorial commentary on each.