exametrika
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
Comparison · Infra & APIs
profileCI vs projoint
A side-by-side editorial comparison of profileCI and projoint — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
profileCI vs projoint: at a glance
What is profileCI?
Profile-likelihood confidence intervals for any fitted model, in a feed that publishes out of order.
profileCI computes confidence intervals from the profile log-likelihood for user-supplied fitted models, generalising what confint.glm does for GLMs to any model object exposing a log-likelihood. The releases handle the awkward cases that make profiling fail in practice: infinite limits when the profile never drops below the interval threshold, bounded profiling ranges, and interpolation that breaks down near the limits. Only convex log-likelihoods are supported, so disjoint intervals are out of scope by design.
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.
profileCI vs projoint: editorial side-by-side
profileCI
0.0INFRA · APIS
Profile-likelihood confidence intervals for any fitted model, in a feed that publishes out of order.
◆ Current state
profileCI computes confidence intervals from the profile log-likelihood for user-supplied fitted models, generalising what confint.glm does for GLMs to any model object exposing a log-likelihood. The releases handle the awkward cases that make profiling fail in practice: infinite limits when the profile never drops below the interval threshold, bounded profiling ranges, and interpolation that breaks down near the limits. Only convex log-likelihoods are supported, so disjoint intervals are out of scope by design.
◆ Where it's heading
Work is concentrated on numerical reliability rather than scope: 1.1.1 replaced quadratic with monotonic cubic spline interpolation because the quadratic form could fail, and corrected parameter values stored near the confidence limits. The feed publishes these out of order, with the v1.0.0 entry stamped six months after v1.1.0 and carrying the package's full description rather than a changelog, so release order should be read from the version numbers rather than the dates. The same maintainer's revdbayes has been in pure maintenance across this period, which places profileCI as the more active project.
◆ Prediction
Expect further robustness work at the profiling limits and more logLikFn methods for common model classes, following the nls method added in 1.1.0.
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 profileCI 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 profileCI or projoint.
nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
eratosthenes
eratosthenes spends 0.1.0 hardening inputs rather than adding chronology methods.
dqcheckr
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
lifecontingencies
An actuarial mainstay spends its releases on CI plumbing, not on new mathematics.
EDAForge
EDAForge is a data-quality auditor renamed mid-flight, still finding its CRAN footing.
See all profileCI alternatives → · See all projoint alternatives →
Recent activity from profileCI and projoint
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 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
- 5mo agoprojointorganize_data() no longer drops respondent-level weights
- 6mo agoprofileCICubic spline interpolation replaces a quadratic that could fail
- 7mo agoprofileCICRAN 1.0.0 release of profile-likelihood interval computation
- 1y agoprofileCIInfinite limits and bounded profiling ranges handled
Frequently asked questions
What is the difference between profileCI and projoint?
Both compete on the same themes — r-package — within Infra & APIs. projoint 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 profileCI better than projoint?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. projoint 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 profileCI?
Top profileCI alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "profileCI alternatives" section above for the current picks, or visit /alternatives/profileci 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.