rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of afcharts and mpactr — release velocity, themes, recent moves, and the top alternatives to consider.
UK government chart styling in ggplot2, chasing ggplot2 v4 and stretching its palette to five.
afcharts supplies the UK Analysis Function's chart styling for ggplot2, as a theme, colour and fill scales, and a use_afcharts() call that applies the styling globally. Version 0.5.1 extends the sequential palette to five shades so it can carry quintile data such as deprivation bands, renames the na_colour argument to na.value, and adds a reset argument to switch the styling back off. The package began as a first release derived from sgplot and has had three releases in roughly two years.
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.
afcharts supplies the UK Analysis Function's chart styling for ggplot2, as a theme, colour and fill scales, and a use_afcharts() call that applies the styling globally. Version 0.5.1 extends the sequential palette to five shades so it can carry quintile data such as deprivation bands, renames the na_colour argument to na.value, and adds a reset argument to switch the styling back off. The package began as a first release derived from sgplot and has had three releases in roughly two years.
The work splits between palette design and keeping the styling composable. On the design side the sequential palette growing to five shades is driven by a specific reporting need rather than aesthetics, since quintiles are a standard unit in UK official statistics. On the mechanical side, the na.value rename was forced by ggplot2 v4.0.1, theme_af() now respects options set by an earlier use_afcharts() call, and a reset argument acknowledges that global styling needs an off switch. These are the problems a styling package hits once people use it inside larger documents.
Expect continued adjustment to ggplot2 v4, since the na.value rename is unlikely to be the only argument affected, and further palette work driven by the reporting formats government analysts actually publish. As a sibling to aftables in the same Analysis Function family, it is likely to keep tracking that guidance rather than setting its own direction.
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 afcharts 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 afcharts alternatives → · See all mpactr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. afcharts 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. afcharts 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 afcharts alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "afcharts alternatives" section above for the current picks, or visit /alternatives/afcharts 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.