← Back to home
Comparison · Analytics

mizer vs treespace

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

mizer vs treespace: at a glance

Featuremizertreespace
SectorAnalyticsAnalytics
Velocity score5.00.0
Sparks · 30d00
Top themessize-spectrum-modelling, marine-ecology, numerical-methods, extension-frameworkphylogenetics, transmission-trees, cran-compliance, maintenance-mode
Last editorial update4h ago46m ago
WebsiteVisit →Visit →

What is mizer?

After two and a half years dormant, mizer shipped three major versions in seven weeks.

The size-spectrum fish modelling package sat at 2.5.0 from December 2023 until June 2026, then released 3.0.0, 3.1.0 and 3.2.0 in the space of seven weeks. The three releases divide cleanly: 3.0.0 added biological realism through a diffusion term in the McKendrick-von Foerster equation, 3.1.0 added an opt-in second-order numerical scheme in size, and 3.2.0 rebuilt how species and resource parameters are set. Backward compatibility is handled carefully throughout — the experimental scheme is off by default and the first-order path is byte-identical to previous versions.

Read the full mizer trajectory →

What is treespace?

treespace ships once every year or two, and only when CRAN or a user forces it.

treespace explores and compares sets of phylogenetic and transmission trees, including the tree-distance measures used in outbreak reconstruction. Its release history is entirely reactive: five updates across five years, each triggered by a CRAN policy change, an upstream package removal, or a bug someone reported. The most recent is an Rd cross-reference format patch plus a maintainer email change.

Read the full treespace trajectory →

mizer vs treespace: editorial side-by-side

M
mizer
ANALYTICS
5.0

After two and a half years dormant, mizer shipped three major versions in seven weeks.

◆ Current state

The size-spectrum fish modelling package sat at 2.5.0 from December 2023 until June 2026, then released 3.0.0, 3.1.0 and 3.2.0 in the space of seven weeks. The three releases divide cleanly: 3.0.0 added biological realism through a diffusion term in the McKendrick-von Foerster equation, 3.1.0 added an opt-in second-order numerical scheme in size, and 3.2.0 rebuilt how species and resource parameters are set. Backward compatibility is handled carefully throughout — the experimental scheme is off by default and the first-order path is byte-identical to previous versions.

◆ Where it's heading

Two threads run through the 3.x line. The first is numerical: diffusion, then higher-order accuracy in both size and time, with explicit warnings that enabling them shifts diagnostics and may require recalibration. The second is making the package composable — extensions now work regardless of load order, and parameter assignment propagates to the derived rate arrays instead of being silently discarded. That second thread reads as the more consequential one: the 3.2.0 notes describe scalar edits that previously vanished and now accumulate, which is the kind of fix that changes what published model configurations actually computed.

◆ Prediction

Expect the experimental second-order scheme to move toward default-on once recalibration guidance exists, and the patch line to keep absorbing the documentation and website gaps that 3.2.1 started on.

T
treespace
ANALYTICS
0.0

treespace ships once every year or two, and only when CRAN or a user forces it.

◆ Current state

treespace explores and compares sets of phylogenetic and transmission trees, including the tree-distance measures used in outbreak reconstruction. Its release history is entirely reactive: five updates across five years, each triggered by a CRAN policy change, an upstream package removal, or a bug someone reported. The most recent is an Rd cross-reference format patch plus a maintainer email change.

◆ Where it's heading

The package is stable and lightly staffed rather than abandoned — bugs that affect correctness do get fixed, and CRAN deadlines are met. But the 2023 update is the telling one: rather than vendor or replace adephylo when it faced removal, the maintainers disabled two tree-vector methods and marked the loss as hopefully temporary. Two years on, nothing in the feed indicates they came back.

◆ Prediction

The next entry will most likely be another CRAN-compliance patch, on the pattern of four of the last five releases. Whether the Abouheif and sumDD methods ever return is not something these entries give any signal on.

Alternatives to mizer and treespace

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 mizer or treespace.

See all mizer alternatives → · See all treespace alternatives →

Recent activity from mizer and treespace

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

  1. 15d agomizerpkgdown index fix for a man page added after the 3.2.0 build
  2. 25d agomizerParameter assignment rebuilds derived rates; extensions compose in any load order
  3. 1mo agomizerOpt-in second-order accurate scheme in the size variable
  4. 2mo agomizerDiffusion enters the McKendrick-von Foerster equation, ending a two-year gap
  5. 11mo agotreespacetreespace patches Rd cross-references for CRAN
  6. 2y agomizerExternal encounter rate, and a split between given and calculated parameters
  7. 2y agotreespacetreespace disables Abouheif and sumDD as adephylo exits CRAN
  8. 3y agotreespacetreespace fixes vignette build on NA tree names
  9. 3y agomizerw_inf renamed to w_max to separate maximum size from von Bertalanffy asymptotic size
  10. 5y agotreespacetreespace fixes dist indexing that broke its tests
  11. 5y agotreespacetreespace corrects tip label handling in transmission distances

Frequently asked questions

What is the difference between mizer and treespace?

They serve adjacent needs but don't currently overlap on shipped themes. mizer is currently shipping more aggressively (velocity 5.0 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 mizer better than treespace?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mizer is currently shipping more aggressively (velocity 5.0 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 mizer?

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

What are the best alternatives to treespace?

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