mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of ipeaplot and rollupTree — 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.
The recursive-computation engine under massProps grows the accessors its consumer needed
rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.
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.
rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.
The package develops in response to its one visible consumer. The 0.4.0 accessors appeared in January 2026 and massProps switched to them thirteen days later; 0.4.1 then fixed missing column names in the setters, which is the kind of defect only real use surfaces. Before that, 0.3.0's default_validate_dag() extended validation past strict trees to directed acyclic graphs, widening what structures the engine will accept.
On the established pattern the next release will be whatever massProps needs next, discovered by using it. A DAG validator suggests non-tree structures are in scope, but nothing in these notes says that path is being pushed further.
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 rollupTree.
mice can finally predict, not just estimate, from multiply imputed data.
A market-microstructure toolkit that keeps adding estimators as the papers land.
A vowel-analysis package trimming dependencies after an email address got it archived.
The R half of the EMU speech database system, fixing what was quietly broken.
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all ipeaplot alternatives → · See all rollupTree alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ipeaplot and rollupTree 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 rollupTree 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 rollupTree alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rollupTree alternatives" section above for the current picks, or visit /alternatives/rolluptree for the full list with editorial commentary on each.