vbpm 0.9.1

Test-portability release. No executable estimator or API behaviour changed, and no number a fit returns changed; 0.9.0 was rejected at CRAN’s incoming checks and never reached the archive.

vbpm 0.9.0

First public release. It was submitted to CRAN but not accepted, so it never reached the archive; see 0.9.1. pefa() is now a measurement-only factor-count sweep: it fits every K in a fixed consecutive window, reports candidate and between-candidate quantities, and chooses nothing. This completes an arc running through 0.8.0 (removed the stable verdict), 0.8.1 (removed absolute-fit gating), and 0.8.2 (removed automated raw/BIC selection). 0.8.3 was withdrawn and never reached CRAN.

Every structural number in a pefa() object changes, because the column-correspondence rule changed. Congruence, pooled and maximum RMSD, ARI, PIP RMSD, unmatched-column size, and the collision flag are not comparable across 0.8.x and 0.9.0, and neither is any threshold calibrated on them.

Breaking removals

The following existed in 0.8.3 and are gone. Removing them is intentional pre-1.0 breakage, not a deprecation cycle.

The correspondence rule

The returned object

Convergence and warnings

Exports and methods

Other

vbpm 0.8.3

This release makes the compact PEFA object easier to inspect and removes two uninformative PIP summaries. It is a breaking refinement of the 0.8.2 schema; the 0.8.2 release history below is unchanged.

vbpm 0.8.2

This release deliberately simplifies PEFA before 1.0 and changes both its object schema and its adjacent-solution diagnostics.

vbpm 0.8.1

pefa() is reduced to a compact, in-memory factor-number sweep. This is a breaking cleanup of the 0.8.0 interface; the 0.8.0 release history below is left unchanged.

vbpm 0.8.0

pefa() is reorganized around what each quantity is indexed by, and gains adjacent-count stability diagnostics. This release changes results as well as structure – see the two breaking notes below.

vbpm 0.7.1

vbpm 0.7.0

Slimming release: fitted objects now store each quantity exactly once. No estimator changes – every number a model produces is unchanged.

Nothing was on CRAN when these fields were removed, so no released API is affected; scripts that read the documented top-level components (fit$Lam, fit$pi, fit$Q, …) are unaffected.

vbpm 0.6.1

vbpm 0.6.0

vbpm 0.5.0

Documentation-and-parallelism release preparing the CRAN submission, plus one estimator bug fix.

vbpm 0.4.0

vbpm 0.3.0

Fits are now classed objects, output names are plain-language, the default is quiet, and the package has vignettes. One release, one breaking-change window, before any public release — no public API ever carried the old behaviour.

vbpm 0.2.0

vbpm 0.1.0

First release.

Not implemented in this first release

All three items below were addressed in 0.4.0; they are recorded here as the state of 0.1.0. See “Known limitations” in README.md for current status.