rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
fio vs PEIMAN2
A side-by-side editorial comparison of fio and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.
fio vs PEIMAN2: at a glance
What is fio?
Input-output economics in R with a Rust core, now spanning multiple regions.
fio builds and analyses input-output models in R, using an R6 object for the model and Rust with the faer crate for the linear algebra behind technical coefficients and the Leontief inverse. Version 1.0.0 extended it from single-region tables to multi-regional models with spillover analysis, and 1.1.0 immediately corrected the naming and measures that release introduced, renaming shock-origin columns that had been labelled as destinations and replacing an interdependence index with spillover balance and export share.
What is PEIMAN2?
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
PEIMAN2 does enrichment analysis over post-translational modifications, testing whether a protein list is enriched for particular PTMs against UniProt-derived annotations, with translation functions bridging to mass spectrometry workflows. Its answers are only as current as its bundled database, and until June that database could only be refreshed by releasing a new package version. Version 1.1.0 changes that.
fio vs PEIMAN2: editorial side-by-side
fio
0.0INFRA · APIS
Input-output economics in R with a Rust core, now spanning multiple regions.
◆ Current state
fio builds and analyses input-output models in R, using an R6 object for the model and Rust with the faer crate for the linear algebra behind technical coefficients and the Leontief inverse. Version 1.0.0 extended it from single-region tables to multi-regional models with spillover analysis, and 1.1.0 immediately corrected the naming and measures that release introduced, renaming shock-origin columns that had been labelled as destinations and replacing an interdependence index with spillover balance and export share.
◆ Where it's heading
The package built its foundation first and its scope second. The 0.1.x releases were almost entirely about making a Rust-backed R package install reliably across platforms and toolchain versions, with the actual economics settled at 0.1.0. Once that was stable, 1.0.0 added the multi-regional layer in one release, and 1.1.0 shows the usual consequence of a large surface arriving at once: names and derived measures needing correction before they harden. Breaking changes are being taken freely while the multi-regional interface is young.
◆ Prediction
Expect further refinement of the multi-regional measures before the interface settles, given that 1.1.0 revised them within three months of their introduction. The Rust core makes larger multi-regional systems tractable, so extending coverage to more published multi-region tables is the obvious direction, though these entries name no specific dataset.
PEIMAN2
0.0INFRA · APIS
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
◆ Current state
PEIMAN2 does enrichment analysis over post-translational modifications, testing whether a protein list is enriched for particular PTMs against UniProt-derived annotations, with translation functions bridging to mass spectrometry workflows. Its answers are only as current as its bundled database, and until June that database could only be refreshed by releasing a new package version. Version 1.1.0 changes that.
◆ Where it's heading
The package has been moving from a fixed snapshot toward versioned, user-selectable data. Earlier releases updated the bundled database in place — 1.0.0 shipped the March 2025 version and said little else — which meant the annotation vintage was whatever the package version implied. Now update_peiman_database() downloads and caches external database files and UniProt PTM lists, enrichment workflows take a database_version argument, and the mass-spec translators take a ptmlist_version, so an analysis can pin a dated database rather than a package release. The CRAN-safe default is preserved deliberately: loading, examples and checks still use the bundled internal data and need no network.
◆ Prediction
Version pinning is now expressible but the release notes do not describe how a chosen version is recorded in output, so surfacing the active database version in results is the natural companion. The database and the UniProt PTM list are versioned separately, which leaves room for a combined manifest.
Alternatives to fio and PEIMAN2
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 fio or PEIMAN2.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
Recent activity from fio and PEIMAN2
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agoPEIMAN2Database updates decouple from package releases ⚡
- 2mo agofioSpillover columns renamed to name the shock's origin
- 5mo agofioMulti-regional input-output models and spillover analysis ⚡
- 1y agoPEIMAN2Bundled database refreshed to the March 2025 UniProt vintage
- 1y agoPEIMAN2Documentation fix for the second example dataset
- 1y agofioToolchain fixes for R-devel and Windows linking
- 1y agofioSystem check scripts handle a missing Rust toolchain
- 1y agofioRust minimum version lowered to widen installability
- 2y agofioFirst release: Rust-backed input-output modelling in R ⚡
- 2y agoPEIMAN2Background lists for SEA and PSEA; tidyverse dependency dropped
Frequently asked questions
What is the difference between fio and PEIMAN2?
They serve adjacent needs but don't currently overlap on shipped themes. fio and PEIMAN2 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 fio better than PEIMAN2?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fio and PEIMAN2 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 fio?
Top fio alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "fio alternatives" section above for the current picks, or visit /alternatives/fio for the full list with editorial commentary on each.
What are the best alternatives to PEIMAN2?
Top PEIMAN2 alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PEIMAN2 alternatives" section above for the current picks, or visit /alternatives/peiman2 for the full list with editorial commentary on each.