← Back to home
Comparison · Infra & APIs

PINstimation vs valr

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

PINstimation vs valr: at a glance

FeaturePINstimationvalr
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesmarket-microstructure, finance, informed-trading, r-packagegenomics, interval-arithmetic, bioinformatics, bigwig
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is PINstimation?

A market-microstructure toolkit that keeps adding estimators as the papers land.

PINstimation estimates probability-of-informed-trading models — PIN, multilayer PIN, adjusted PIN and VPIN — from trade and quote data, and handles the trade classification and aggregation that feeds them. The current 0.2.0 adds ivpin(), a maximum-likelihood variant of VPIN from Ke and Lin (2017). The package's early history is compressed into a single hour of backfilled tags in October 2022, so version order there does not track release order.

Read the full PINstimation 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 →

PINstimation vs valr: editorial side-by-side

P
PINstimation
INFRA · APIS
0.0

A market-microstructure toolkit that keeps adding estimators as the papers land.

◆ Current state

PINstimation estimates probability-of-informed-trading models — PIN, multilayer PIN, adjusted PIN and VPIN — from trade and quote data, and handles the trade classification and aggregation that feeds them. The current 0.2.0 adds ivpin(), a maximum-likelihood variant of VPIN from Ke and Lin (2017). The package's early history is compressed into a single hour of backfilled tags in October 2022, so version order there does not track release order.

◆ Where it's heading

Each release tracks the literature: a Bayesian PIN estimator from Griffin et al., an improved VPIN from Ke and Lin, initial-parameter generation realigned to Ersan and Ghachem. The other steady thread is data handling — matrix inputs so the estimators compose with rolling windows, user-specified aggregation frequencies, and now quote leads as well as lags. The three-year gap between 0.1.2 and 0.2.0 makes this a slow, publication-paced package rather than an actively developed one.

◆ Prediction

On this pattern the next release adds whatever estimator the authors publish next, since two of the three feature releases here implement a specific paper. Nothing in the entries points to a change in the package's structure.

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

See all PINstimation alternatives → · See all valr alternatives →

Recent activity from PINstimation 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 agoPINstimationPINstimation 0.2.0
  4. 8mo agovalrmin_overlap introduced; C++ backend moves from Rcpp to cpp11
  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. 3y agoPINstimationPINstimation v0.1.2
  9. 3y agoPINstimationPINstimation v0.1.1
  10. 3y agoPINstimationPINstimation v0.0.1-beta
  11. 3y agoPINstimationPINstimation v0.1.0

Frequently asked questions

What is the difference between PINstimation and valr?

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

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

Top PINstimation alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PINstimation alternatives" section above for the current picks, or visit /alternatives/pinstimation 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.