-
Notifications
You must be signed in to change notification settings - Fork 21
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
Advice about a dataset with conditions #52
Comments
Hi @AmelZulji, when doing case-control comparisons we've usually run Pando on both conditions together and then tested for differential module activity or reg region accessibility. I personally would probably not constrain the GRN to DEGs, because a lot of important regulators will not be DE and so it might be hard to get a well-connected GRN |
Thank you for the answer, @joschif! When it comes to module activity, do you first build module activity with If yes, what test would you use to test differentia module activity (I am having 2 groups with 5 biological replicate each)? |
Hi @AmelZulji, yes, that |
Thank you, @joschif! One last question: in order to avoid bias from number of cells, pseudobulk profiles should be generated using averages, or? |
hi @joschif, congrats on the publication and thank you for porting the analysis in a package!
I would like to ask for an advice for analyzing a 10x multiome dataset (control and condition with multiple biological replicates) using Pando.
I want to analyze each cell type separately (which should be fine as mentioned in #49), but since im interested into differences between control and condition within the same cell type, im not sure what would be the best way to call
infer_grn()
. I was thinking about:infer_grn(genes = cell_type_specific_DEGs)
and interpreting the network as condition specific, but im not sure if that makes sense?!What do you think about it, do you have any advice? Is there any use case of pando in the experimental design similar to the one I have?
Would be very thankful for support!
Amel
The text was updated successfully, but these errors were encountered: