← Back to home
Comparison · Analytics

dendroNetwork vs fellingdater

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

Shared themes:dendrochronologyarchaeologyropensci

dendroNetwork vs fellingdater: at a glance

FeaturedendroNetworkfellingdater
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdendrochronology, network-analysis, cytoscape, archaeologydendrochronology, crossdating, archaeology, ropensci
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is dendroNetwork?

Six releases, six identical bodies — the feed carries the package abstract instead of release notes

dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.

Read the full dendroNetwork trajectory →

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 →

dendroNetwork vs fellingdater: editorial side-by-side

D
dendroNetwork
ANALYTICS
0.0

Six releases, six identical bodies — the feed carries the package abstract instead of release notes

◆ Current state

dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.

◆ Where it's heading

What the timestamps show is more informative than the text. Versions 0.5.0 through 0.5.3 were all published within two minutes of each other on 12 April 2024, and in descending version order, which is the signature of a release history backfilled in one pass rather than four separate releases. Real releases follow at 0.5.4 a fortnight later and 0.5.5 fifteen months after that. Development is slow and, on this evidence, undocumented.

◆ Prediction

No prediction is supportable from these entries — none of them describe a change. Any read on where this package is heading would need the NEWS file or the commit history rather than the feed.

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.

Alternatives to dendroNetwork and fellingdater

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 dendroNetwork or fellingdater.

See all dendroNetwork alternatives → · See all fellingdater alternatives →

Recent activity from dendroNetwork and fellingdater

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

  1. 4mo agofellingdaterPolish for the crossdating plots and file reader
  2. 1y agodendroNetworkdendroNetwork 0.5.5
  3. 1y agofellingdaterAdds a full crossdating and tree-ring analysis toolkit
  4. 1y agofellingdaterUser-supplied sapwood data works across all functions
  5. 1y agofellingdaterFixes fd_report() with user-defined sapwood files
  6. 2y agofellingdaterJOSS paper accepted; citation updated
  7. 2y agofellingdaterAdds a workflow vignette ahead of JOSS submission
  8. 2y agodendroNetworkdendroNetwork 0.5.4
  9. 2y agodendroNetworkdendroNetwork 0.5.0
  10. 2y agodendroNetworkdendroNetwork 0.5.1
  11. 2y agodendroNetworkdendroNetwork 0.5.2
  12. 2y agodendroNetworkdendroNetwork 0.5.3

Frequently asked questions

What is the difference between dendroNetwork and fellingdater?

Both compete on the same themes — dendrochronology, archaeology, ropensci — within Analytics. dendroNetwork and fellingdater 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 dendroNetwork better than fellingdater?

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

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

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.