← Back to home
Comparison · Analytics

biocro vs etn

A side-by-side editorial comparison of biocro and etn — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r

biocro vs etn: at a glance

Featurebiocroetn
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr, crop-modeling, cpp, numerical-methodsr, telemetry, marine-science, api-client
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

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.

Read the full biocro trajectory →

What is etn?

etn stopped being an RStudio-server package and became something you can run anywhere.

etn is the R client for the European Tracking Network's acoustic telemetry database, maintained at INBO. The 3.0.0 release routes queries through an API served by the companion etnservice package, so the package no longer requires a session on the ETN RStudio server. Credentials moved out of a connection object and into .Renviron, and the data model was rescoped in 2.0.0 around tag_serial_number so acoustic work is one scope among several rather than the whole package.

Read the full etn trajectory →

biocro vs etn: editorial side-by-side

B
biocro
ANALYTICS
0.0

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.

E
etn
ANALYTICS
0.0

etn stopped being an RStudio-server package and became something you can run anywhere.

◆ Current state

etn is the R client for the European Tracking Network's acoustic telemetry database, maintained at INBO. The 3.0.0 release routes queries through an API served by the companion etnservice package, so the package no longer requires a session on the ETN RStudio server. Credentials moved out of a connection object and into .Renviron, and the data model was rescoped in 2.0.0 around tag_serial_number so acoustic work is one scope among several rather than the whole package.

◆ Where it's heading

Two arcs run in parallel: widening access, and making room for non-acoustic data. The access work has been deliberate — an API-backed beta in 2024, then a stable release that picks the transport automatically and checks that a local etnservice install matches the deployed one, because the same query returning different results by transport would be worse than requiring the server. The Darwin Core export added in 2.1.0 points the same outward direction, moving data to OBIS and GBIF instead of keeping it in the ETN silo.

◆ Prediction

The cpod scope named in the 2.0.0 notes is the most likely next addition, now that the naming and the API transport are both in place to carry it.

Alternatives to biocro and etn

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 etn.

See all biocro alternatives → · See all etn alternatives →

Recent activity from biocro and etn

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5mo agoetnetn runs off the ETN RStudio server via the etnservice API
  2. 6mo agobiocroCompiler warning blocking Linux builds fixed
  3. 6mo agoetnData model rescoped; acoustic becomes one named scope
  4. 6mo agoetnwrite_dwc() exports telemetry as Darwin Core for OBIS and GBIF
  5. 6mo agoetndepth_in_meters added to acoustic detections
  6. 6mo agoetnwrite_dwc() fixes for uppercase project codes
  7. 6mo agoetnNA formatting and duplicate receiver ID fixes
  8. 8mo agobiocroC++ root finders added; Ci calculation moved off fixed-point iteration
  9. 1y agobiocroMaintenance respiration module; SLA split into swappable methods
  10. 2y agobiocroFirst CRAN-accepted release after a 20 MB to 5 MB cut
  11. 2y agobiocroDESCRIPTION date refreshed for CRAN submission
  12. 2y agobiocroCI workflow debugging tag, not a release

Frequently asked questions

What is the difference between biocro and etn?

Both compete on the same themes — r — within Analytics. biocro and etn 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 biocro better than etn?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. biocro and etn 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 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 etn?

Top etn alternatives in Analytics are ranked by recent ship velocity. Browse the "etn alternatives" section above for the current picks, or visit /alternatives/etn-r for the full list with editorial commentary on each.