Skip to content
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

[Q] How to test significance of change between pileups? #148

Open
AudreyBaguette opened this issue Jun 3, 2024 · 1 comment
Open

[Q] How to test significance of change between pileups? #148

AudreyBaguette opened this issue Jun 3, 2024 · 1 comment

Comments

@AudreyBaguette
Copy link

State the question
I generated a set of pileups, all using the same list of regions, but with different Hi-C files. How do I test if the resulting pileups are significantly different from one another?

What have you tried?

  • I tried finding an existing method, but didn't find any
  • Methods form a paper suggested separating the pileup to get each snip, computing one pileup value per snip (ex the mean of the middle 3x3 pixels), then comparing the distribution of snip values between the two Hi-C files with a t-test. Cooltools permits to find the values for each snip, but not coolpup

Additional context
While the method stated above, using cooltools, could work for pileups using a set of punctual regions (like CTCF peaks), cooltools isn't able to take as input a set of ranges (like compartments). It'd like to generate pileups for various Hi-C maps (with different coverage) then see if the pileups I obtain are significantly different from each other considering the changes in coverage.

@efriman
Copy link
Collaborator

efriman commented Jun 6, 2024

There's no statistical tests implemented in coolpup.py, but you can extract contact frequency distributions along the "stripes" (store_stripes=True or --stripe). I'm not sure if this is what you mean but you can see an example of how to get the values here: https://github.com/efriman/Friman_etal_ULI/blob/main/pileups/TSS_quartiles_score_stripes.ipynb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants