nat.nblast
The NBLAST neuron-similarity engine is stable code on life support, shipping once every few years.
A side-by-side editorial comparison of atrrr and rnpn — release velocity, themes, recent moves, and the top alternatives to consider.
The R client for Bluesky adds a firehose and stops assuming Bluesky is the server
atrrr wraps the AT Protocol for R, covering posting, search, profiles, lists, direct messages and starter packs. The latest release adds an experimental firehose implementation and allows connecting to personal data servers other than Bluesky's — Eurosky is the example given. Earlier releases built out the posting surface: videos, multiple images, link preview cards, hashtags, and ggplot2 objects posted directly.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
rnpn is the R client for the USA National Phenology Network, retrieving observation records, phenometrics and gridded model layers. Version 1.3.0 in March 2025 replaced nearly all of its infrastructure at once — sp and raster dropped, terra made optional, XML swapped for xml2, plyr for dplyr, httr and curl for httr2 — and changed what functions return, with tibbles in place of data.tables and empty tibbles in place of NULL on error. The two releases since have completed the missing-value handling and restored performance lost in the transition.
atrrr wraps the AT Protocol for R, covering posting, search, profiles, lists, direct messages and starter packs. The latest release adds an experimental firehose implementation and allows connecting to personal data servers other than Bluesky's — Eurosky is the example given. Earlier releases built out the posting surface: videos, multiple images, link preview cards, hashtags, and ggplot2 objects posted directly.
Two years of work made atrrr a capable REST client for one network. This release starts undoing that second part. The firehose is a different access mode — a stream rather than a request — which is what researchers doing collection at scale need, and PDS-agnosticism means the package addresses the protocol rather than the company. The rest of the changelog is steadily maintenance-shaped: repeated httr2 compatibility work, endpoint changes tracked as they happen.
The firehose is labelled experimental, so the next release most likely stabilises it rather than opening another front — though the notes give no detail on what remains unfinished.
rnpn is the R client for the USA National Phenology Network, retrieving observation records, phenometrics and gridded model layers. Version 1.3.0 in March 2025 replaced nearly all of its infrastructure at once — sp and raster dropped, terra made optional, XML swapped for xml2, plyr for dplyr, httr and curl for httr2 — and changed what functions return, with tibbles in place of data.tables and empty tibbles in place of NULL on error. The two releases since have completed the missing-value handling and restored performance lost in the transition.
The package is being brought onto the current R stack and made honest about missing data, and those are the same project. Converting the -9999 sentinel to NA started in 1.3.0 for download functions and was extended to all columns in 1.4.1; the string "emptyvalue" got the same treatment. Beyond the migration, the feature additions are modest and specific to the domain, such as custom start and end dates for defining a phenometrics season.
With the dependency migration finished and sentinel handling now applied across all columns, the next releases most likely return to domain features and to fixes surfaced by the server side, which has already prompted work through migrations and backend moves. The removed progress indicator is an acknowledged regression that may come back.
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 atrrr or rnpn.
The NBLAST neuron-similarity engine is stable code on life support, shipping once every few years.
A random-walk generator that outgrew one dimension and renamed its core column to prove it.
Time-based rolling statistics for water-quality data, finally getting plotting and padding built in.
A roxygen2 documentation-reuse helper whose release notes are mostly upstream damage control.
The tidy front-end for GAMs, now stable enough that upstream ggplot2 sets its release calendar.
A safer case_when that keeps hardening its guarantees while realigning to tidyverse naming.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. atrrr and rnpn 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. atrrr and rnpn 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 atrrr alternatives in Analytics are ranked by recent ship velocity. Browse the "atrrr alternatives" section above for the current picks, or visit /alternatives/atrrr for the full list with editorial commentary on each.
Top rnpn alternatives in Analytics are ranked by recent ship velocity. Browse the "rnpn alternatives" section above for the current picks, or visit /alternatives/rnpn for the full list with editorial commentary on each.