← Back to home
Comparison · Analytics

filtro vs units

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

Shared themes:r package

filtro vs units: at a glance

Featurefiltrounits
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesfeature selection, tidymodels, s7, filter methodsmeasurement units, r package, udunits2, breaking parser change
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is filtro?

filtro moves to S7 and multiplies its feature-scoring methods in a single release.

filtro supplies feature-selection filter scores for the tidymodels stack. Version 0.2.0 adds five scoring methods — correlation, random forest importance, information gain, ROC AUC and cross tabulation — and moves the package from S3 to S7. It also gains a ranking layer: show_best_score_* and rank_best_score_* helpers for a single score, plus desirability-function helpers for optimising across several scores at once.

Read the full filtro 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 →

filtro vs units: editorial side-by-side

F
filtro
ANALYTICS
0.0

filtro moves to S7 and multiplies its feature-scoring methods in a single release.

◆ Current state

filtro supplies feature-selection filter scores for the tidymodels stack. Version 0.2.0 adds five scoring methods — correlation, random forest importance, information gain, ROC AUC and cross tabulation — and moves the package from S3 to S7. It also gains a ranking layer: show_best_score_* and rank_best_score_* helpers for a single score, plus desirability-function helpers for optimising across several scores at once.

◆ Where it's heading

The package is being built out on two axes at once — the catalogue of scores, and the machinery for choosing between them. The desirability functions are the more telling half, since they assume users will filter on several criteria rather than one. Adopting S7 while still pre-1.0 suggests the object model is being settled before the API is frozen.

◆ Prediction

Expect more scoring methods on the same S7 interface and a 1.0 release once the score and ranking APIs stop moving; the ranking helpers' naming is the most likely thing to change first.

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

See all filtro alternatives → · See all units alternatives →

Recent activity from filtro and units

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

  1. 5mo agounitsMemory-leak and udunits2 parsing fixes after 1.0
  2. 10mo agounitsNew tokenizer parses compound units correctly
  3. 11mo agofiltroFive new filter scores and the move to S7
  4. 11mo agofiltroDevelopment build: score transformation handling
  5. 1y agounitsCopy semantics fix in ud_convert(); C++17 for old R
  6. 1y agounitscbind/rbind methods, ud_convert() and broad fixes
  7. 1y agounitsSilences a CRAN compiler warning
  8. 2y agounitsRestores simplify=FALSE for identical units

Frequently asked questions

What is the difference between filtro and units?

Both compete on the same themes — r package — within Analytics. filtro and units 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 filtro better than units?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. filtro and units 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 filtro?

Top filtro alternatives in Analytics are ranked by recent ship velocity. Browse the "filtro alternatives" section above for the current picks, or visit /alternatives/filtro-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.