← Back to home
Comparison · Infra & APIs

inti vs phyloatlas

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

inti vs phyloatlas: at a glance

Featureintiphyloatlas
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesplant-science, pca, shiny, reproducible-reportingphylogenetics, research-data, data-provenance, open-science
Last editorial update3h ago1h ago
WebsiteVisit →Visit →

What is inti?

inti keeps compounding small statistics and publishing tools for plant-science labs.

inti bundles the tooling a plant-science lab uses end to end: the Yupana analysis app, the Tarpuy experiment planner, scihub and rticle document rendering, and helpers for ANOVA and heritability. The 0.7.x line has been dominated by one thread, a PCA sub-module in Yupana carrying variable contribution, dimension correlation, supplementary variables and per-dimension selection. Releases are cumulative: 0.7.0, 0.7.1 and 0.7.2 all restate the same PCA lines, with each tag adding a few items on top, and 0.7.0 itself is split across two tags published 35 seconds apart.

Read the full inti trajectory →

What is phyloatlas?

An atlas of the tree of life that keeps publishing what it got wrong, and stopped shipping the trees it does not own.

This is a curated deposit of species-level phylogenies — 264 trees across 62 partitions, 247 of them time-calibrated — paired with a species-name dictionary of roughly 638,000 standardized labels and per-tree provenance. It is moving through peer review at Methods in Ecology and Evolution, and the release stream is essentially a public erratum log: eight releases in five weeks, each reconciling the deposit against source papers, the manuscript, and its own metadata. The most recent replaced the turtle canonical with a 274-tip ultrametric chronogram after the previous tree failed time-calibration integrity checks.

Read the full phyloatlas trajectory →

inti vs phyloatlas: editorial side-by-side

I
inti
INFRA · APIS
2.5

inti keeps compounding small statistics and publishing tools for plant-science labs.

◆ Current state

inti bundles the tooling a plant-science lab uses end to end: the Yupana analysis app, the Tarpuy experiment planner, scihub and rticle document rendering, and helpers for ANOVA and heritability. The 0.7.x line has been dominated by one thread, a PCA sub-module in Yupana carrying variable contribution, dimension correlation, supplementary variables and per-dimension selection. Releases are cumulative: 0.7.0, 0.7.1 and 0.7.2 all restate the same PCA lines, with each tag adding a few items on top, and 0.7.0 itself is split across two tags published 35 seconds apart.

◆ Where it's heading

Two axes are moving. Analysis is deepening inside Yupana, where PCA went from a single view to a sub-module with its own contribution and correlation outputs across three tags. Publishing is widening around rticle() and scihub(), which now handle Google Docs markdown, crossrefs and page numbers, continuing the gdocs2qmd work from the 0.6 line. Neither is a change of direction; the package accretes features where the maintainer's own research workflow needs them.

◆ Prediction

Expect the next tag to extend the PCA sub-module again and add another rticle() or scihub() rendering detail, on the two-to-six-week cadence the 0.7 line has held.

P
phyloatlas
INFRA · APIS
0.0

An atlas of the tree of life that keeps publishing what it got wrong, and stopped shipping the trees it does not own.

◆ Current state

This is a curated deposit of species-level phylogenies — 264 trees across 62 partitions, 247 of them time-calibrated — paired with a species-name dictionary of roughly 638,000 standardized labels and per-tree provenance. It is moving through peer review at Methods in Ecology and Evolution, and the release stream is essentially a public erratum log: eight releases in five weeks, each reconciling the deposit against source papers, the manuscript, and its own metadata. The most recent replaced the turtle canonical with a 274-tip ultrametric chronogram after the previous tree failed time-calibration integrity checks.

◆ Where it's heading

The project's defining decision is that it archives the recipe rather than the corpus. Since 1.0.3 the Zenodo deposit holds metadata, provenance, and standardization code while the tree files live at their original sources, and the same principle was applied again when the TimeTree-of-Life was removed at the TimeTree project's request and reduced to a citation. What makes the correction log unusual is its direction: partitions keep getting reclassified from dated to undated as verification confirms the source papers described chronograms they never deposited. The atlas is being built to be honest about archival uncertainty rather than to maximize coverage.

◆ Prediction

The release cadence is driven by the manuscript review cycle, so expect corrections to continue until MEE acceptance and then slow sharply; the open thread most likely to produce the next one is the remaining recoverable archival uncertainty flagged across non-Condamine dated source trees.

Alternatives to inti and phyloatlas

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 inti or phyloatlas.

See all inti alternatives → · See all phyloatlas alternatives →

Recent activity from inti and phyloatlas

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

  1. 22d agointiscihub() gains pages, rticle() improves crossrefs
  2. 1mo agophyloatlasv1.0.8 — turtle chronogram canonical; MEE integrity pass
  3. 1mo agophyloatlasv1.0.7 — restore species-name dictionary
  4. 1mo agophyloatlasv1.0.6 — data-integrity corrections + TimeTree de-redistribution
  5. 1mo agointi0.7.1 restates the 0.7.0 PCA and Tarpuy notes
  6. 2mo agophyloatlasv1.0.5 — consistency corrections
  7. 2mo agointiPCA sub-module adds contribution and dimension correlation
  8. 2mo agointiNew rticle() renders Google Docs markdown into articles
  9. 2mo agophyloatlasv1.0.4 — data corrections + canonical succession (Supplementary Table S7)
  10. 2mo agophyloatlasv1.0.3 — title alignment, LICENSE, three-category framework, sensitivity bounds
  11. 10mo agointiH2cal() takes factors as a formula; scihub() templates updated
  12. 11mo agointiSciHub RStudio addin arrives; gdocs2qmd table export fixed

Frequently asked questions

What is the difference between inti and phyloatlas?

They serve adjacent needs but don't currently overlap on shipped themes. inti is currently shipping more aggressively (velocity 2.5 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 inti better than phyloatlas?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inti is currently shipping more aggressively (velocity 2.5 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to inti?

Top inti alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "inti alternatives" section above for the current picks, or visit /alternatives/inti for the full list with editorial commentary on each.

What are the best alternatives to phyloatlas?

Top phyloatlas alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "phyloatlas alternatives" section above for the current picks, or visit /alternatives/phylo-species-atlas for the full list with editorial commentary on each.