← Back to home
Comparison · Analytics

mizer vs units

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

mizer vs units: at a glance

Featuremizerunits
SectorAnalyticsAnalytics
Velocity score5.00.0
Sparks · 30d00
Top themessize-spectrum-modelling, marine-ecology, numerical-methods, extension-frameworkmeasurement units, r package, udunits2, breaking parser change
Last editorial update50m ago4h 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 units?

units reaches 1.0 by rewriting its parser and accepting the breakage that comes with it.

units attaches physical units to R vectors on top of the udunits2 library, covering arithmetic, conversion and ggplot2 scales. Version 1.0-0 replaced the unit-expression tokenizer so numbers are consistently treated as prefixes, and expressions like ml/min/1.73m^2 now parse the way physiologists write them. Printing follows NIST conventions, and 1.0-1 is a fix pass over memory handling and parser edge cases.

Read the full units trajectory →

mizer vs units: 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.

U
units
ANALYTICS
0.0

units reaches 1.0 by rewriting its parser and accepting the breakage that comes with it.

◆ Current state

units attaches physical units to R vectors on top of the udunits2 library, covering arithmetic, conversion and ggplot2 scales. Version 1.0-0 replaced the unit-expression tokenizer so numbers are consistently treated as prefixes, and expressions like ml/min/1.73m^2 now parse the way physiologists write them. Printing follows NIST conventions, and 1.0-1 is a fix pass over memory handling and parser edge cases.

◆ Where it's heading

The long 0.8-x run was accretion — ggplot2 scales absorbed from ggforce, ud_convert(), matrix methods, steady performance work — while known parsing defects stayed in place. The 1.0 release finally traded backwards compatibility for correct parsing, and 1.0-1's pointer-wrapping and exception-propagation work suggests the C++ glue is being hardened behind it. Fixes cluster at the udunits2 boundary, which remains the main source of surprises.

◆ Prediction

Expect continued patch releases against udunits2 quirks and the new tokenizer's fallout rather than new surface area, with the ggplot2 integration and conversion helpers already in place.

Alternatives to mizer and units

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 units.

See all mizer alternatives → · See all units alternatives →

Recent activity from mizer and units

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. 5mo agounitsMemory-leak and udunits2 parsing fixes after 1.0
  6. 10mo agounitsNew tokenizer parses compound units correctly
  7. 1y agounitsCopy semantics fix in ud_convert(); C++17 for old R
  8. 1y agounitscbind/rbind methods, ud_convert() and broad fixes
  9. 1y agounitsSilences a CRAN compiler warning
  10. 2y agomizerExternal encounter rate, and a split between given and calculated parameters
  11. 2y agounitsRestores simplify=FALSE for identical units
  12. 3y agomizerw_inf renamed to w_max to separate maximum size from von Bertalanffy asymptotic size

Frequently asked questions

What is the difference between mizer and units?

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 units?

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 units?

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