phyloatlas
An atlas of the tree of life that keeps publishing what it got wrong, and stopped shipping the trees it does not own.
Comparison · Infra & APIs
gkwdist vs projoint
A side-by-side editorial comparison of gkwdist and projoint — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
gkwdist vs projoint: at a glance
What is gkwdist?
gkwdist keeps finding that its distributions were returning the wrong numbers.
The package implements the Generalized Kumaraswamy distribution family and its sub-families. The current release fixes six numerical defects, the most serious being that dgkw() returned zero for every input because internal helpers collided with same-named functions in R's public Rmath.h header. Log-likelihoods for three sub-families were also wrong for data near zero due to clamping instead of working in log space.
What is projoint?
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
gkwdist vs projoint: editorial side-by-side
gkwdist
2.5INFRA · APIS
gkwdist keeps finding that its distributions were returning the wrong numbers.
◆ Current state
The package implements the Generalized Kumaraswamy distribution family and its sub-families. The current release fixes six numerical defects, the most serious being that dgkw() returned zero for every input because internal helpers collided with same-named functions in R's public Rmath.h header. Log-likelihoods for three sub-families were also wrong for data near zero due to clamping instead of working in log space.
◆ Where it's heading
Every release in this window is correctness work with an unchanged public API — critical MLE fixes in 1.1.3, a CRAN timing-test patch in 1.1.4, numerical corrections in 1.1.5. The recurring theme is that analytically correct formulas were being defeated by implementation details: name collisions, sign errors returning negative infinity where positive was required, and clamping thresholds that destroyed precision in the tails. Test infrastructure added in 1.1.2 validates analytical derivatives against numerical differentiation, which is how several of these were caught.
◆ Prediction
Expect further validation-driven fixes rather than new distributions, since the derivative-checking suite added earlier is still surfacing defects in existing routines.
projoint
2.5INFRA · APIS
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
◆ Current state
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
◆ Where it's heading
The maintainer is hardening the path from raw Qualtrics export to estimate, which is where conjoint analysis quietly goes wrong. Three separate releases fix that path: dropped respondent-level weights in organize_data(), repeated-task reshaping in reshape_projoint(), and choice-to-profile mapping in 1.1.3. Each fix now arrives with regression tests and stricter validation rather than just a patch, and 1.1.3 adds an explicit .choice_map so the mapping is auditable instead of inferred.
◆ Prediction
Expect the validation-and-regression-test pattern to keep extending across the import path, with releases continuing to arrive in bursts around CRAN submission rather than on a cadence.
Alternatives to gkwdist and projoint
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 gkwdist or projoint.
OpenLand
Land-change analysis in R that has spent six years defending one download link.
FoRecoML
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
FoReco
Forecast reconciliation with a real object model, five years after it started returning bare matrices.
wooldridge
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
L1centrality
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
See all gkwdist alternatives → · See all projoint alternatives →
Recent activity from gkwdist and projoint
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7d agogkwdistv1.1.5 — Numerical correctness fixes and componentwise derivative validation
- 17d agoprojointExplicit .choice_map guards choice-to-profile mapping
- 1mo agoprojointCRAN submission housekeeping for DESCRIPTION and examples
- 1mo agoprojointCRAN formatting pass; minor make_projoint_data() fix
- 1mo agoprojointreshape_projoint() repeated-task bug fixed; validation tightened
- 1mo agoprojointCitation metadata updated with the CRAN DOI
- 2mo agogkwdistv1.1.4 — CRAN fix: skip timing-based tests on CRAN
- 3mo agogkwdistv1.1.3 — Critical MLE Bug Fixes & Numerical Corrections
- 5mo agoprojointorganize_data() no longer drops respondent-level weights
- 7mo agogkwdistAdds analytical derivative validation across all sub-families
- 8mo agogkwdistRefactors the C++ backend around stable log-space utilities
Frequently asked questions
What is the difference between gkwdist and projoint?
Both compete on the same themes — r-package — within Infra & APIs. gkwdist and projoint are shipping at a similar cadence (velocity 2.5 vs 2.5, 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 gkwdist better than projoint?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gkwdist and projoint are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to gkwdist?
Top gkwdist alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gkwdist alternatives" section above for the current picks, or visit /alternatives/gkwdist for the full list with editorial commentary on each.
What are the best alternatives to projoint?
Top projoint alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "projoint alternatives" section above for the current picks, or visit /alternatives/projoint for the full list with editorial commentary on each.