-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using cell ontology with SingleR() #199
Comments
The ontology terms and the fine/broad labels don't have a 1:1 mapping. So the prediction results will change depending on whether you use one set of labels or the other. Specifically, consider these two strategies:
These will not yield the same results, as the grouping of cells in the reference data will change (remember, it's not 1:1). Which in turn changes the detected marker genes, correlation scores, etc., etc. |
@j-andrews7 and I went through all the labels and mapped them to the Cell Ontology manually. We literally went through the labels and looked them up on https://www.ebi.ac.uk/ols/ontologies/cl to figure out the best matching term.
The celldex package has some mappings between labels in its installation directory, accessible from: system.file("mapping", "hpca.tsv", package="celldex") You can have a look at them here. |
I see. |
Hi,
I've read the SingleR book, and discussion about ontology (#68) but didn't see the tutorial about cell ontology applied on the query single cell data. I wonder if I can assign labels parameters with
label.ont
? I am not familiar with the cell ontology, not sure whether it is a correct way for interpretation. How do you integrate cell ontology with celldex references?P.S. I am asking the last question is because I don't see a clear relationship, when I replace
SingleR(..., labels = db$label.main)
andSingleR(..., labels = db$label.fine)
. For example, the first two cells were both defined in "main" with Neurons, and "fine" with NPCs, why would they come up with different ontology?Thanks you.
The text was updated successfully, but these errors were encountered: