← Back to home
Comparison · Infra & APIs

BIOMASS vs JointFPM

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

BIOMASS vs JointFPM: at a glance

FeatureBIOMASSJointFPM
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesforest-ecology, biomass-estimation, geospatial, taxonomysurvival-analysis, recurrent-events, parametric-models, api-stability
Last editorial update22h ago57m ago
WebsiteVisit →Visit →

What is BIOMASS?

A tropical-forest biomass staple modernising its geospatial stack without saying so

BIOMASS estimates aboveground biomass and its uncertainty in tropical forests and is well established in that niche. Its public changelog is close to empty: the most recent entry, 2.2.4, is a thirty-four character pointer to the NEWS file. The last release with readable content, 2.1.11, bundled six versions of work whose substantive part was migrating off sp and raster to sf and terra, and from httr to httr2.

Read the full BIOMASS trajectory →

What is JointFPM?

Recurrent-event modelling settles, with mean_no() promoted to stable.

JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.

Read the full JointFPM trajectory →

BIOMASS vs JointFPM: editorial side-by-side

B
BIOMASS
INFRA · APIS
0.0

A tropical-forest biomass staple modernising its geospatial stack without saying so

◆ Current state

BIOMASS estimates aboveground biomass and its uncertainty in tropical forests and is well established in that niche. Its public changelog is close to empty: the most recent entry, 2.2.4, is a thirty-four character pointer to the NEWS file. The last release with readable content, 2.1.11, bundled six versions of work whose substantive part was migrating off sp and raster to sf and terra, and from httr to httr2.

◆ Where it's heading

The visible arc is dependency modernisation and CRAN compliance rather than science: retiring sp and raster ahead of their deprecation, failing gracefully when taxonomic services are unreachable, and repeatedly changing taxonomic backend as those services disappeared — taxosaurus to TNRS, then away from Tropicos once it was no longer maintained. The recurring fragility is correctTaxo(), which depends on third-party name resolution outside the maintainers' control.

◆ Prediction

Expect the next release to be another compliance or dependency response; on this feed's record the release notes will not say what changed, leaving the NEWS file as the only reliable source.

J
JointFPM
INFRA · APIS
0.0

Recurrent-event modelling settles, with mean_no() promoted to stable.

◆ Current state

JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.

◆ Where it's heading

The arc runs from a working estimator toward a usable one: input validation and error messages first, then control over the numerical integration, then a summary method and pass-through arguments to the underlying rstpm2 fit. The latest release adds no code so much as a stability commitment to a function users were already calling.

◆ Prediction

With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit itself.

Alternatives to BIOMASS and JointFPM

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 BIOMASS or JointFPM.

See all BIOMASS alternatives → · See all JointFPM alternatives →

Recent activity from BIOMASS and JointFPM

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

  1. 11mo agoBIOMASSVersion 2.2.4 released on CRAN
  2. 1y agoJointFPMmean_no() promoted to a stable interface
  3. 1y agoBIOMASSMigration from sp/raster to sf/terra and httr to httr2
  4. 2y agoJointFPMsummary() method and control arguments passed to rstpm2
  5. 2y agoJointFPMGaussian quadrature option for the mean-events integration
  6. 2y agoJointFPMStandardized marginal estimates plus input validation
  7. 2y agoJointFPMBug fixes for differences between mean-event functions
  8. 5y agoBIOMASSTNRS replaces taxosaurus for name resolution

Frequently asked questions

What is the difference between BIOMASS and JointFPM?

They serve adjacent needs but don't currently overlap on shipped themes. BIOMASS and JointFPM 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 BIOMASS better than JointFPM?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BIOMASS and JointFPM 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to BIOMASS?

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

What are the best alternatives to JointFPM?

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