skytrackr
Light-based animal geolocation gets a second model that stops assuming the bird sat still.
Comparison · Infra & APIs
portfoliobacktest vs whirl
A side-by-side editorial comparison of portfoliobacktest and whirl — release velocity, themes, recent moves, and the top alternatives to consider.
portfoliobacktest vs whirl: at a glance
What is portfoliobacktest?
Four dormant years end with a test fix, not a feature
portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.
What is whirl?
whirl turned script logging into a standardized provenance artifact regulators can read.
A parallel R script runner that produces execution logs, aimed at regulated analysis environments. The 0.3.0 release added write_biocompute(), emitting logs as BioCompute Objects in standardized JSON, and simplified the approved-package check to a plain package@version vector. Since then the work has been about what the log can be trusted to contain: an environment_secrets option to keep secret variables out of it, direct versus indirect package usage distinguished and highlighted against the approved list, and the same approval check extended to Python packages.
portfoliobacktest vs whirl: editorial side-by-side
portfoliobacktest
0.0INFRA · APIS
Four dormant years end with a test fix, not a feature
◆ Current state
portfolioBacktest runs portfolio strategies across multiple datasets and resampled windows, producing performance tables, leaderboards and charts. After a run of substantive releases through 2021 and early 2022 it went quiet for four years. The May 2026 release does one thing: fix unit tests against a breaking change in PerformanceAnalytics::Return.portfolio(), which now returns results for the full input series rather than only from the first weight date.
◆ Where it's heading
The development work is behind it. The 2019 to 2022 releases built the substance — parallel execution, resampling that works beyond stock data and beyond daily bars, transaction-cost-aware designs through w_current, and a switch from compounded to uncompounded returns in the Sharpe and annualized return calculations. Since then the package has moved only when a dependency forced it, and even then only far enough to keep the tests green.
◆ Prediction
Nothing in the entries suggests planned work; the next release is most likely triggered by another dependency change, on the same four-year-gap pattern.
whirl
0.0INFRA · APIS
whirl turned script logging into a standardized provenance artifact regulators can read.
◆ Current state
A parallel R script runner that produces execution logs, aimed at regulated analysis environments. The 0.3.0 release added write_biocompute(), emitting logs as BioCompute Objects in standardized JSON, and simplified the approved-package check to a plain package@version vector. Since then the work has been about what the log can be trusted to contain: an environment_secrets option to keep secret variables out of it, direct versus indirect package usage distinguished and highlighted against the approved list, and the same approval check extended to Python packages.
◆ Where it's heading
The through-line is the log as evidence rather than as debugging output. Every recent addition either widens what the log proves — which packages were really used, in which language, against which approved list — or narrows what it must not leak. Setting options only through an explicit with_options argument to run() and getting renv library paths right for Quarto both point the same way: reproducible, auditable child sessions with nothing implicit.
◆ Prediction
Expect the approved-package and provenance machinery to keep expanding across languages and environments, since Python approval checks followed the R ones and both feed the same log.
Alternatives to portfoliobacktest and whirl
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 portfoliobacktest or whirl.
ESPHome
ESPHome ships on a calendar, and the August beta train is now four builds deep.
rapr
rapr generalises its Rangeland Analysis Platform API access one endpoint at a time
b3doc
A small B-Cubed utility for turning R Markdown into publishable docs
gpkg
An R interface to GeoPackage that keeps sanding down its own API
logger
R's logging package handed to new maintainers and rebuilt from the inside out
See all portfoliobacktest alternatives → · See all whirl alternatives →
Recent activity from portfoliobacktest and whirl
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agoportfoliobacktestTests fixed for a PerformanceAnalytics breaking change
- 6mo agowhirlExplicit option passing to child sessions; renv path fix
- 11mo agowhirlLogs flag package approval status and exclude secrets
- 1y agowhirlwhirl 0.3.0 ⚡
- 4y agoportfoliobacktestSharpe ratio charts and reworked weight outputs
- 4y agoportfoliobacktestUncompounded return metrics and transaction-cost-aware designs
- 5y agoportfoliobacktestResampling generalised beyond daily stock data
- 6y agoportfoliobacktestCRAN example fixes and vignette references
- 6y agoportfoliobacktestDrawdown, cumulative return and stacked bar charts
Frequently asked questions
What is the difference between portfoliobacktest and whirl?
They serve adjacent needs but don't currently overlap on shipped themes. portfoliobacktest and whirl 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 portfoliobacktest better than whirl?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. portfoliobacktest and whirl 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 portfoliobacktest?
Top portfoliobacktest alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "portfoliobacktest alternatives" section above for the current picks, or visit /alternatives/portfoliobacktest for the full list with editorial commentary on each.
What are the best alternatives to whirl?
Top whirl alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "whirl alternatives" section above for the current picks, or visit /alternatives/whirl for the full list with editorial commentary on each.