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

conservation analysis when only a few syntenic blocks are available #50

Closed
zy041225 opened this issue Oct 12, 2021 · 3 comments
Closed

Comments

@zy041225
Copy link

Hi,

I would like to compare the Hi-C maps but only a few (e.g. less than five, or even one) syntenic blocks (≥ 1Mb) are available. In my understanding, the raw SN and SSIM calculation do not depend on the sample size, but the z-SSIM will be affected by the sample size. I'm wondering, in my case, if the sample size is small, is it reasonable to use chess to quantify the contact map differences?

Many thanks

Best,
Yang

@liz-is
Copy link
Collaborator

liz-is commented Oct 20, 2021

Hello,
I don't personally have experience using CHESS to compare between species, but it sounds like this is an ideal use case for the --background-query option, which will run comparisons between all regions of the genomes (non-syntenic), which can then be used to calculate a p-value for the similarity of your syntenic regions. @nickmachnik knows more about this, maybe he can give some more specific guidance (I'm realising now that the docs are not very detailed for this part!)

@nickmachnik
Copy link
Collaborator

I agree with @liz-is, if you need to put your comparison results into context of some random expectation, using the --background-query flag is an option. Your reference block will then be compared to the whole query genome, in a block size equal to the syntenic query block. Whether that is a meaningful background model depends on the goal of your analysis.

@zy041225
Copy link
Author

I see. Thank you.

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

3 participants