← Back to home
Comparison · Infra & APIs

inlabru vs standardlastprofile

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

inlabru vs standardlastprofile: at a glance

Featureinlabrustandardlastprofile
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesbayesian-modelling, spatial-statistics, r-package, api-consolidationenergy, load-profiles, bdew, gas
Last editorial update3h ago1h ago
WebsiteVisit →Visit →

What is inlabru?

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

Read the full inlabru trajectory →

What is standardlastprofile?

A German electricity load-profile package added gas and doubled the market it serves.

standardlastprofile implements the BDEW standard load profiles that German utilities use to assign consumption to customers without interval metering. Until June it did electricity only. Version 2.0.0 added the gas side — the SigLinDe synthetic procedure across all 15 BDEW gas profile IDs — and gave electricity a new primary interface, slp_electricity(), with slp_generate() superseded but retained.

Read the full standardlastprofile trajectory →

inlabru vs standardlastprofile: editorial side-by-side

I
inlabru
INFRA · APIS
2.5

A Bayesian spatial modelling package rebuilding its foundations one breaking release at a time

◆ Current state

inlabru wraps INLA for spatial, point-process and latent-Gaussian models in R. It is mid-modernisation: since 2.12.0 cut the sp stack, each release has renamed part of the public surface, standardised how external packages attach custom mappers, or replaced internal machinery. 2.15.0 is the latest step, pairing a new predictor evaluation and linearisation implementation with broom's tidy(), glance() and augment() methods and four non-zero-truncated observation families.

◆ Where it's heading

The arc is consolidation of the extension surface rather than expansion of the model catalogue. Every release adds mappers or families with one hand and removes a dependency, a re-export or a deprecated path with the other — plyr in 2.15.0, fmesher's Depends entry in 2.14.1, sp and ggmap in 2.12.0. The compatibility flag bru_compat_pre_2_14_enable and the temporary fm_int/fm_pixels re-exports show a maintainer sequencing breaks across releases instead of landing them together.

◆ Prediction

The 2.14 compatibility flag is still defaulting to TRUE and the fmesher re-exports are described in the entries as temporary, so the next obvious move is a release that flips bru_compat_pre_2_14_enable off and drops those re-exports.

S
standardlastprofile
INFRA · APIS
0.0

A German electricity load-profile package added gas and doubled the market it serves.

◆ Current state

standardlastprofile implements the BDEW standard load profiles that German utilities use to assign consumption to customers without interval metering. Until June it did electricity only. Version 2.0.0 added the gas side — the SigLinDe synthetic procedure across all 15 BDEW gas profile IDs — and gave electricity a new primary interface, slp_electricity(), with slp_generate() superseded but retained.

◆ Where it's heading

The package is converting from a dataset wrapper into a calculation library. Electricity profiles are tabulated values the package ships; gas profiles are computed from daily temperatures and a customer value through a coefficient-driven function, and the maintainer exposed the whole ladder — slp_gas() for the profile, slp_gas_kundenwert() to derive the customer value from a reference year, slp_gas_siglinde() for the raw h(theta) demand function so users can supply state-level coefficients, and coefficient and weekday-factor accessors underneath. The same instinct removed the built-in holiday table in favour of computing Easter directly, which lifted the date range cap from 2073 to open-ended. Deprecations are handled carefully throughout: renames keep working with lifecycle warnings, and the one hard break was already a warning since 1.1.0.

◆ Prediction

slp_gas_siglinde() was exported specifically so users could plug in region-specific coefficients such as Baden-Wurttemberg's, which points at state-level coefficient sets as the next thing to ship rather than leave to callers. The BDEW reference edition is now pinned to an Internet Archive permalink after the last one 404'd, so tracking edition changes is an ongoing maintenance cost.

Alternatives to inlabru and standardlastprofile

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 inlabru or standardlastprofile.

See all inlabru alternatives → · See all standardlastprofile alternatives →

Recent activity from inlabru and standardlastprofile

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

  1. 23d agoinlabruPredictor linearisation rewritten; broom tidiers, truncated families
  2. 1mo agostandardlastprofileValidation against the SigLinDe pole; numeric variant accepted
  3. 2mo agostandardlastprofileGas standard load profiles arrive alongside electricity
  4. 3mo agoinlabruBugfix release: factor contrasts, raster extraction, error classes
  5. 5mo agoinlabruNew mappers, standardised cgeneric support, bru_obs storage refactor
  6. 5mo agostandardlastprofileFive 2025 BDEW profiles added, including PV and storage variants
  7. 1y agoinlabruMapper classes shortened to bm_*, experimental predictor aggregation
  8. 1y agoinlabruDrops sp and ggmap for an sf-native spatial stack

Frequently asked questions

What is the difference between inlabru and standardlastprofile?

They serve adjacent needs but don't currently overlap on shipped themes. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is inlabru better than standardlastprofile?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inlabru is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to inlabru?

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

What are the best alternatives to standardlastprofile?

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