osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
A side-by-side editorial comparison of fellingdater and graphicalMCP — release velocity, themes, recent moves, and the top alternatives to consider.
Went from estimating felling dates to doing the crossdating that produces them.
fellingdater estimates when a tree was felled from sapwood measurements, the core inference in dendrochronological dating of timber. Version 1.0.0 passed rOpenSci review with that scope, and the 2024 releases were mostly about the accompanying JOSS paper and user-supplied sapwood datasets. Version 1.2.0 changed the package's remit substantially, adding an entire trs_* family for tree-ring series handling: crossdating with multiple statistical measures, the Hollstein and Baillie-Pilcher t-value transformations, parallel variation percentages, synthetic series generation, and dated-series plotting.
graphicalMCP is a narrow statistical tool being hardened rather than grown.
graphicalMCP implements graphical multiple comparison procedures — the method used to control family-wise error across several endpoints in a clinical trial. The package moved under the openpharma organisation in 0.2.6, picked up Hochberg tests and internal validation in 0.2.8, and its most recent release fixes a case where graph testing by closure disagreed with the rejection-based path. Releases are roughly annual and short.
fellingdater estimates when a tree was felled from sapwood measurements, the core inference in dendrochronological dating of timber. Version 1.0.0 passed rOpenSci review with that scope, and the 2024 releases were mostly about the accompanying JOSS paper and user-supplied sapwood datasets. Version 1.2.0 changed the package's remit substantially, adding an entire trs_* family for tree-ring series handling: crossdating with multiple statistical measures, the Hollstein and Baillie-Pilcher t-value transformations, parallel variation percentages, synthetic series generation, and dated-series plotting.
The package has expanded backwards along the workflow. It began at the last step — given dated series, estimate the felling date — and 1.2.0 added the step before it, establishing those dates by crossdating in the first place. Version 1.2.1 is early polish on that new surface: axis control, non-syntactic column names, encoding safety in read_fh(). The direction is a single package covering the chain from raw ring widths to a felling-date estimate.
Expect the trs_* family to keep accumulating polish and additional crossdating statistics, since it is barely a year old and 1.2.1 was already fixing its plotting and top_n behaviour. Whether the two halves of the package get unified into one workflow interface is the open question the entries do not answer.
graphicalMCP implements graphical multiple comparison procedures — the method used to control family-wise error across several endpoints in a clinical trial. The package moved under the openpharma organisation in 0.2.6, picked up Hochberg tests and internal validation in 0.2.8, and its most recent release fixes a case where graph testing by closure disagreed with the rejection-based path. Releases are roughly annual and short.
The changelog reads as a package settling into reference-implementation status: procedure coverage widened once, then the work turned to proving the two computational routes through the same graph agree with each other. That agreement is the whole promise of this kind of tool, since the closure-based calculation is the definition and the rejection-based one is the fast path everyone actually runs. The openpharma move points the same direction — shared maintenance rather than a single author's project.
The entries show no feature roadmap, only correctness and validation work, so the next release is most likely another consistency or precision fix rather than a new procedure.
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 fellingdater or graphicalMCP.
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
See all fellingdater alternatives → · See all graphicalMCP alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. fellingdater and graphicalMCP 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. fellingdater and graphicalMCP 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 fellingdater alternatives in Analytics are ranked by recent ship velocity. Browse the "fellingdater alternatives" section above for the current picks, or visit /alternatives/fellingdater for the full list with editorial commentary on each.
Top graphicalMCP alternatives in Analytics are ranked by recent ship velocity. Browse the "graphicalMCP alternatives" section above for the current picks, or visit /alternatives/graphicalmcp for the full list with editorial commentary on each.