← Back to home
Comparison · Analytics

common vs r2dii.analysis

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

Shared themes:r-package

common vs r2dii.analysis: at a glance

Featurecommonr2dii.analysis
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-utilities, base-r-extensions, infix-operators, data-frame-toolsclimate-finance, portfolio-alignment, pacta, scenario-analysis
Last editorial update39m ago42m ago
WebsiteVisit →Visit →

What is common?

A base-R utility belt that grows one small function at a time, on no particular schedule

common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.

Read the full common trajectory →

What is r2dii.analysis?

The climate-alignment maths behind PACTA, now stable and maintained rather than reshaped

r2dii.analysis computes the target-setting side of PACTA: market-share and sectoral decarbonisation targets that measure a loan book or portfolio against climate scenarios. It sits downstream of the matched company data the sibling packages produce. The 0.5.0 release declared it lifecycle-stable and handed maintenance to a new lead, and releases since have been narrow corrections rather than new methods.

Read the full r2dii.analysis trajectory →

common vs r2dii.analysis: editorial side-by-side

C
common
ANALYTICS
0.0

A base-R utility belt that grows one small function at a time, on no particular schedule

◆ Current state

common collects small helpers that base R leaves out — data frame labelling and sorting, infix operators for pasting and equality, UTF-8 superscript and subscript lookups, file and directory search, attribute copying between data frames. It has no dependencies to speak of and deliberately removed the one it had. In practice it is the shared substrate for its author's wider package family, and its source.all() function is maintained specifically to cooperate with the logr logging package.

◆ Where it's heading

The pattern is accretion rather than direction: each release adds a couple of utilities and fixes whatever the last batch broke, with gaps of a year or more between them. Function additions cluster around whatever the author's other packages needed at the time — file search, attribute preservation, group-boundary detection, script sourcing. The 2025 release continues exactly this, extending the infix comparison operators from equality alone to the full set of relational tests.

◆ Prediction

Expect more of the same shape — a handful of small helpers whenever a sibling package needs them — with no sign in these entries of a broader API push.

R0.0

The climate-alignment maths behind PACTA, now stable and maintained rather than reshaped

◆ Current state

r2dii.analysis computes the target-setting side of PACTA: market-share and sectoral decarbonisation targets that measure a loan book or portfolio against climate scenarios. It sits downstream of the matched company data the sibling packages produce. The 0.5.0 release declared it lifecycle-stable and handed maintenance to a new lead, and releases since have been narrow corrections rather than new methods.

◆ Where it's heading

The history is a package converging. Early releases churn the output contract of target_market_share() and target_sda() — which sectors appear, which years, how missing production is treated — and each change alters the numbers users get. The ald-to-abcd rename runs across several releases before completing, and by 0.5.0 the churn has stopped, with three older summarise functions soft-deprecated and the package marked stable. What remains is edge-case correctness in target coverage.

◆ Prediction

With the package marked stable and the terminology migration finished, the soft-deprecated summarise functions are the obvious next thing to remove outright.

Alternatives to common and r2dii.analysis

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 common or r2dii.analysis.

See all common alternatives → · See all r2dii.analysis alternatives →

Recent activity from common and r2dii.analysis

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

  1. 7mo agor2dii.analysisLow-carbon technology targets filled in for partial company coverage
  2. 8mo agocommonFull set of relational infix operators added
  3. 1y agor2dii.analysisColumn definitions filled into the data dictionary
  4. 1y agor2dii.analysisPackage declared stable, three summarise functions soft-deprecated
  5. 2y agocommonsource.all() fixed to cooperate with logr
  6. 2y agor2dii.analysisald argument removed for good in favour of abcd
  7. 2y agocommonsource.all() added for sourcing a directory of scripts
  8. 2y agor2dii.analysisCompany-level SDA converges on the scenario's final year
  9. 2y agocommonchanged() fixed for single-value input
  10. 2y agocommonchanged() identifies grouping boundaries
  11. 3y agocommonthis.path() dependency removed
  12. 3y agor2dii.analysisRepository moved to the RMI-PACTA organisation

Frequently asked questions

What is the difference between common and r2dii.analysis?

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

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

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

What are the best alternatives to r2dii.analysis?

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