rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
radiatR vs writeAlizer
A side-by-side editorial comparison of radiatR and writeAlizer — release velocity, themes, recent moves, and the top alternatives to consider.
radiatR vs writeAlizer: at a glance
What is radiatR?
A circular-statistics toolkit for animal movement, shipped and then tightened in three weeks.
radiatR reads movement trajectories, plots them on circular axes, computes kinematics such as speed and path sinuosity, and runs the circular statistics that go with them, including tests of mean direction, symmetry and unimodality. It arrived as a first public release on 9 July 2026 with an accompanying Shiny app, and has had two releases since at roughly weekly intervals. The 0.1.x line is still setting its boundaries: 0.1.2 removes a loader dialect and makes previously silent data problems into errors.
What is writeAlizer?
Six months of releases and not one of them touched the scoring models
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
radiatR vs writeAlizer: editorial side-by-side
radiatR
2.5INFRA · APIS
A circular-statistics toolkit for animal movement, shipped and then tightened in three weeks.
◆ Current state
radiatR reads movement trajectories, plots them on circular axes, computes kinematics such as speed and path sinuosity, and runs the circular statistics that go with them, including tests of mean direction, symmetry and unimodality. It arrived as a first public release on 9 July 2026 with an accompanying Shiny app, and has had two releases since at roughly weekly intervals. The 0.1.x line is still setting its boundaries: 0.1.2 removes a loader dialect and makes previously silent data problems into errors.
◆ Where it's heading
Three releases in twelve days show a package hardening in public rather than accreting features. The direction of travel is toward refusing bad input instead of quietly working around it: non-finite coordinate rows now error by default rather than being dropped silently, combining Tracks objects rejects colliding trajectory ids and conflicting calibration metadata instead of merging them and discarding one side, and the Shiny app clears prior state before reading a new upload. The statistical surface is growing in parallel, but within the scope the first release already claimed.
◆ Prediction
Expect the remaining goodness-of-fit gap the notes name explicitly, Jones-Pewsey, to be filled in a later release, and the error-on-bad-input treatment to reach the parts of the loader it has not yet covered. A CRAN submission is the natural next step for a package this young, though nothing in these entries commits to one.
writeAlizer
0.0INFRA · APIS
Six months of releases and not one of them touched the scoring models
◆ Current state
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
◆ Where it's heading
The package is being made safe to distribute. CRAN's policy on packages that reach the internet drove the first wave — graceful failure, tests that preflight their URLs and skip, examples seeded from a local mock model — and 1.7.0 turned the accumulated fixes into structure with named error classes for each failure mode. Only 1.7.2 adds anything a user would ask for: filename handling for Coh-Metrix and GAMET outputs that arrive as paths.
◆ Prediction
With the artifact registry hardened and documented, the pressure that produced nine releases in six months should ease, and attention can return to the models themselves — the vignette on scoring-model development added in 1.7.2 hints at that. Nothing here promises new models.
Alternatives to radiatR and writeAlizer
Other Infra & APIs 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 radiatR or writeAlizer.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
GeoThinneR
Spatial thinning grows a result object, and the API breaks to make room for it
See all radiatR alternatives → · See all writeAlizer alternatives →
Recent activity from radiatR and writeAlizer
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoradiatRctrax loader dropped; bad coordinates now error by default
- 1mo agoradiatRWrapped-Cauchy and Pycke tests close two statistical gaps
- 1mo agoradiatRFirst public release ⚡
- 6mo agowriteAlizerOne example rewrapped to silence a CRAN check note
- 8mo agowriteAlizerFilename stems recovered from Coh-Metrix and GAMET paths
- 10mo agowriteAlizerOffline example guard, declared as no API change
- 10mo agowriteAlizerNamed error classes for every model-download failure mode
- 10mo agowriteAlizerNetwork failures degrade gracefully under CRAN policy
- 11mo agowriteAlizerwa_seed_example_models() exported and documented
Frequently asked questions
What is the difference between radiatR and writeAlizer?
They serve adjacent needs but don't currently overlap on shipped themes. radiatR is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is radiatR better than writeAlizer?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. radiatR is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to radiatR?
Top radiatR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "radiatR alternatives" section above for the current picks, or visit /alternatives/radiatr for the full list with editorial commentary on each.
What are the best alternatives to writeAlizer?
Top writeAlizer alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "writeAlizer alternatives" section above for the current picks, or visit /alternatives/writealizer for the full list with editorial commentary on each.