rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of climate and mpactr — release velocity, themes, recent moves, and the top alternatives to consider.
climate stops scraping and starts parsing: an in-house SYNOP engine replaces the HTML path.
climate pulls meteorological, hydrological and sounding data in R from public providers, chiefly the Polish IMGW-PIB repository, OGIMET and NOAA. Version 1.4.0 changes how it gets that data rather than what it offers: a new synop_parser() reads raw SYNOP messages directly, the OGIMET functions take a parser argument and default to SYNOP for hourly data with HTML kept for daily summaries, and the XML parsing engine has been replaced by in-house code to cut dependencies. The sounding functions also lost their server-side thermodynamic indices when the legacy Wyoming interface shut down.
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.
climate pulls meteorological, hydrological and sounding data in R from public providers, chiefly the Polish IMGW-PIB repository, OGIMET and NOAA. Version 1.4.0 changes how it gets that data rather than what it offers: a new synop_parser() reads raw SYNOP messages directly, the OGIMET functions take a parser argument and default to SYNOP for hourly data with HTML kept for daily summaries, and the XML parsing engine has been replaced by in-house code to cut dependencies. The sounding functions also lost their server-side thermodynamic indices when the legacy Wyoming interface shut down.
This package's history is largely a record of upstream providers changing underneath it, and 1.4.0 is the release where it stops absorbing those changes and reduces its exposure to them. The 1.2.9 notes described a 20-second pause between OGIMET requests as a temporary measure and named a SYNOP parsing engine as the intended fix; that engine is now here, and SYNOP messages can be retrieved in bulk rather than one scrape at a time. Owning the parser and dropping XML means the next provider-side HTML change is a smaller problem than the last one was.
Expect the SYNOP path to become the default for more of the OGIMET surface as it proves out, with the HTML parser retained only where the provider offers nothing else. Whether the thermodynamic indices return in some form, or stay permanently delegated to thundeR, is the open question these notes leave.
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 climate 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 climate 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. climate 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. climate 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 climate alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "climate alternatives" section above for the current picks, or visit /alternatives/climate 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.