← Back to home
Comparison · Analytics

dvir vs malariasimulation

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

dvir vs malariasimulation: at a glance

Featuredvirmalariasimulation
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesforensic genetics, victim identification, pipeline, scalabilityepidemiology, malaria, simulation, r-packages
Last editorial update15m ago1h ago
WebsiteVisit →Visit →

What is dvir?

dvir keeps making disaster victim identification a single call instead of a workflow.

dvir handles disaster victim identification: matching unidentified remains against reference families using pedigree likelihoods. The package has consolidated around dviSolve(), a complete pipeline introduced in 3.2.1 and rewritten in 3.3.0 to use generalised likelihood ratios for families with several missing persons. Recent releases have been about making that pipeline survive large cases, adding dviGridSize() and a maxAssign cutoff to skip joint analysis when the combination count explodes, plus per-step timings.

Read the full dvir trajectory →

What is malariasimulation?

An individual-based malaria model that grew a second parasite species, then froze itself for reproducibility.

malariasimulation is an individual-based transmission model whose 2.0 line added a full Plasmodium vivax implementation alongside the existing P. falciparum one, including hypnozoites, competing hazards, vivax-specific drug handling, an equilibrium solution and dedicated outputs. The most recent entry is not a code release at all but a coordinated malariaverse_01_2025 tag applied across the package suite, freezing every package at a matching version so existing analyses can be reproduced after the suite moves on. The record here is thin, two entries spanning sixteen months, so the visible cadence understates the work in the underlying repository.

Read the full malariasimulation trajectory →

dvir vs malariasimulation: editorial side-by-side

D
dvir
ANALYTICS
0.0

dvir keeps making disaster victim identification a single call instead of a workflow.

◆ Current state

dvir handles disaster victim identification: matching unidentified remains against reference families using pedigree likelihoods. The package has consolidated around dviSolve(), a complete pipeline introduced in 3.2.1 and rewritten in 3.3.0 to use generalised likelihood ratios for families with several missing persons. Recent releases have been about making that pipeline survive large cases, adding dviGridSize() and a maxAssign cutoff to skip joint analysis when the combination count explodes, plus per-step timings.

◆ Where it's heading

The arc is from a toolbox of functions toward one supervised pipeline, with the older jointDVI() now emitting a legacy message. The current constraint is combinatorial: joint analysis over many victims and missing persons blows up, so the work has gone to measuring the blowup and bailing out of it. Parallelism is mid-migration, with the parallel and pbapply implementation removed and a mirai replacement stated as planned but not yet shipped, leaving numCores accepted and ignored with a warning.

◆ Prediction

The mirai-based parallelisation is announced as coming, so expect it next, most likely applied to the joint analysis step that maxAssign currently exists to avoid.

M0.0

An individual-based malaria model that grew a second parasite species, then froze itself for reproducibility.

◆ Current state

malariasimulation is an individual-based transmission model whose 2.0 line added a full Plasmodium vivax implementation alongside the existing P. falciparum one, including hypnozoites, competing hazards, vivax-specific drug handling, an equilibrium solution and dedicated outputs. The most recent entry is not a code release at all but a coordinated malariaverse_01_2025 tag applied across the package suite, freezing every package at a matching version so existing analyses can be reproduced after the suite moves on. The record here is thin, two entries spanning sixteen months, so the visible cadence understates the work in the underlying repository.

◆ Where it's heading

The direction visible in these entries is toward being a suite rather than a package. The snapshot tag is explicit that packages are installed together at one tag rather than mixed with main, which is the versioning discipline of a research platform whose users publish against specific model versions. On the modelling side, the vivax work was not a parameter addition but a distinct biology, with immunity structures removed rather than reused, indicating the model now carries two species with genuinely different natural histories.

◆ Prediction

The snapshot describes itself as freezing state immediately before an upcoming update, so the next visible release should be that update across the suite rather than any single package. Whether it extends the vivax model or the falciparum one is not indicated here.

Alternatives to dvir and malariasimulation

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 dvir or malariasimulation.

See all dvir alternatives → · See all malariasimulation alternatives →

Recent activity from dvir and malariasimulation

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

  1. 1mo agodvirCombination sizing and a cutoff for joint analysis
  2. 2mo agomalariasimulationCoordinated suite snapshot tag for reproducible installs
  3. 3mo agodvirJoint tables added to solver output
  4. 3mo agodvirVictim and database accessors, plus solver refinements
  5. 1y agomalariasimulationPlasmodium vivax model lands: hypnozoites, competing hazards, equilibrium
  6. 1y agodvirSolver rewritten around generalised likelihood ratios
  7. 2y agodvirdviSolve() pipeline and manual pairing controls
  8. 2y agodvirMaintainer handover and small reporting additions

Frequently asked questions

What is the difference between dvir and malariasimulation?

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

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

What are the best alternatives to dvir?

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

What are the best alternatives to malariasimulation?

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