-
Notifications
You must be signed in to change notification settings - Fork 20
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
Normalized contact value? #80
Comments
Hi @yanchunzhang |
Thanks a lot! Thanks, |
Hi @yanchunzhang |
Hi @ay-lab , I have a fithichip result with only 300+ merged peak to peak loops (q-value<=0.05) using the loose (P2P=0) and coverage bias setting. My QC is good according to: https://hichip.readthedocs.io/en/latest/library_qc.html. Total sequencing depth is 200M+, number of PCR duplicate reads is 40% (88M), My total number of peaks provided to the fithichip program is ~40K. Do you know why I only got 300+ loops? Thanks, |
Hi, your QC results show you are effectively left with 11.5M or so valid reads that are >10kb and useful. So you are working with quite sparse data. You haven't mentioned what resolution but likely you may want to consider 20kb or lower resolution for analysis |
@ay-lab Thank you! |
Hi @ay-lab I tried different bin sizes and q-value/p-value cutoffs for peak-to-all loop calling. Here is a screenshort at our ROI: They just look so different. It's likely that smaller bin (2.5k, 5k) will have lower read counts and thus more variance and low confidence, so they look quite different. But I'm not sure how to explain 20kb significant loops vs 5kb significant loops (0.05 qvalue), there is no overlap at all. Even if we increase to 0.5 qvalue at 5kb bin, those two short interactions in the 20kb track do not show up in the 5kb track. We have micro-capture-C data at this ROI, so we think currently loops from 5kb bin and 0.5 qvalue look better, but this q-value is so insignificant. I'm wondering if you have any thoughts. Thanks, |
Hi, do you calculate a normalized contact value in the final bed files? I checked the file but didn't see it. Just like the normalized value in Hi-C contact map.
And what's your recommend cutoff for Qvalue? 0.01 or 0.05?
Thanks,
Yanchun
The text was updated successfully, but these errors were encountered: