treasury
A thin Treasury rates wrapper has stopped adding endpoints and started making its tables self-describing.
Comparison · Analytics
chromConverter vs collinear
A side-by-side editorial comparison of chromConverter and collinear — release velocity, themes, recent moves, and the top alternatives to consider.
chromConverter vs collinear: at a glance
What is chromConverter?
The chromatography file-format translator keeps absorbing vendor formats one release at a time
chromConverter reads proprietary chromatography data files into R. Version 0.9.0 adds four input paths — Agilent ACAML markup, Agilent OpenLab .amx method files, preliminary Chromatotec .Chrom support, and plain UTF-8 CSV — while consolidating sample_id and vial into a single sample_position field and introducing a chrom_list class whose print method shows a compact metadata summary instead of dumping every chromatogram.
What is collinear?
collinear has broken its API twice to stop making the user pick thresholds.
collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.
chromConverter vs collinear: editorial side-by-side
chromConverter
0.0ANALYTICS
The chromatography file-format translator keeps absorbing vendor formats one release at a time
◆ Current state
chromConverter reads proprietary chromatography data files into R. Version 0.9.0 adds four input paths — Agilent ACAML markup, Agilent OpenLab .amx method files, preliminary Chromatotec .Chrom support, and plain UTF-8 CSV — while consolidating sample_id and vial into a single sample_position field and introducing a chrom_list class whose print method shows a compact metadata summary instead of dumping every chromatogram.
◆ Where it's heading
Format coverage is the product, so each release reads as a list of newly readable vendors. The more interesting movement in 0.9.0 is around the data rather than the parsers: consolidating metadata fields, defaulting the rainbow parser to sparse output for long-format MS data, and reordering read_agilent_d to prioritise DAD data over 2D chromatograms. Those are opinions about what users actually want back, and each one breaks existing code.
◆ Prediction
Chromatotec support is described as preliminary, which is the same language that has preceded fuller parser support in this package before.
collinear
0.0ANALYTICS
collinear has broken its API twice to stop making the user pick thresholds.
◆ Current state
collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.
◆ Where it's heading
The through-line is removing decisions the user was never well placed to make. Preference-order functions were renamed twice — first onto a metric-and-model scheme in 2.0.0, then onto a response-type scheme in 3.0.0 — and f_auto() picks one when none is given; target encoding went from automatic to opt-in; max_cor and max_vif now default to NULL and trigger a data-driven threshold derived from the 75th percentile of pairwise correlations through a sigmoid and a fitted correlation-to-VIF mapping. Each change is defensible and each one broke callers, which is the cost of this approach.
◆ Prediction
3.0.1 moved the example datasets out into a separate spatialData package and fixed four crashes rather than adding anything, so the next release is most likely more consolidation on the 3.0 surface than a fourth interface.
Alternatives to chromConverter and collinear
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 chromConverter or collinear.
soilDB
The R front door to USDA soil data finishes a long deprecation cleanup and turns local-first.
lstar
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
quanteda
Text analysis in R keeps optimising its token internals — and builds a path out to torch
moderndive
The ModernDive teaching package learns to render inside the browser that runs its own textbook
glmbayes
A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain
See all chromConverter alternatives → · See all collinear alternatives →
Recent activity from chromConverter and collinear
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agochromConverterFour new vendor formats and a breaking metadata consolidation
- 3mo agocollinearNamespace, NA and sf fixes; example data moves to spatialData
- 8mo agocollinearAdaptive thresholds, multi-response support and a new output class ⚡
- 1y agochromConvertersample_names reworked to read names from file metadata
- 1y agocollinearCategorical responses, f_auto() defaults and future-based parallelism ⚡
Frequently asked questions
What is the difference between chromConverter and collinear?
They serve adjacent needs but don't currently overlap on shipped themes. chromConverter and collinear 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 chromConverter better than collinear?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. chromConverter and collinear 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 chromConverter?
Top chromConverter alternatives in Analytics are ranked by recent ship velocity. Browse the "chromConverter alternatives" section above for the current picks, or visit /alternatives/chromconverter for the full list with editorial commentary on each.
What are the best alternatives to collinear?
Top collinear alternatives in Analytics are ranked by recent ship velocity. Browse the "collinear alternatives" section above for the current picks, or visit /alternatives/collinear for the full list with editorial commentary on each.