rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
Comparison · Analytics
biocro vs vellum
A side-by-side editorial comparison of biocro and vellum — release velocity, themes, recent moves, and the top alternatives to consider.
biocro vs vellum: at a glance
What is biocro?
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
BioCro is a C++ crop growth simulator with an R interface, built from swappable modules for photosynthesis, respiration and development. Version 3.3.0 added multidimensional and one-dimensional root finders to the C++ source and put them to work immediately, replacing the fixed-point iteration used for intercellular CO2 with a Dekker root finder on the grounds that fixed-point iteration is known to be unstable there. Getting to that release also required moving from C++11 to C++17 and updating the bundled boost from 1.71 to 1.89.
What is vellum?
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
biocro vs vellum: editorial side-by-side
biocro
0.0ANALYTICS
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
◆ Current state
BioCro is a C++ crop growth simulator with an R interface, built from swappable modules for photosynthesis, respiration and development. Version 3.3.0 added multidimensional and one-dimensional root finders to the C++ source and put them to work immediately, replacing the fixed-point iteration used for intercellular CO2 with a Dekker root finder on the grounds that fixed-point iteration is known to be unstable there. Getting to that release also required moving from C++11 to C++17 and updating the bundled boost from 1.71 to 1.89.
◆ Where it's heading
Two threads run together: the biology is being broken into finer interchangeable modules — separate maintenance respiration, alternative linear and logistic SLA methods, a direct development-index module — while the numerics underneath are being made solvable in general. The root finders are explicitly staged to move into the shared biocro/framework repository, so this is groundwork for other models rather than for this package alone.
◆ Prediction
More module-level alternatives that depend on simultaneous-equation solutions are the natural follow-on, and the root finders should migrate out to biocro/framework as the notes state.
vellum
5.0ANALYTICS
vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.
◆ Current state
The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.
◆ Where it's heading
The pivotal detail is stated outright in 0.6.3 — the first bug in the series found by using the engine from vellumplot rather than testing it in isolation. Every release since names the downstream as the source: the contrast rule's false positives, the lint rules that fired on all five sample plots, the keyed roundrect batch. A rendering engine with a real grammar built on top of it is now getting the integration coverage that unit tests structurally cannot provide, and the fixes are converging on one theme: the measurement path and the draw path must not drift.
◆ Prediction
Expect the release rate to fall as the vellumplot integration surface is exhausted, with remaining work concentrated in the lint rule set now that it is meant to gate builds rather than just inform.
Alternatives to biocro and vellum
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 biocro or vellum.
epikit
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
mutagen
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
broman
A statistician's personal toolbox, growing one plotting utility at a time
qtl
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all biocro alternatives → · See all vellum alternatives →
Recent activity from biocro and vellum
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11d agovellumLinter grows to 20 rules and stops firing on every plot
- 13d agovellumAnimated SVGs no longer blink once and vanish or play in reverse
- 14d agovellumPick table now reports device pixels instead of two coordinate systems
- 14d agovellumContrast rule stops flagging every plot; gridlines become PDF artifacts
- 15d agovellumgrobwidth and grobheight now measure wrapped text, not the unwrapped line
- 15d agovellumKeyed roundrect becomes a real batch after downstream integration exposes it
- 6mo agobiocroCompiler warning blocking Linux builds fixed
- 8mo agobiocroC++ root finders added; Ci calculation moved off fixed-point iteration ⚡
- 1y agobiocroMaintenance respiration module; SLA split into swappable methods
- 2y agobiocroFirst CRAN-accepted release after a 20 MB to 5 MB cut
- 2y agobiocroDESCRIPTION date refreshed for CRAN submission
- 2y agobiocroCI workflow debugging tag, not a release
Frequently asked questions
What is the difference between biocro and vellum?
They serve adjacent needs but don't currently overlap on shipped themes. vellum is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is biocro better than vellum?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vellum is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to biocro?
Top biocro alternatives in Analytics are ranked by recent ship velocity. Browse the "biocro alternatives" section above for the current picks, or visit /alternatives/biocro-r for the full list with editorial commentary on each.
What are the best alternatives to vellum?
Top vellum alternatives in Analytics are ranked by recent ship velocity. Browse the "vellum alternatives" section above for the current picks, or visit /alternatives/vellum-r for the full list with editorial commentary on each.