← Back to home
Comparison · Analytics

KLINK vs parglm

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

KLINK vs parglm: at a glance

FeatureKLINKparglm
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesforensic-genetics, kinship-testing, str-markers, shinyr, glm, parallel computing, c++
Last editorial update2h ago13m ago
WebsiteVisit →Visit →

What is KLINK?

Forensic kinship testing with linked STR markers, now peer-reviewed and taking data from anywhere.

KLINK is a Shiny application and R package for kinship testing that accounts for linkage between STR markers, rather than treating all markers as independent. The built-in genetic map covers 50 common STR markers, pairs them dynamically after data loads, and lets the user set the maximum distance at which a pair counts as linked. Custom marker maps can now arrive as Excel files including KLINK's own download files, and a paper describing the tool was published in FSI:Genetics in 2026.

Read the full KLINK trajectory →

What is parglm?

Under a new maintainer, parglm traded raw speed work for glm parity and memory safety

parglm fits generalized linear models using parallel QR decomposition, targeting datasets where glm() is too slow. Tom Palmer took over maintenance at 0.1.8 in April 2026, and the package has released five times since — a burst of activity after a long quiet period. 0.2.0 in July 2026 is the first release to focus on correctness rather than throughput.

Read the full parglm trajectory →

KLINK vs parglm: editorial side-by-side

K
KLINK
ANALYTICS
2.5

Forensic kinship testing with linked STR markers, now peer-reviewed and taking data from anywhere.

◆ Current state

KLINK is a Shiny application and R package for kinship testing that accounts for linkage between STR markers, rather than treating all markers as independent. The built-in genetic map covers 50 common STR markers, pairs them dynamically after data loads, and lets the user set the maximum distance at which a pair counts as linked. Custom marker maps can now arrive as Excel files including KLINK's own download files, and a paper describing the tool was published in FSI:Genetics in 2026.

◆ Where it's heading

The direction is from fixed panel toward general instrument. Hard-coded linkage pairs gave way to dynamic pairing, the built-in map grew from 18 to 50 markers, the map itself was then moved out to the norSTR package, and the app now accepts custom maps in several file formats and decimal conventions. Method capability tracks the upstream pedsuite rather than KLINK itself: special lumping in pedprobr and pedmut is what allowed complex mutation models in common pedigrees, and the newest release pins pedtools 2.11.0 and pedprobr 1.1.0 for faster likelihoods and better handling of looped pedigrees. Much of the remaining work is unglamorous casework ergonomics, replacing stray Norwegian text in Excel output, controlling table heights, fixing karyogram colours.

◆ Prediction

With the map externalised and custom maps loading from multiple formats, the likeliest next step is broader marker-panel coverage through norSTR rather than changes in KLINK itself. Method gains should continue to arrive as pedprobr and pedmut version bumps.

P
parglm
ANALYTICS
0.0

Under a new maintainer, parglm traded raw speed work for glm parity and memory safety

◆ Current state

parglm fits generalized linear models using parallel QR decomposition, targeting datasets where glm() is too slow. Tom Palmer took over maintenance at 0.1.8 in April 2026, and the package has released five times since — a burst of activity after a long quiet period. 0.2.0 in July 2026 is the first release to focus on correctness rather than throughput.

◆ Where it's heading

The arc runs from performance to trustworthiness. 0.1.9 was a large optimization release — deque-based task queues, fused memory passes, upper-triangle-only Fisher information, thread_local IDs — plus ecosystem integration with sandwich and gtsummary. 0.2.0 then fixed an out-of-bounds write triggered by small block_size values and a path where a non-finite working response could poison the QR decomposition, and brought response-type handling in line with glm().

◆ Prediction

With the memory-safety issues addressed and glm parity closed for binomial responses, further work is likely to extend family coverage or the benchmark suite rather than revisit the threading model. The C++17 requirement set at 0.1.8 gives room for more aggressive optimization if the maintainer returns to that.

Alternatives to KLINK and parglm

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 KLINK or parglm.

See all KLINK alternatives → · See all parglm alternatives →

Recent activity from KLINK and parglm

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

  1. 12d agoKLINKExcel marker maps, more robust map loading, and a published paper
  2. 1mo agoparglmglm-compatible response types plus out-of-bounds and QR safety fixes
  3. 2mo agoparglmBuild fixes for macOS SDK and thread pool includes
  4. 3mo agoparglmAdd missing <thread> include for older Apple SDKs
  5. 3mo agoparglmThreading overhaul, quasi families, and sandwich/gtsummary compatibility
  6. 3mo agoKLINKIn-app help pages, a mutation-model setting, and clearer controls
  7. 3mo agoparglmNew maintainer takes over; C++17 now required
  8. 1y agoKLINKComplex mutation models become usable via upstream special lumping
  9. 1y agoKLINKDownload fix for XML initials containing hyphens
  10. 1y agoKLINKUnlinked report picks the higher-PIC marker from each pair
  11. 2y agoKLINKMarkers pair dynamically against a 50-marker map, replacing hard-coded pairs

Frequently asked questions

What is the difference between KLINK and parglm?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. KLINK 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 Analytics products to evaluate alongside.

What are the best alternatives to KLINK?

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

What are the best alternatives to parglm?

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