simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
Comparison · Analytics
vim vs vinereg
A side-by-side editorial comparison of vim and vinereg — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
vim vs vinereg: at a glance
What is vim?
Six dormant years end with a correctness audit across VIM's entire imputation surface
VIM handles visualization and imputation of missing values in R, with kNN, hot-deck, iterative robust model-based imputation and matching-based methods. Development effectively stopped after 6.0.0 in 2020. Version 7.2.0 arrives in July 2026 as an explicitly framed correctness milestone: MI-properness warnings, ordered-factor preservation, a keep_all_columns option, list returns from irmi(mi>1), repairs to imputeRobust and imputeRobustChain, cellwise IRWLS and initial-weight fixes, and kNN and gowerD mixed-scaling corrections with a weightDist guard.
What is vinereg?
Conditional density and log-likelihood fill out a vine copula regression package.
vinereg fits D-vine copula-based regression models on top of rvinecopulib and kde1d, in Thomas Nagler's package stack. The January 2025 pair - 0.10.0 and 0.11.0 tagged the same day - adds a pdf() function and then fixes conditional density computation for discrete variables while requiring the newer kde1d. Release notes run to one or two bullets each.
vim vs vinereg: editorial side-by-side
vim
0.0ANALYTICS
Six dormant years end with a correctness audit across VIM's entire imputation surface
◆ Current state
VIM handles visualization and imputation of missing values in R, with kNN, hot-deck, iterative robust model-based imputation and matching-based methods. Development effectively stopped after 6.0.0 in 2020. Version 7.2.0 arrives in July 2026 as an explicitly framed correctness milestone: MI-properness warnings, ordered-factor preservation, a keep_all_columns option, list returns from irmi(mi>1), repairs to imputeRobust and imputeRobustChain, cellwise IRWLS and initial-weight fixes, and kNN and gowerD mixed-scaling corrections with a weightDist guard.
◆ Where it's heading
The release notes describe an audit — Wave 1 plus tail — rather than a feature cycle, and the fixes cluster around statistical validity: whether multiple imputation is proper, whether factor ordering survives, whether distance scaling across mixed variable types is right. Those are the properties users cannot easily verify themselves, so a package correcting them after six years is implicitly restating what its earlier output was worth. The notes also name a forthcoming R Journal paper under the name vimpute, which points at a successor or companion identity.
◆ Prediction
The entries call this a stable reference point for a paper and refer to Wave 1, so a further audit wave is the most likely next release; the vimpute naming is worth watching but the entries do not say what it is.
vinereg
0.0ANALYTICS
Conditional density and log-likelihood fill out a vine copula regression package.
◆ Current state
vinereg fits D-vine copula-based regression models on top of rvinecopulib and kde1d, in Thomas Nagler's package stack. The January 2025 pair - 0.10.0 and 0.11.0 tagged the same day - adds a pdf() function and then fixes conditional density computation for discrete variables while requiring the newer kde1d. Release notes run to one or two bullets each.
◆ Where it's heading
Work has concentrated on evaluation rather than fitting: cll() in 0.9.0, pdf() in 0.10.0, and the discrete-variable correction in 0.11.0 all concern what can be computed from a model already fitted. Releases arrive in same-day pairs, and the notes are terse enough that 0.10.0 reuses 0.9.0's wording verbatim, describing pdf() with cll()'s sentence. Version floors also track the sibling packages - kde1d here, rvinecopulib in 0.8.3.
◆ Prediction
Given the shared release rhythm across the stack, the next entry is as likely to be a dependency-driven bump as a new function; the discrete-variable path is the one area these notes show as recently unstable.
Alternatives to vim and vinereg
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 vim or vinereg.
lavaanExtra
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
ibis.iSDM
A raster-to-terra migration is the only readable change in a feed of merge notes.
anyflights
A nycflights13 generator whose recent work is all about the data being right.
stringx
A drop-in string API for base R, kept alive by upstream check failures.
healthyR.data
From a bundled hospital dataset to a live CMS API client.
Recent activity from vim and vinereg
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agovimCorrectness audit fixes MI-properness, factor order and distance scaling
- 1y agovineregDiscrete conditional densities fixed; kde1d 1.1.0 required
- 1y agovineregpdf() added for conditional density
- 2y agovineregBoost compile flag and a weights error fixed
- 2y agovineregcll() computes conditional log-likelihood
- 4y agovineregvinecopulib floor raised for RcppThread compatibility
- 4y agovineregcpit() fixed and external marginals allowed via uscale
- 6y agovimAdds ranger-based imputation, drops survey and GUI support
- 6y agovimAdds nine example datasets and splits help pages
- 6y agovimAdds matchImpute() and random-forest augmented kNN
- 6y agovimOrdered factor support and ordinal regression in irmi()
- 6y agovimBug fixes for kNN, hotdeck and irmi input handling
Frequently asked questions
What is the difference between vim and vinereg?
Both compete on the same themes — r-package — within Analytics. vim and vinereg 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 vim better than vinereg?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vim and vinereg 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 vim?
Top vim alternatives in Analytics are ranked by recent ship velocity. Browse the "vim alternatives" section above for the current picks, or visit /alternatives/vim for the full list with editorial commentary on each.
What are the best alternatives to vinereg?
Top vinereg alternatives in Analytics are ranked by recent ship velocity. Browse the "vinereg alternatives" section above for the current picks, or visit /alternatives/vinereg for the full list with editorial commentary on each.