-
Notifications
You must be signed in to change notification settings - Fork 12
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
Several quetions: NMF, Escore to p value, MAGMA gene prioritization #27
Comments
|
@kkdey |
@kkdey I still have some to clarify.
|
@KoichiHashikawa |
@KoichiHashikawa , |
Hi @kkdey,
I have following questions on GSSG pipeline. It is great if I can hear when you have a chance.
Regarding the generation of gene program .txt file from .csv. https://github.com/kkdey/GSSG STEP1. This seems compatible with converting .csv files generated at https://github.com/karthikj89/scgenetics, but not with NMF .csv files. Do you have the NMF version of GSSG?
Escore and pvalue. We have computed Escores using the same scdata. I wonder how the p-values are computed from here. The postprocessing LDSC (postprocess_ldsc_sclinker.R) produced table for E value and p.E. Initially, I thought this p.E is the p-value reported in the paper, but the values are too small and this may not be the one. It helps if there are any scripts for p-value computations for each gene program.
Another question is regarding E-value computation. Our E-value/tau results slightly differs from the one found in https://alkesgroup.broadinstitute.org/LDSCORE/Jagadeesh_Dey_sclinker/sclinker_results/
I wonder
PASS_Ulcerative_Colitis.sumstats vs include all sumstats)
For instance, for UC data, it seems you compute both BLD and GI versions. Does the LDSC results differ if I only choose GI?
In addition, I was not entirely sure by reading the paper, but is MAGMA used to determine the top driving genes in data_file_S4? How these top driving genes are computed?
Related to this, I wonder how we can go from E-score and p-value of cell type programs.
Thank you so much for your time!
Koichi
The text was updated successfully, but these errors were encountered: