← Back to home
Comparison · Analytics

edibble vs r2dii.plot

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

Shared themes:r-package

edibble vs r2dii.plot: at a glance

Featureedibbler2dii.plot
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesexperimental-design, grammar-of-design, reproducibility, simulationclimate-finance, data-visualization, pacta, ggplot2
Last editorial update30m ago37m ago
WebsiteVisit →Visit →

What is edibble?

A grammar for experimental design that learned to compose designs and track its own provenance.

edibble expresses experimental designs declaratively — units, treatments, records and their allotments — rather than calling a canned design function. Since 1.0.0 its internals run on a Provenance object that records the commands used to build a design, and 1.1.0 added conditional treatments, design composition and a separated simulation step. Recent work has focused on designs constructed from existing data rather than from scratch.

Read the full edibble trajectory →

What is r2dii.plot?

PACTA's climate-alignment charting layer split prep from plotting, then settled into stable.

r2dii.plot renders the standard PACTA climate-alignment charts — trajectory, tech mix, emission intensity — as ggplot2 objects, paired with the 2DII colour palettes and theme. Since 0.4.0 the package has exposed a two-step pipeline where prep_*() shapes the data before plot_*() draws it, while qplot_*() remains the one-call convenience path. It declared itself stable in early 2025.

Read the full r2dii.plot trajectory →

edibble vs r2dii.plot: editorial side-by-side

E
edibble
ANALYTICS
0.0

A grammar for experimental design that learned to compose designs and track its own provenance.

◆ Current state

edibble expresses experimental designs declaratively — units, treatments, records and their allotments — rather than calling a canned design function. Since 1.0.0 its internals run on a Provenance object that records the commands used to build a design, and 1.1.0 added conditional treatments, design composition and a separated simulation step. Recent work has focused on designs constructed from existing data rather than from scratch.

◆ Where it's heading

Development has moved from vocabulary to composition. Early releases established the core grammar; 1.0.0 replaced the internal R6 machinery with a Provenance object that tracks both internal and external commands, which is what lets a design carry its own construction history. On that foundation 1.1.0 added the ability to add two designs together, express conditional treatment structures, and split simulation specification from execution. The 2025 release turns toward a different entry point — wiring up level edges and unit attributes when an edibble object is built from data that already exists, rather than from a design declared up front.

◆ Prediction

Expect continued work on designs derived from existing data, since that is where the last release concentrated and it is the path least covered by the declarative grammar.

R
r2dii.plot
ANALYTICS
0.0

PACTA's climate-alignment charting layer split prep from plotting, then settled into stable.

◆ Current state

r2dii.plot renders the standard PACTA climate-alignment charts — trajectory, tech mix, emission intensity — as ggplot2 objects, paired with the 2DII colour palettes and theme. Since 0.4.0 the package has exposed a two-step pipeline where prep_*() shapes the data before plot_*() draws it, while qplot_*() remains the one-call convenience path. It declared itself stable in early 2025.

◆ Where it's heading

The package has been converging on a settled contract for years. Early releases chased visual polish and label handling, then 0.2.0 exposed the palette scales as reusable ggplot2 components, and 0.4.0 made the prepared data a first-class artefact rather than something hidden inside a plotting call. Recent releases are documentation and hygiene: a data_dictionary describing every column, definitions filled in, demo datasets renamed to say they are demos. It also moved organisations, from 2DII to RMI-PACTA, and its releases stay pinned to r2dii.analysis and to ggplot2's deprecation schedule.

◆ Prediction

With the lifecycle marked stable and the last two releases confined to dataset naming and documentation, the next release is most likely another ggplot2 compatibility pass or a sibling-package alignment rather than new chart types.

Alternatives to edibble and r2dii.plot

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 edibble or r2dii.plot.

See all edibble alternatives → · See all r2dii.plot alternatives →

Recent activity from edibble and r2dii.plot

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

  1. 1y agor2dii.plotBundled datasets renamed to mark them as demos
  2. 1y agoedibbleBetter handling of designs built from existing data
  3. 1y agor2dii.plotColumn definitions added to the data dictionary
  4. 1y agor2dii.plotData dictionary lands and the package declares itself stable
  5. 2y agor2dii.plotr2dii.plot 0.4.0
  6. 2y agoedibbleedibble 1.1.0
  7. 2y agoedibbleInternals rebuilt on a command-tracking Provenance object
  8. 3y agoedibbleS3 consistency and citation modernised
  9. 3y agor2dii.plotPACTA colour palettes exposed as datasets after org move
  10. 3y agoedibbleRd files fixed for HTML5 compatibility
  11. 4y agoedibbleInitial release
  12. 4y agor2dii.plotTrajectory plots move to percentage scaling alongside r2dii.analysis

Frequently asked questions

What is the difference between edibble and r2dii.plot?

Both compete on the same themes — r-package — within Analytics. edibble and r2dii.plot 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 edibble better than r2dii.plot?

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

What are the best alternatives to edibble?

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

What are the best alternatives to r2dii.plot?

Top r2dii.plot alternatives in Analytics are ranked by recent ship velocity. Browse the "r2dii.plot alternatives" section above for the current picks, or visit /alternatives/r2dii-plot for the full list with editorial commentary on each.