← Back to home
Comparison · Analytics

ggtrace vs simmer.plot

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

Shared themes:ggplot2r-package

ggtrace vs simmer.plot: at a glance

Featureggtracesimmer.plot
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesggplot2, debugging, ggproto, developer-toolingdiscrete-event-simulation, simmer, ggplot2, visualisation
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is ggtrace?

A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.

ggtrace lets users step inside ggplot2's rendering pipeline — tracing ggproto methods, dumping intermediate state, and snapshotting layer data at each stage via layer_before_stat(), layer_after_stat(), layer_before_geom() and layer_after_scale(). The workflow functions gained short aliases at 0.7.1, and recent releases have gone into making method resolution work on ggproto definitions written in forms the tracer did not originally expect.

Read the full ggtrace trajectory →

What is simmer.plot?

The plotting companion to simmer, shipping only when the simulator or a graphics dependency moves.

simmer.plot renders discrete-event simulation output — S3 plot() methods over get_mon_arrivals(), get_mon_attributes() and get_mon_resources(), plus trajectory diagrams drawn through DiagrammeR. Since 0.1.12 the methods attach to the monitoring data itself rather than the simulation environment, and 0.1.18 finished that migration by deleting the deprecated environment-level methods.

Read the full simmer.plot trajectory →

ggtrace vs simmer.plot: editorial side-by-side

G
ggtrace
ANALYTICS
0.0

A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.

◆ Current state

ggtrace lets users step inside ggplot2's rendering pipeline — tracing ggproto methods, dumping intermediate state, and snapshotting layer data at each stage via layer_before_stat(), layer_after_stat(), layer_before_geom() and layer_after_scale(). The workflow functions gained short aliases at 0.7.1, and recent releases have gone into making method resolution work on ggproto definitions written in forms the tracer did not originally expect.

◆ Where it's heading

The package matured from raw tracing primitives into named workflows: 0.6.0 added the sublayer snapshot functions and error-context helpers, 0.7.x has been sanding down how reliably those workflows find and evaluate a method. Three consecutive releases in May 2025, two of them minutes apart, all address the same class of failure — one-liner ggproto methods without braces, and inheritance resolution on instances rather than subclasses. That pattern says the remaining bugs are in method introspection, not in the tracing machinery itself.

◆ Prediction

Expect continued fixes to method resolution as ggplot2's ggproto definitions vary, and realignment work when ggplot2 4.x changes internals this package deliberately reaches into. The entries do not signal new workflow functions.

S
simmer.plot
ANALYTICS
0.0

The plotting companion to simmer, shipping only when the simulator or a graphics dependency moves.

◆ Current state

simmer.plot renders discrete-event simulation output — S3 plot() methods over get_mon_arrivals(), get_mon_attributes() and get_mon_resources(), plus trajectory diagrams drawn through DiagrammeR. Since 0.1.12 the methods attach to the monitoring data itself rather than the simulation environment, and 0.1.18 finished that migration by deleting the deprecated environment-level methods.

◆ Where it's heading

This package moves when something it depends on moves. Its history is a sequence of parser fixes for new simmer trajectory formats, DiagrammeR and tidyr and dplyr version bumps, and ggplot2 workarounds. The one clear internal decision — plotting monitor output instead of the environment — was made in 2017 and completed six years later. The 2025 release fixes documentation cross-references and nothing else.

◆ Prediction

The next release most likely follows a simmer trajectory-format change or a CRAN documentation policy, matching every recent entry. There is no visible feature work in the pipeline.

Alternatives to ggtrace and simmer.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 ggtrace or simmer.plot.

See all ggtrace alternatives → · See all simmer.plot alternatives →

Recent activity from ggtrace and simmer.plot

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

  1. 1y agosimmer.plotDocumentation cross-reference fixes
  2. 1y agoggtraceBrace-less one-liner methods traced gracefully
  3. 1y agoggtraceget_method_inheritance() fixed for class instances
  4. 1y agoggtraceWorkflow functions recognise one-liner ggproto methods
  5. 1y agoggtraceEager layer_is(), clearer method-mismatch errors, consistent tracedump names
  6. 1y agoggtracetrace_steps = "all" added; double-evaluation side effects fixed
  7. 1y agoggtracelayer_is() targets by_layer() downstream directly
  8. 3y agosimmer.plotActivity tags and named rollbacks; deprecated plot methods removed
  9. 4y agosimmer.plotZero-capacity utilization fixed; usage limits exposed
  10. 6y agosimmer.plotRollback pointer fix and upstream bug workarounds
  11. 8y agosimmer.plotResource plot factors keep the supplied order
  12. 8y agosimmer.plotUpdate for DiagrammeR 1.0.0

Frequently asked questions

What is the difference between ggtrace and simmer.plot?

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

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

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

What are the best alternatives to simmer.plot?

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