← Back to home
Comparison · Analytics

constants vs modeltime.resample

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

constants vs modeltime.resample: at a glance

Featureconstantsmodeltime.resample
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesphysical-constants, codata, units, uncertainty-propagationtime series, cross-validation, tidymodels, compatibility maintenance
Last editorial update1h ago11h ago
WebsiteVisit →Visit →

What is constants?

The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.

constants exposes the CODATA recommended values of the physical constants to R, as a data frame plus symbol lists that carry units, uncertainties, or both. The package reached 1.0.0 on the 2018 CODATA release and has shipped once since, purely to track a units package update. Its surface is small and its release cadence is bound to CODATA, which revises every few years.

Read the full constants trajectory →

What is modeltime.resample?

modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.

modeltime.resample runs time series cross-validation over modeltime models, returning per-resample predictions and accuracy plots. Version 0.3.0 is the substantive release in view: tune 2.0.0 compatibility, deterministic seeding via withr, guaranteed .predictions output, and clearer failures when resample fits break. The three releases before it are dependency chores.

Read the full modeltime.resample trajectory →

constants vs modeltime.resample: editorial side-by-side

C
constants
ANALYTICS
0.0

The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.

◆ Current state

constants exposes the CODATA recommended values of the physical constants to R, as a data frame plus symbol lists that carry units, uncertainties, or both. The package reached 1.0.0 on the 2018 CODATA release and has shipped once since, purely to track a units package update. Its surface is small and its release cadence is bound to CODATA, which revises every few years.

◆ Where it's heading

The direction set at 1.0.0 was to stop being a curated convenience wrapper and become a mechanical mirror of NIST. Hand-crafted symbol names were replaced with NIST's own ASCII symbols, categories adopted NIST's, and uncertainty switched from relative to absolute — all framed by the maintainer as necessary to make future CODATA updates routine. On top of that the package gained a correlation matrix and optional integration with the quantities package, moving it from a lookup table toward something that can propagate uncertainty.

◆ Prediction

Having rebuilt the symbol table specifically so CODATA revisions become mechanical, the next substantive release most likely tracks a new CODATA dataset rather than adding API. The experimental correlated-value support, disabled by default at 1.0.0, is the one part these entries flag as unfinished.

M0.0

modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.

◆ Current state

modeltime.resample runs time series cross-validation over modeltime models, returning per-resample predictions and accuracy plots. Version 0.3.0 is the substantive release in view: tune 2.0.0 compatibility, deterministic seeding via withr, guaranteed .predictions output, and clearer failures when resample fits break. The three releases before it are dependency chores.

◆ Where it's heading

Every entry here is compatibility work against something upstream — hardhat 1.0.0, workflows regression mode, then tune 2.0.0 twice. The 0.3.0 notes show a second concern emerging alongside it: making failures legible, with .notes on failed fits, actionable errors from unnest_modeltime_resamples(), and fallback logic when prediction columns go missing across versions. Reproducibility gets the same treatment through explicit seeding.

◆ Prediction

Expect the next release to track the next tidymodels breaking change, with any new work continuing on error reporting rather than resampling strategies.

Alternatives to constants and modeltime.resample

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 constants or modeltime.resample.

See all constants alternatives → · See all modeltime.resample alternatives →

Recent activity from constants and modeltime.resample

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

  1. 11mo agomodeltime.resampletune 2.0 support, deterministic seeding, clearer errors
  2. 11mo agomodeltime.resampleDependency cleanup ahead of the next tune release
  3. 3y agomodeltime.resampleFixes workflows in regression mode
  4. 4y agomodeltime.resampleUpdates for hardhat 1.0.0
  5. 5y agoconstantsCompatibility fix for units 0.7-0
  6. 5y agoconstantsconstants 1.0.0
  7. 8y agoconstantsUnit handling fixes ahead of the 1.0.0 rebuild

Frequently asked questions

What is the difference between constants and modeltime.resample?

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

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

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

What are the best alternatives to modeltime.resample?

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