← Back to home
Comparison · Analytics

chromer vs fellingdater

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

Shared themes:ropenscir-package

chromer vs fellingdater: at a glance

Featurechromerfellingdater
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesropensci, r-package, api-client, biodiversitydendrochronology, crossdating, archaeology, ropensci
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

What is chromer?

A chromosome-count database client that only ever ships when the upstream API moves.

chromer is a thin R client for the Chromosome Counts Database. Every release in the past three years is maintenance: a new maintainer and licence change in 0.3, test-skipping when the upstream service is down in 0.4, and two separate releases whose entire content is that the database's URL changed again. The current 0.10 points at ccdb.tau.ac.il/services/.

Read the full chromer 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 →

chromer vs fellingdater: editorial side-by-side

C
chromer
ANALYTICS
0.0

A chromosome-count database client that only ever ships when the upstream API moves.

◆ Current state

chromer is a thin R client for the Chromosome Counts Database. Every release in the past three years is maintenance: a new maintainer and licence change in 0.3, test-skipping when the upstream service is down in 0.4, and two separate releases whose entire content is that the database's URL changed again. The current 0.10 points at ccdb.tau.ac.il/services/.

◆ Where it's heading

The package is functionally complete and externally driven — its release cadence is a record of the CCDB's hosting history rather than of any development plan. The defensive work in 0.4, which added an internal check for whether the database is down and skips tests accordingly, shows the maintainer treating upstream instability as the permanent condition rather than an incident.

◆ Prediction

The next release will most likely be triggered by another CCDB endpoint or format change; nothing in the history suggests new functionality is planned.

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

See all chromer alternatives → · See all fellingdater alternatives →

Recent activity from chromer and fellingdater

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

  1. 4mo agofellingdaterPolish for the crossdating plots and file reader
  2. 1y agochromerChromosome Counts Database endpoint moved again
  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 agochromerDatabase URL updated after upstream move
  9. 2y agochromerAPI calls switched to https
  10. 2y agochromerDocumentation tweak for a CRAN check
  11. 3y agochromerTests skipped when the upstream database is down
  12. 3y agochromerNew maintainer; licence changes from CC0 to MIT

Frequently asked questions

What is the difference between chromer and fellingdater?

Both compete on the same themes — ropensci, r-package — within Analytics. chromer 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 chromer better than fellingdater?

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

Top chromer alternatives in Analytics are ranked by recent ship velocity. Browse the "chromer alternatives" section above for the current picks, or visit /alternatives/chromer 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.