Open lgeistlinger opened 6 days ago
Below an attempt to make the paragraphs under Key Features a bit more concise and precise:
Visualization of Cell Type Annotations: illustrates the distributions of cell type annotations of the query and reference dataset, allowing the user to identify potential differences in the cell type composition between datasets.
Evaluation of QC and Annotation Scores: provides functionality for assessing the impact of frequently used QC criteria on the cell type annotation confidence, allowing the user to identify systematic relationships between QC metrics and the predicted cell type categories.
Evaluation of Dataset and Marker Gene Alignment: provides functionality for assessing dataset alignment through quantitative comparison of query-to-reference projections in reduced dimension space. Additional functionality for assessing marker gene expression across datasets allows the user to identify potential misalignments between reference and query on the level of individual genes.
Statistical Measures to Assess Dataset Alignment: shouldn't that be part of the previous paragraph / functionality category?
Detection of Annotation Anomalies: focuses on identifying inconsistencies or anomalies in cell type annotations between the query and reference datasets through comparison of expert annotations with annotations derived from automated methods. By highlighting discrepancies that could be indicative of potential errors, this feature aids in refining and improving the accuracy and reliability of cell type classifications.
Analysis of Distances Between Specific Cells and Cell Populations: looks good
Thanks for your very clear feedback, @lgeistlinger. For the "Statistical Measures to Assess Dataset Alignment" there is indeed an argument that could be made to merge that collection of functions to the previous collection of functions in "Evaluation of Dataset and Marker Gene Alignment". It is really a matter of taste to create this hierarchy of different functionalities, but I would argue separating them is a good idea solely based on the fact that combining these two sets of functions together could make it a little too long/overwhelming in a single vignette.
Two different installation methods are introduced for installing the release (via
BiocManager::install
) and the development version (viaremotes::install_github
) of the package.Note that
BiocManager::install
can be used for both. In fact,BiocManager::install
simply invokesremotes::install_github
when provided a github account and repo string, that means here:BiocManager::install("ccb-hms/scDiagnostics")
.This will simplify installation instructions for end users.
Further:
Under installation instructions for Release Version:
Under Usage: