tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
forcis vs ijtiff
A side-by-side editorial comparison of forcis and ijtiff — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
forcis vs ijtiff: at a glance
What is forcis?
A foraminifera data-access package whose entire release history is the rOpenSci review process.
forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.
What is ijtiff?
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
ijtiff reads and writes TIFF files the way ImageJ writes them, which ordinary R TIFF readers get wrong — multi-channel, multi-frame, and unusual bit depths. The 3.1.x line is dominated by memory correctness in the C tag-handling layer, alongside dropping the large imager dependency from the display path. Cadence is sporadic, with multi-year gaps.
forcis vs ijtiff: editorial side-by-side
forcis
0.0ANALYTICS
A foraminifera data-access package whose entire release history is the rOpenSci review process.
◆ Current state
forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.
◆ Where it's heading
The package is moving from research artifact to reviewed, distributable infrastructure — submitted to rOpenSci at 0.1.0, integrated review feedback at 1.0.0, cleared CRAN at 1.0.1. That arc is complete, so the next phase should be the first release driven by users rather than reviewers.
◆ Prediction
With review and CRAN acceptance both behind it, the next release is most likely to track upstream FORCIS database changes or add query conveniences; the entries themselves say nothing about planned features.
ijtiff
0.0ANALYTICS
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
◆ Current state
ijtiff reads and writes TIFF files the way ImageJ writes them, which ordinary R TIFF readers get wrong — multi-channel, multi-frame, and unusual bit depths. The 3.1.x line is dominated by memory correctness in the C tag-handling layer, alongside dropping the large imager dependency from the display path. Cadence is sporadic, with multi-year gaps.
◆ Where it's heading
Two threads run through the window. The C layer is being hardened — memory leaks in tag handling, buffer cleanup, PROTECT errors, validation of malformed files — which is the kind of work that surfaces when a package gets run against real-world files at volume. Separately, the R layer is shedding dependencies, with base graphics replacing imager for display. Both make the package cheaper and safer to depend on rather than more capable.
◆ Prediction
Expect continued C-level correctness work rather than format features, since three of the last three substantive releases were memory or compiler fixes.
Alternatives to forcis and ijtiff
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 forcis or ijtiff.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all forcis alternatives → · See all ijtiff alternatives →
Recent activity from forcis and ijtiff
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agoforcisPost-CRAN-review example and practice cleanup
- 1y agoforcis1.0.0 incorporates rOpenSci review feedback
- 1y agoijtiffPROTECT-error and documentation fixes across 3.1.1-3.1.3
- 1y agoijtiffDrops the imager dependency; fixes tag-handling memory leaks
- 1y agoforcisFirst stable release, submitted to rOpenSci
- 3y agoijtiffMoves to rlang::abort() and away from magrittr
- 3y agoijtiffFixes NEWS.md headings
- 5y agoijtiffCompatibility with libtiff using C99 stdint.h
- 5y agoijtiffQuiets pkg-config warnings; drops LazyData
Frequently asked questions
What is the difference between forcis and ijtiff?
Both compete on the same themes — r-package — within Analytics. forcis and ijtiff 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 forcis better than ijtiff?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. forcis and ijtiff 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 forcis?
Top forcis alternatives in Analytics are ranked by recent ship velocity. Browse the "forcis alternatives" section above for the current picks, or visit /alternatives/forcis for the full list with editorial commentary on each.
What are the best alternatives to ijtiff?
Top ijtiff alternatives in Analytics are ranked by recent ship velocity. Browse the "ijtiff alternatives" section above for the current picks, or visit /alternatives/ijtiff for the full list with editorial commentary on each.