← Back to home
Comparison · Infra & APIs

cvms vs ggInterval

A side-by-side editorial comparison of cvms and ggInterval — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

cvms vs ggInterval: at a glance

FeaturecvmsggInterval
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themescross-validation, r-package, model-evaluation, visualizationsymbolic-data-analysis, interval-data, ggplot2, data-visualization
Last editorial update1d ago1h ago
WebsiteVisit →Visit →

What is cvms?

A cross-validation package whose real development has moved to its plotting function

cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.

Read the full cvms trajectory →

What is ggInterval?

Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.

ggInterval visualizes symbolic interval-valued data — observations recorded as ranges rather than points — with a family of plot functions in the ggplot2 idiom. The plot catalogue grew most recently with interval correlation heatmaps and interval line plots compatible with time-series input. The three releases before that were corrections: seven plot functions renamed for consistency, examples switched from dontrun to donttest at CRAN's request, and a vignette rewritten to demonstrate every function in one place.

Read the full ggInterval trajectory →

cvms vs ggInterval: editorial side-by-side

C
cvms
INFRA · APIS
0.0

A cross-validation package whose real development has moved to its plotting function

◆ Current state

cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.

◆ Where it's heading

Two threads run in parallel and only one is about cross-validation. The plotting function plot_confusion_matrix() has absorbed most feature work since 1.5.0 - custom gradient palettes, intensity limits, per-tile settings, dynamic font colors keyed to value thresholds, and arguments that accept functions rather than constants - to the point where a companion web application exists for using it without code. The cross-validation core, by contrast, sees maintenance: upstream compatibility fixes for pROC, ggnewscale and ggplot2, and the fold-matching correction that finally forced a major version.

◆ Prediction

Expect continued option growth in the confusion matrix plotting surface, since that is where nearly every release since 1.5.0 has spent its changes, with core cross-validation changes arriving only as upstream packages force them.

G
ggInterval
INFRA · APIS
0.0

Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.

◆ Current state

ggInterval visualizes symbolic interval-valued data — observations recorded as ranges rather than points — with a family of plot functions in the ggplot2 idiom. The plot catalogue grew most recently with interval correlation heatmaps and interval line plots compatible with time-series input. The three releases before that were corrections: seven plot functions renamed for consistency, examples switched from dontrun to donttest at CRAN's request, and a vignette rewritten to demonstrate every function in one place.

◆ Where it's heading

The package is consolidating an interface that had drifted. Renaming seven functions in a single release is the clearest signal — the naming was inconsistent enough to be worth breaking, and the vignette rewrite that followed suggests discoverability was the underlying complaint. Underneath that, the additions are steady and narrow: each release brings interval-aware versions of plot types that already exist for point data, which is the whole premise of the package.

◆ Prediction

The pattern of porting one more standard plot type into interval-aware form each release is the most likely continuation; the tsplot compatibility in the latest version hints that time-series interval data is the direction attracting attention.

Alternatives to cvms and ggInterval

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 cvms or ggInterval.

See all cvms alternatives → · See all ggInterval alternatives →

Recent activity from cvms and ggInterval

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2mo agocvmsCoefficient extraction restored for multinom and mixed models
  2. 3mo agoggIntervalInterval correlation heatmaps and time-series-compatible line plots
  3. 6mo agoggIntervalExamples switched to donttest per CRAN review
  4. 6mo agoggIntervalVignette rewritten to cover every plot function
  5. 6mo agoggIntervalSeven plot functions renamed for consistency
  6. 9mo agocvmsBreaking fix for mismatched folds with non-sequential fold IDs
  7. 11mo agocvmsTest compatibility with pROC 1.19 and a deprecation warning fix
  8. 1y agocvmsConfusion matrix fonts and colors can now be computed from the values
  9. 1y agocvmsTile intensity by row or column percentages
  10. 1y agocvmsMultinom coefficient extraction fix after a parameters update

Frequently asked questions

What is the difference between cvms and ggInterval?

Both compete on the same themes — r-package — within Infra & APIs. cvms and ggInterval 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.

Is cvms better than ggInterval?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cvms and ggInterval 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to cvms?

Top cvms alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "cvms alternatives" section above for the current picks, or visit /alternatives/cvms for the full list with editorial commentary on each.

What are the best alternatives to ggInterval?

Top ggInterval alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ggInterval alternatives" section above for the current picks, or visit /alternatives/gginterval for the full list with editorial commentary on each.