← Back to home
Comparison · Infra & APIs

ggInterval vs profoc

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

Shared themes:r-package

ggInterval vs profoc: at a glance

FeatureggIntervalprofoc
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessymbolic-data-analysis, interval-data, ggplot2, data-visualizationforecasting, online-learning, r-package, rcpp
Last editorial update1h ago1d ago
WebsiteVisit →Visit →

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 →

What is profoc?

A forecast combination package that spun its profiler out into its own project

profoc combines probabilistic forecasts online, using the Bernstein online aggregation family with B-spline smoothing over quantiles and time. The recent releases are infrastructure rather than method: 1.3.4 removed a using namespace arma directive for CRAN compliance and closed a timer edge case, 1.3.3 adjusted the integration with rcpptimer against its now-stable 1.2.0 API. The last release to change what users can do was 1.3.0, which exposed the conline C++ class to R and exported init_experts_list(), make_basis_mats(), make_hat_mats() and post_process_model() so the engine can be driven directly.

Read the full profoc trajectory →

ggInterval vs profoc: editorial side-by-side

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.

P
profoc
INFRA · APIS
0.0

A forecast combination package that spun its profiler out into its own project

◆ Current state

profoc combines probabilistic forecasts online, using the Bernstein online aggregation family with B-spline smoothing over quantiles and time. The recent releases are infrastructure rather than method: 1.3.4 removed a using namespace arma directive for CRAN compliance and closed a timer edge case, 1.3.3 adjusted the integration with rcpptimer against its now-stable 1.2.0 API. The last release to change what users can do was 1.3.0, which exposed the conline C++ class to R and exported init_experts_list(), make_basis_mats(), make_hat_mats() and post_process_model() so the engine can be driven directly.

◆ Where it's heading

The direction is toward a reusable C++ core with thin language bindings. The timing code that lived inside profoc was extracted into the standalone rcpptimer package in 1.3.2, deliberately so other R packages and Python projects could use it through cpptimer and cppytimer, and the clock header was reworked in 1.3.1 to maximise the code shared between the R and Python versions. Method work sits earlier in the history - periodic splines and penalties in 1.2.0, the penalty() function in 1.1.0 - while the recent cadence, a single release in the last sixteen months, points at a package the maintainer considers finished.

◆ Prediction

The repeated references to future Python use suggest the next significant work happens outside this package, in the shared C++ components, rather than in profoc's R surface.

Alternatives to ggInterval and profoc

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

See all ggInterval alternatives → · See all profoc alternatives →

Recent activity from ggInterval and profoc

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

  1. 3mo agoggIntervalInterval correlation heatmaps and time-series-compatible line plots
  2. 6mo agoggIntervalExamples switched to donttest per CRAN review
  3. 6mo agoggIntervalVignette rewritten to cover every plot function
  4. 6mo agoggIntervalSeven plot functions renamed for consistency
  5. 6mo agoprofocCRAN compliance fix removing a namespace directive
  6. 1y agoprofocTimer integration updated to the stable rcpptimer API
  7. 2y agoprofocTiming code extracted into the standalone rcpptimer package
  8. 2y agoprofocInteger overflow fix and Welford timing statistics
  9. 2y agoprofocThe conline C++ class opens up to R users
  10. 2y agoprofocQuantile crossing flagged and tidy methods added

Frequently asked questions

What is the difference between ggInterval and profoc?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggInterval and profoc 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 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.

What are the best alternatives to profoc?

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