-
Notifications
You must be signed in to change notification settings - Fork 99
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
mbias plot methylation rate fluctuations #664
Comments
The steep drop at the beginning of Read 2 is almost certainly a consequence of a bias brought in by the end-repair of fragments, as discussed in this QCFail article. Ignoring the first 2-4bp will alleviate this. I don't really know the reason why the levels are a meandering around the 80% mark in Read 2, and only reach the Read 1 levels ~100bp into the read - there clearly seems to be some technical reason. Maybe it has to do the sequencing run as such? |
Thanks for your explanation! The low quailty bases have been detected at the end of read 2, while we cut them out using Trimmomatic. Maybe that is the reason why the mbias plot of read 2 was unsteady. May I ask for any suggestions? And based on this situation, can I use this |
I don't think this has anything to do with the 3' trimming of low qualities, especially since the more variable part is at the 5' end. I personally would re-run the methylation extraction while using You will also notice that the total number of calls in Read 2 goes down with increased length as a function of the overlap detection and removal, so all in all Read 1 will get some more weight anyways. |
Thanks for your generous advice, i would try it. |
The data I used has been processed by fastqc and Trimmomatic. Then the data has been processed by
bismark
,deduplicate_bismark
andbismark_methylation_extractor
as the manual told.As the mbias plots show, the methylation level in read 1 seems to be stable. However, the methylation read 2 is very volatile. May I ask the possible reasons for this fluctuations appears in this read 2 plot.
The text was updated successfully, but these errors were encountered: