← Back to home
Comparison · Infra & APIs

cvms vs HydroPortailStats

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

Shared themes:r-package

cvms vs HydroPortailStats: at a glance

FeaturecvmsHydroPortailStats
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themescross-validation, r-package, model-evaluation, visualizationhydrology, flood-frequency, bayesian-statistics, extreme-values
Last editorial update1h ago52m ago
WebsiteVisit →Visit →

What is cvms?

A cross-validation package whose real development has moved to its plotting function

cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.

Read the full cvms trajectory →

What is HydroPortailStats?

France's national flood statistics, ported out of Fortran and into R.

HydroPortailStats exposes the statistical machinery behind the French HydroPortail — distribution fitting, quantile curves and their uncertainties for hydrological series. The 2025 release re-implements the HBay Fortran executable in R, adding Bayesian estimation from historical flood records with censored and interval-valued data and systematic measurement error, plus a triangular distribution and truncated random generation.

Read the full HydroPortailStats trajectory →

cvms vs HydroPortailStats: editorial side-by-side

C
cvms
INFRA · APIS
0.0

A cross-validation package whose real development has moved to its plotting function

◆ Current state

cvms runs repeated cross-validation over model formulas and reports comparable metrics. The 2.0.0 release was a breaking correctness fix: every function accepting fold_cols mismatched training and testing data when fold indices were non-sequential, did not start at 1, or were strings, because the iteration index was compared against the raw fold value rather than its factor level index. 2.0.1 restored coefficient extraction for nnet::multinom and mixed models by supplying an environment containing the training data, and followed lme4's move of findbars() into the reformulas package.

◆ Where it's heading

Two threads run in parallel and only one is about cross-validation. The plotting function plot_confusion_matrix() has absorbed most feature work since 1.5.0 - custom gradient palettes, intensity limits, per-tile settings, dynamic font colors keyed to value thresholds, and arguments that accept functions rather than constants - to the point where a companion web application exists for using it without code. The cross-validation core, by contrast, sees maintenance: upstream compatibility fixes for pROC, ggnewscale and ggplot2, and the fold-matching correction that finally forced a major version.

◆ Prediction

Expect continued option growth in the confusion matrix plotting surface, since that is where nearly every release since 1.5.0 has spent its changes, with core cross-validation changes arriving only as upstream packages force them.

H
HydroPortailStats
INFRA · APIS
0.0

France's national flood statistics, ported out of Fortran and into R.

◆ Current state

HydroPortailStats exposes the statistical machinery behind the French HydroPortail — distribution fitting, quantile curves and their uncertainties for hydrological series. The 2025 release re-implements the HBay Fortran executable in R, adding Bayesian estimation from historical flood records with censored and interval-valued data and systematic measurement error, plus a triangular distribution and truncated random generation.

◆ Where it's heading

The package started as a straight extraction of the portal's existing functions and is now absorbing the surrounding legacy toolchain: HBay was a separate compiled program with its own config files, and this release brings both the method and its configuration format inside R. Releases are sparse — three in two years, with an eighteen-month gap before the latest — and the intervening one was CRAN paperwork.

◆ Prediction

The HBay import came with a configuration-file reader for continuity with the old executable, which suggests further legacy hydrological tooling could follow the same path; the entries name no specific next target.

Alternatives to cvms and HydroPortailStats

Other Infra & APIs 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 cvms or HydroPortailStats.

See all cvms alternatives → · See all HydroPortailStats alternatives →

Recent activity from cvms and HydroPortailStats

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

  1. 2mo agocvmsCoefficient extraction restored for multinom and mixed models
  2. 9mo agocvmsBreaking fix for mismatched folds with non-sequential fold IDs
  3. 11mo agocvmsTest compatibility with pROC 1.19 and a deprecation warning fix
  4. 1y agocvmsConfusion matrix fonts and colors can now be computed from the values
  5. 1y agocvmsTile intensity by row or column percentages
  6. 1y agocvmsMultinom coefficient extraction fix after a parameters update
  7. 1y agoHydroPortailStatsHistorical flood records enter the estimator via an HBay port
  8. 3y agoHydroPortailStatsCRAN submission renames the return-period arguments
  9. 3y agoHydroPortailStatsFirst release: the HydroPortail statistical functions in R

Frequently asked questions

What is the difference between cvms and HydroPortailStats?

Both compete on the same themes — r-package — within Infra & APIs. cvms and HydroPortailStats 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 cvms better than HydroPortailStats?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cvms and HydroPortailStats 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to cvms?

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

What are the best alternatives to HydroPortailStats?

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