-
Notifications
You must be signed in to change notification settings - Fork 46
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
celltypist before/after batch correction #119
Comments
@malonzm1, |
Thanks! |
Is |
@malonzm1, depends, but |
@ChuanXu1 Based on what you've described, it seems that batch effects will not impact the predicted_labels, but they can influence the majority_voting results??? After applying harmony to remove batch effects, my data also encountered the issue of "Invalid expression matrix in .X, expect log1p normalized expression to 10000 counts per cell; will use .raw.X instead." |
@smallsmalltown, as I remember, Harmony will not change the expression values but produce only the corrected latent space. To predict your data using CellTypist, you need to provide a normalized gene expression in either .X or .raw.X. |
@ChuanXu1 Can you explain more about the latent space idea and harmony?. If I integrated using harmony in R then converted my object to h5ad then provided celltypist with the normalized .X of it, what would be better predicted_labels or majority voting? will celltypist use the latent space of the samples at all? |
@Flu09, celltypist does not use the latent space to predict cell types, namely, the |
I see thank you but if i will combine two studies and i noticed that the overall counts in one study are fewer than the other. should the annotation by celltypist be done on each study alone. |
@Flu09, it's safer to do this for each dataset separately to ensure sufficient gene overlap between your data and the model used. |
Hi,
I perform batch correction using scVI. But I perform celltypist prediction before batch correction. Is it better to perform celltypist after batch correction or it doesn't matter?
Good day.
The text was updated successfully, but these errors were encountered: