A. “Old / first Bioconductor release era” exports were small and monolithic
Using the Bioconductor 3.15 reference manual (COTAN v1-era), the exported surface is compact and centered on a single legacy class scCOTAN plus a small set of procedural functions for:
This is the “classic COTAN” feel: few entry points, user does a linear workflow, and most operations are directly on the legacy object.
B. “Current v2” exports are modular and much broader (QC + clustering + metadata + uniformity)
In the current reference manual (v2-era), the exports are clearly organized into distinct user-facing modules. You can see whole families of functions dedicated to:
Object model + conversions (interoperability)
COTAN / COTAN-class and conversions to/from SingleCellExperiment (convertFromSingleCellExperiment, convertToSingleCellExperiment)
Clusterization management (a first-class concept now)
addCondition, dropCondition, getAllConditions, plus metadata utilities like datasetTags, initializeMetaDataset, addElementToMetaDataset
Raw-data QC / cleaning became a full toolbox (not just “clean()”)
Functions and plots like cellSizePlot, mitochondrialPercentagePlot, screePlot, scatterPlot, and a suite of “fully expressed genes/cells” utilities (findFullyExpressedGenes, flagNotFullyExpressedGenes, etc.)
cellsUniformClustering, checkClusterUniformity, mergeUniformCellsClusters, plus checker classes like AdvancedGDIUniformityCheck-class, SimpleGDIUniformityCheck-class, and threshold shifting helpers
Performance / modern compute hooks
Multi-threading controls (handleMultiCore, canUseTorch) and explicit references to torch installation/usage pathways
Backward compatibility is explicitly preserved (important for reviewers)
You can still see scCOTAN-class and legacy helpers grouped under a “legacy” area in the docs/index, which signals a conscious compatibility strategy rather than a breaking rewrite.