← Back to home
Comparison · Infra & APIs

JointFPM vs valr

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

JointFPM vs valr: at a glance

FeatureJointFPMvalr
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, recurrent-events, parametric-models, api-stabilitygenomics, interval-arithmetic, bioinformatics, bigwig
Last editorial update50m ago3h ago
WebsiteVisit →Visit →

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 →

What is valr?

valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.

valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.

Read the full valr trajectory →

JointFPM vs valr: editorial side-by-side

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.

V
valr
INFRA · APIS
0.0

valr's interval verbs now read genomic files in place instead of demanding a loaded tibble.

◆ Current state

valr reimplements bedtools-style genome interval arithmetic as tidyverse verbs backed by C++. Its long project has been closing the behavioural gap with bedtools — the book-ended interval semantics finally match in 0.10.0, three releases after the deprecation began. The July release also ends the assumption that intervals must be in memory: bed_map(), bed_intersect(), bed_subtract(), bed_coverage() and bed_window() accept a bigWig or bigBed path or URL where an interval table used to go.

◆ Where it's heading

Two arcs converge here. One is compatibility: min_overlap arrived with a deprecation warning in 0.9.0 and its default flipped from 0 to 1 in 0.10.0, so book-ended intervals are excluded by default as bedtools does, with the internal calculations in bed_closest() and friends deliberately left counting them. The other is the file-backed path, which grew out of the cpp11bigwig dependency adopted in 0.8.3 for read_bigwig() and re-exported in 0.9.0 — reading a file became querying one. Underneath, the C++ base keeps getting lighter: Rcpp swapped for cpp11, rlang cut to a single function, per-group memory copies removed from three verbs.

◆ Prediction

Only five verbs take a file argument today and bed_closest(), bed_glyph() and the statistical verbs do not, so extending the file-backed path across the rest of the API is the obvious follow-up. The deprecated tibble re-exports and the now-defunct n_fields argument suggest continued removal of the compatibility layer in the next minor release.

Alternatives to JointFPM and valr

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

See all JointFPM alternatives → · See all valr alternatives →

Recent activity from JointFPM and valr

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

  1. 1mo agovalrInterval verbs read bigWig and bigBed files directly
  2. 7mo agovalrbed_slop() and bed_flank() preserve input row order
  3. 8mo agovalrmin_overlap introduced; C++ backend moves from Rcpp to cpp11
  4. 1y agoJointFPMmean_no() promoted to a stable interface
  5. 1y agovalrTest updated for ggplot2 3.6.0
  6. 1y agovalrread_bigwig() switches to cpp11bigwig; read_gtf() deprecated
  7. 1y agovalrCRAN Rd link NOTE and maintainer email change
  8. 2y agoJointFPMsummary() method and control arguments passed to rstpm2
  9. 2y agoJointFPMGaussian quadrature option for the mean-events integration
  10. 2y agoJointFPMStandardized marginal estimates plus input validation
  11. 2y agoJointFPMBug fixes for differences between mean-event functions

Frequently asked questions

What is the difference between JointFPM and valr?

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

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

What are the best alternatives to valr?

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