← Back to home
Comparison · Analytics

pedbuildr vs vellumwidget

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

pedbuildr vs vellumwidget: at a glance

Featurepedbuildrvellumwidget
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d01
Top themespedigree reconstruction, forensic genetics, parallel computing, performancer-graphics, interactive-widgets, declarative-interaction, shiny
Last editorial update17m ago1h ago
WebsiteVisit →Visit →

What is pedbuildr?

pedbuildr reconstructs pedigrees from DNA, and it just got much faster at the search.

pedbuildr infers pedigree structure from marker data by scoring candidate pedigrees against likelihoods. Version 0.4.0 moved reconstruct() to mirai for parallel likelihood computation, deprecated the old numCores argument, and picked up the improved loop breaking from pedtools and pedprobr, which lets many complex looped pedigrees succeed where they previously failed. buildPeds() also got significantly faster in its default configuration where mating between lineally related individuals is disallowed.

Read the full pedbuildr trajectory →

What is vellumwidget?

vellumwidget is dissolving its own API: interaction now lives in the plot spec, not the widget call.

vellumwidget compiles a vellum scene or a vellumplot plot into a self-contained client-side htmlwidget with hover, select, brush, lasso, pan/zoom and export, and no server round-trip. The two-way Shiny story is complete: interactions surface as reactive inputs keyed by output id, and vellumwidget_proxy() drives an already-rendered widget from the server without re-rendering it. The last two releases are fidelity work rather than new surface, calibrating hit-testing from the rendered positions of marks and rendering the raster base image at 2x for HiDPI screens.

Read the full vellumwidget trajectory →

pedbuildr vs vellumwidget: editorial side-by-side

P
pedbuildr
ANALYTICS
0.0

pedbuildr reconstructs pedigrees from DNA, and it just got much faster at the search.

◆ Current state

pedbuildr infers pedigree structure from marker data by scoring candidate pedigrees against likelihoods. Version 0.4.0 moved reconstruct() to mirai for parallel likelihood computation, deprecated the old numCores argument, and picked up the improved loop breaking from pedtools and pedprobr, which lets many complex looped pedigrees succeed where they previously failed. buildPeds() also got significantly faster in its default configuration where mating between lineally related individuals is disallowed.

◆ Where it's heading

The package is bounded by two costs: how many candidate pedigrees it enumerates and how expensive each likelihood is. The recent release attacks both, parallelizing the likelihoods and speeding up enumeration in the common case. The earlier 0.3.0 release worked on the other end, adding inbreeding limits and a proper result class so the output of a large search is manageable. Releases are infrequent, roughly three years apart in this window.

◆ Prediction

Expect the candidate generation side to receive the same attention the likelihood side just did, since search space size is the remaining bound on what pedbuildr can reconstruct.

V
vellumwidget
ANALYTICS
6.3

vellumwidget is dissolving its own API: interaction now lives in the plot spec, not the widget call.

◆ Current state

vellumwidget compiles a vellum scene or a vellumplot plot into a self-contained client-side htmlwidget with hover, select, brush, lasso, pan/zoom and export, and no server round-trip. The two-way Shiny story is complete: interactions surface as reactive inputs keyed by output id, and vellumwidget_proxy() drives an already-rendered widget from the server without re-rendering it. The last two releases are fidelity work rather than new surface, calibrating hit-testing from the rendered positions of marks and rendering the raster base image at 2x for HiDPI screens.

◆ Where it's heading

The direction is declarative. 0.7.0 removed the interaction-intent arguments from as_widget() outright, dropping the signature from roughly 36 arguments to 24 and moving highlight, filter and cross-filter into vellumplot's spec via select_point(), condition() and filter_by(). Each release since has enacted more of that compiled spec on the frozen scene, from conditional encodings to single-view filters to cross-view cross-filtering, leaving the widget as an interpreter of the plot rather than a configuration surface of its own. The bug fixes track the same theme the engine's do: measured geometry and rendered geometry must not drift.

◆ Prediction

The notes name the remaining hold-outs explicitly, saying hover_mode, crosshair, legend_click, select_mode and the tooltip-appearance arguments remain only until their spec equivalents land, so the next releases most likely move those into vellumplot and shrink as_widget() further. The scale binds flagged as following the filter work are the other stated next step.

Alternatives to pedbuildr and vellumwidget

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 pedbuildr or vellumwidget.

See all pedbuildr alternatives → · See all vellumwidget alternatives →

Recent activity from pedbuildr and vellumwidget

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

  1. 14d agovellumwidget2x raster base image for HiDPI, and exact element hit-testing
  2. 20d agovellumwidgetInteraction moves into the plot spec; as_widget() sheds a third of its arguments
  3. 27d agovellumwidgetAxis-aware zoom re-ticks the axes instead of scaling the whole scene
  4. 1mo agovellumwidgetSelectable native SVG text, and crisp canvas redraw when zooming raster
  5. 1mo agovellumwidgetServer-side proxy drives a rendered widget without re-rendering it
  6. 1mo agovellumwidgetShiny input read-back, and keyboard plus screen-reader access by default
  7. 1mo agopedbuildrmirai parallelism and faster pedigree enumeration
  8. 2y agopedbuildrpedCollection class and an inbreeding ceiling

Frequently asked questions

What is the difference between pedbuildr and vellumwidget?

They serve adjacent needs but don't currently overlap on shipped themes. vellumwidget is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 pedbuildr better than vellumwidget?

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

What are the best alternatives to pedbuildr?

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

What are the best alternatives to vellumwidget?

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