-
Notifications
You must be signed in to change notification settings - Fork 27
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
edgeR analysis not preserving the level and order information of the Cell_type #21
Comments
I don't think this is a bug? You can just reset the factor levels in your DE object after running it? |
I have the same issue, I don't really understand how I'm supposed to reset the factor levels in the DE object after I've run it.
DE object, cell type is just nonPT epithelia - I can't see any other option to view different cell types
When I use to_pseudobulk I get matrices with all the cell types present |
Set the factor levels before. |
Hi Thank you for your quick reply! I have tried: metadata$compartment <- as.factor(metadata$compartment) However I still have the same problem, do I need to set them a different way? I am new to DE analysis so I'm sorry if this is something very simple. |
You need to set the order - levels = c(). This is not a libra bug so better to post such issues on the relevant stack exchange thread. |
Hi,
I'm interested in looking at DE differences between, for example, edgeR and MAST. Running edgeR on a seurat object works well, but the output loses cell_type level information, while the MAST run does not.
SEURAT$cell_type is a factor, whereas after running edgeR levels(edgeR_output$cell_type) returns NULL . After MAST, levels(MAST_output$cell_type) reports the factor levels correctly.
Is that an issue for the underlying algorithms ?
It would be really nice if the edgeR calculation could maintain both the levels AND order of the input matrix, so that it isn't necessary to do that manually for all of the different subclustering analysis that we need to do.
Thanks!
Robert
The text was updated successfully, but these errors were encountered: