metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of logrx and sivirep — release velocity, themes, recent moves, and the top alternatives to consider.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
logrx produces execution logs for R scripts in regulated clinical work, recording what ran, what it returned, and which unapproved packages or functions were used. Its release notes are raw merged-PR lists rather than written changelogs, which makes the substance hard to read from the feed. The most recent release, 0.2.2 in June 2023, exists to track tidyselect and dplyr changes.
sivirep turned Colombia's SIVIGILA surveillance data into a one-call reporting package.
The 1.0.0 release of December 2024 is the substance of this feed: incidence calculation and plotting for the country, departments and municipalities, ethnicity and case-classification breakdowns, multi-year retrospectives, and a Reporte Evento template that assembles them. It was shaped by usability testing and expert review with Colombia's National Institute of Health. The two patches since are fixes, warnings and documentation.
logrx produces execution logs for R scripts in regulated clinical work, recording what ran, what it returned, and which unapproved packages or functions were used. Its release notes are raw merged-PR lists rather than written changelogs, which makes the substance hard to read from the feed. The most recent release, 0.2.2 in June 2023, exists to track tidyselect and dplyr changes.
Feature work concentrated in the 0.1 line — return codes, a results writer, a to_report parameter, and logging of unapproved package and function use — and the 0.2 releases have been compatibility maintenance and hotfixes. Three years of silence in a pharmaverse that has otherwise kept shipping suggests the package reached the shape its users needed rather than that it was abandoned mid-design.
Nothing in these entries points to planned work; the likeliest trigger for a release is a breaking change in tidyverse dependencies, which is what produced the last one.
The 1.0.0 release of December 2024 is the substance of this feed: incidence calculation and plotting for the country, departments and municipalities, ethnicity and case-classification breakdowns, multi-year retrospectives, and a Reporte Evento template that assembles them. It was shaped by usability testing and expert review with Colombia's National Institute of Health. The two patches since are fixes, warnings and documentation.
Work after 1.0.0 has gone into making the report template survive bad input rather than adding analyses — warnings when a municipality or department has no data, handlers that surface import and geo-filter errors during rendering, and an explicit note that first use of any import function needs an internet connection. English-language articles were added alongside the Spanish function interface.
Spanish-named functions paired with new English articles point at a widening audience; more translation of the guides looks likelier than new epidemiological methods.
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 logrx or sivirep.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
See all logrx alternatives → · See all sivirep alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. logrx and sivirep 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. logrx and sivirep 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.
Top logrx alternatives in Analytics are ranked by recent ship velocity. Browse the "logrx alternatives" section above for the current picks, or visit /alternatives/logrx for the full list with editorial commentary on each.
Top sivirep alternatives in Analytics are ranked by recent ship velocity. Browse the "sivirep alternatives" section above for the current picks, or visit /alternatives/sivirep for the full list with editorial commentary on each.