← Back to home
Comparison · Analytics

broman vs pecan

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

Shared themes:r-package

broman vs pecan: at a glance

Featurebromanpecan
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesstatistics, base-graphics, utilities, r-packageecosystem-modeling, data-assimilation, scientific-workflow, r-package
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is broman?

A statistician's personal toolbox, growing one plotting utility at a time

broman is Karl Broman's collection of personal R utilities — base-graphics plotting helpers such as grayplot, dotplot and timeplot, running-window summaries, and assorted conveniences. Recent releases alternate between small additions, like runningratio2() with an adaptive window sized to hit a target denominator, and narrow bug fixes in crayons() and jiggle(). Version 0.92 removes an include that had begun warning on CRAN.

Read the full broman trajectory →

What is pecan?

PEcAn v1.10 makes land-management events a first-class input and parallelises the whole SDA workflow

PEcAn is a workflow framework for ecosystem modelling — it standardises meteorological and initial-condition inputs, drives a set of coupled process models such as SIPNET, ED2, BioCro and LDNDC, and runs uncertainty analysis and state data assimilation over the results. Version 1.10.0 adds an events schema with validation and a SIPNET writer, so disturbance and management events can be declared in JSON and turned into model input, and runs the entire SDA workflow in parallel. It also adds CH4 and N2O to the standard variable table and an AmeriFlux meteorological ensemble path with ERA5 fallback.

Read the full pecan trajectory →

broman vs pecan: editorial side-by-side

B
broman
ANALYTICS
0.0

A statistician's personal toolbox, growing one plotting utility at a time

◆ Current state

broman is Karl Broman's collection of personal R utilities — base-graphics plotting helpers such as grayplot, dotplot and timeplot, running-window summaries, and assorted conveniences. Recent releases alternate between small additions, like runningratio2() with an adaptive window sized to hit a target denominator, and narrow bug fixes in crayons() and jiggle(). Version 0.92 removes an include that had begun warning on CRAN.

◆ Where it's heading

The additions cluster around two themes: time-axis plotting and running-window summaries, both of which have been extended across several releases. Nothing here is planned in the usual sense — functions appear when the author needs them and bugs are fixed when they surface downstream, as jiggle() did through dotplot(). The C-level cleanup in 0.92 matches the same change made to R/qtl the same week, which is what maintaining a set of packages under one author looks like.

◆ Prediction

Both recent function additions extend existing families rather than starting new ones, so the next release is most likely another variant in the running-window or time-plotting group, or a fix surfaced by one of the author's other packages.

P
pecan
ANALYTICS
0.0

PEcAn v1.10 makes land-management events a first-class input and parallelises the whole SDA workflow

◆ Current state

PEcAn is a workflow framework for ecosystem modelling — it standardises meteorological and initial-condition inputs, drives a set of coupled process models such as SIPNET, ED2, BioCro and LDNDC, and runs uncertainty analysis and state data assimilation over the results. Version 1.10.0 adds an events schema with validation and a SIPNET writer, so disturbance and management events can be declared in JSON and turned into model input, and runs the entire SDA workflow in parallel. It also adds CH4 and N2O to the standard variable table and an AmeriFlux meteorological ensemble path with ERA5 fallback.

◆ Where it's heading

Two directions are visible. The framework keeps widening what it can represent — more standard variables, more carbon pools in BADM-based initial conditions, more coupled models — and it keeps industrialising the parts that used to be manual, from automated package documentation to qsub job-array expansion to parallel assimilation. The events schema is the first of these that gives users a declarative input format rather than a function to call, which is a different kind of extension than adding another model coupling.

◆ Prediction

The events schema currently has one model writer, for SIPNET, so the obvious next step is writers for the other coupled models — otherwise the format only benefits a single backend of the several PEcAn drives.

Alternatives to broman and pecan

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 broman or pecan.

See all broman alternatives → · See all pecan alternatives →

Recent activity from broman and pecan

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

  1. 7mo agopecanEvents schema, parallel SDA workflow, CH4 and N2O standard variables
  2. 8mo agobromanRemove R_ext/PrtUtil.h include flagged by CRAN
  3. 10mo agobromanFix exact-name matching in crayons()
  4. 11mo agobromanFix jiggle() with factors missing levels
  5. 1y agobromanrunningratio2() uses an adaptive window
  6. 1y agopecanAutomated pkgdown docs for all packages; qsub job-array support
  7. 1y agopecanLDNDC coupling, soilgrids carbon extraction, SDA observation prep
  8. 1y agopecanPFT-specific sensitivity analysis and BioCro 1.0 support
  9. 1y agopecanBioCro output renamed to PEcAn standard names; RCE fix
  10. 1y agopecanPEcAn.utils namespace cleanup; deprecated model2netcdf removed
  11. 2y agobromantimeplot() added; running functions accept NAs
  12. 2y agobromantime_axis() added for date-time axis labels

Frequently asked questions

What is the difference between broman and pecan?

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

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

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

What are the best alternatives to pecan?

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