← Back to home
Comparison · Analytics

fellingdater vs lobstr

A side-by-side editorial comparison of fellingdater and lobstr — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

fellingdater vs lobstr: at a glance

Featurefellingdaterlobstr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdendrochronology, crossdating, archaeology, ropenscir-lib, introspection, memory, c-api
Last editorial update1h ago2h ago
WebsiteVisit →Visit →

What is fellingdater?

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.

Read the full fellingdater trajectory →

What is lobstr?

R's object inspector is losing its view of the internals as CRAN closes off the private C API.

lobstr exposes R's internal object representation — sizes, addresses, reference counts, abstract syntax trees. Its two most recent releases are both driven by R's move to a restricted public C API: 1.1.3 stopped reporting a vector's truelength and reworked the reference indicator into refs:n, and 1.2.0 changed what sxp(expand = "environment") shows in order to stay compliant. 1.2.0 also adds src() for exploring srcref objects.

Read the full lobstr trajectory →

fellingdater vs lobstr: editorial side-by-side

F
fellingdater
ANALYTICS
0.0

Went from estimating felling dates to doing the crossdating that produces them.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

L
lobstr
ANALYTICS
0.0

R's object inspector is losing its view of the internals as CRAN closes off the private C API.

◆ Current state

lobstr exposes R's internal object representation — sizes, addresses, reference counts, abstract syntax trees. Its two most recent releases are both driven by R's move to a restricted public C API: 1.1.3 stopped reporting a vector's truelength and reworked the reference indicator into refs:n, and 1.2.0 changed what sxp(expand = "environment") shows in order to stay compliant. 1.2.0 also adds src() for exploring srcref objects.

◆ Where it's heading

The package is being rebuilt inside a shrinking window of what R permits. Each release trades some introspection depth for API conformance while trying to keep the diagnostic value intact — showing promise expressions instead of internal frame structures, replacing named with a documented refs scale. Where the constraint does not bite, development continues normally: src() is genuinely new, and the environment-binding fixes remove long-standing errors on for-loop and immediate bindings.

◆ Prediction

Expect further conformance work, since the notes describe it as ongoing, with any remaining non-API-dependent readouts either reworked or dropped as R tightens further.

Alternatives to fellingdater and lobstr

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 lobstr.

See all fellingdater alternatives → · See all lobstr alternatives →

Recent activity from fellingdater and lobstr

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agofellingdaterPolish for the crossdating plots and file reader
  2. 5mo agolobstrNew src() for srcrefs; environment bindings stop erroring
  3. 9mo agolobstrtruelength reporting dropped for public C API compliance
  4. 1y agofellingdaterAdds a full crossdating and tree-ring analysis toolkit
  5. 1y agofellingdaterUser-supplied sapwood data works across all functions
  6. 1y agofellingdaterFixes fd_report() with user-defined sapwood files
  7. 2y agofellingdaterJOSS paper accepted; citation updated
  8. 2y agofellingdaterAdds a workflow vignette ahead of JOSS submission
  9. 4y agolobstrMoves to cpp11, relicensed MIT, adds experimental tree()
  10. 7y agolobstrPROTECT error fixed
  11. 7y agolobstrALTREP sizes computed correctly; obj_addr() stops side-effecting

Frequently asked questions

What is the difference between fellingdater and lobstr?

Both compete on the same themes — r-package — within Analytics. fellingdater and lobstr 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.

Is fellingdater better than lobstr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fellingdater and lobstr 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.

What are the best alternatives to fellingdater?

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.

What are the best alternatives to lobstr?

Top lobstr alternatives in Analytics are ranked by recent ship velocity. Browse the "lobstr alternatives" section above for the current picks, or visit /alternatives/lobstr for the full list with editorial commentary on each.