rjd3highfreq
rjd3highfreq ships whatever the Java side ships, and only occasionally says what that was.
A side-by-side editorial comparison of affiner and n1qn1c — release velocity, themes, recent moves, and the top alternatives to consider.
affiner is quietly turning a grid transformation helper into a small computational geometry library.
An R package that began as a wrapper around grid's affine transformation primitives, with an angle vector class supporting degrees, radians, half-turns, turns and gradians so users need not convert by hand. Four releases in roughly eighteen months. The recent two have expanded well past that starting point into geometric objects and the predicates that operate on them.
A Fortran-descended optimizer got thread-safe, then found two flags that never worked.
n1qn1c is a quasi-Newton optimization routine translated from Fortran to C, used as a solver backend by the nlmixr2 modeling stack rather than called directly by most users. Its two 2026 releases are a concentrated safety pass: global state converted to thread_local, static removed from local variables in the translated code, integer overflow guards added, and memory leaks closed in the R callback wrappers — plus the gcc-asan and valgrind fixes CRAN asked for.
An R package that began as a wrapper around grid's affine transformation primitives, with an angle vector class supporting degrees, radians, half-turns, turns and gradians so users need not convert by hand. Four releases in roughly eighteen months. The recent two have expanded well past that starting point into geometric objects and the predicates that operate on them.
The direction is clear from the order things arrived. Version 0.2.1 added the predicate layer first — has_intersection(), intersection(), is_equivalent() and is_parallel() as S3 generics working across angle vectors, points, lines and planes. Version 0.3.1 then supplied the objects those generics need, with Ellipse2D, Polygon2D and Segment2D R6 classes plus constructors for rectangles, regular n-gons and isotoxal star polygons, and dot products at one, two and three dimensions. Building the operations before the shapes is unusual ordering but it means each new object type arrives already composable with everything else.
Expect more 2D and 3D object types filling out the same generic interface, and the geometry side to keep outgrowing the grid-transformation wrapper the package was named for.
n1qn1c is a quasi-Newton optimization routine translated from Fortran to C, used as a solver backend by the nlmixr2 modeling stack rather than called directly by most users. Its two 2026 releases are a concentrated safety pass: global state converted to thread_local, static removed from local variables in the translated code, integer overflow guards added, and memory leaks closed in the R callback wrappers — plus the gcc-asan and valgrind fixes CRAN asked for.
The package is being hardened for use inside a parallel modeling framework rather than extended. The audit that produced the thread-safety work also surfaced two plain bugs in features users would have assumed worked: restart = TRUE left the mode at 2 instead of 3 because of a typo, and assign = TRUE referenced the wrong field name so the compressed Hessian was never written to the supplied environment. Earlier work points the same direction — the 6.0.1-12 function-pointer interface exists so nlmixr2est does not need resubmission when this package changes.
Expect further memory-safety and sanitizer work rather than algorithmic change; a Fortran-translated numerical core under CRAN's checking regime generates that kind of release indefinitely.
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 affiner or n1qn1c.
rjd3highfreq ships whatever the Java side ships, and only occasionally says what that was.
audubon's release feed is almost entirely Renovate bumping the JavaScript toolchain behind its Japanese text splitter.
ageproR spent two years chasing a moving file format, then added the recruitment models that justify the effort.
ledger adds a Rust toolchain fallback, so beancount imports work whether or not the Python tooling is installed.
gridpattern keeps widening its catalogue, and the newest patterns finally use the device's own line rendering.
distributional taught + and - to work on any pair of distributions, closing the algebra it started with.
See all affiner alternatives → · See all n1qn1c alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. affiner and n1qn1c 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. affiner and n1qn1c 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 affiner alternatives in Analytics are ranked by recent ship velocity. Browse the "affiner alternatives" section above for the current picks, or visit /alternatives/affiner-r for the full list with editorial commentary on each.
Top n1qn1c alternatives in Analytics are ranked by recent ship velocity. Browse the "n1qn1c alternatives" section above for the current picks, or visit /alternatives/n1qn1c for the full list with editorial commentary on each.