← Back to home
Comparison · Analytics

chattr vs fellingdater

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

chattr vs fellingdater: at a glance

Featurechattrfellingdater
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesllm, rstudio, ide-integration, ellmerdendrochronology, crossdating, archaeology, ropensci
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is chattr?

chattr deleted every LLM integration it had written and outsourced the lot to ellmer

chattr puts a large language model inside the RStudio IDE, either through a Shiny app or directly at the console. As of 0.3.0 it no longer talks to any model provider itself: all integration goes through ellmer, and the hand-written OpenAI, Databricks and LlamaGPT backends were removed. The package's supported model list is now whatever ellmer supports, and the Shiny app streams responses through ellmer rather than managing a background process.

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

chattr vs fellingdater: editorial side-by-side

C
chattr
ANALYTICS
0.0

chattr deleted every LLM integration it had written and outsourced the lot to ellmer

◆ Current state

chattr puts a large language model inside the RStudio IDE, either through a Shiny app or directly at the console. As of 0.3.0 it no longer talks to any model provider itself: all integration goes through ellmer, and the hand-written OpenAI, Databricks and LlamaGPT backends were removed. The package's supported model list is now whatever ellmer supports, and the Shiny app streams responses through ellmer rather than managing a background process.

◆ Where it's heading

The first two releases show why that happened. Each provider brought its own error formats, token discovery and response handling, and 0.2.0 is largely a list of per-provider repairs — OpenAI error parsing, Copilot token discovery and model defaults, a new Databricks foundation model backend. Maintaining that surface scales linearly with the number of providers, and the pivot to ellmer trades it for a single dependency. The cost shows up immediately in 0.3.1, which exists solely to absorb a change in ellmer's token object.

◆ Prediction

Expect chattr's releases to now track ellmer's, as 0.3.1 already does, with the package's own work concentrating on the IDE experience rather than model connectivity. New provider support will arrive without a chattr release at all.

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

See all chattr alternatives → · See all fellingdater alternatives →

Recent activity from chattr and fellingdater

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

  1. 4mo agofellingdaterPolish for the crossdating plots and file reader
  2. 0y agochattrAdapts to ellmer's token object change
  3. 1y agofellingdaterAdds a full crossdating and tree-ring analysis toolkit
  4. 1y agofellingdaterUser-supplied sapwood data works across all functions
  5. 1y agochattrAll model integration moves to ellmer, direct backends removed
  6. 1y agofellingdaterFixes fd_report() with user-defined sapwood files
  7. 2y agochattrDatabricks foundation models added; per-provider error handling fixed
  8. 2y agofellingdaterJOSS paper accepted; citation updated
  9. 2y agofellingdaterAdds a workflow vignette ahead of JOSS submission
  10. 2y agochattrFirst release: LLM chat in the RStudio console and app

Frequently asked questions

What is the difference between chattr and fellingdater?

They serve adjacent needs but don't currently overlap on shipped themes. chattr 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 chattr better than fellingdater?

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

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