-
Notifications
You must be signed in to change notification settings - Fork 8
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
No methylation information was calculated for some reads #299
Comments
Hello @Wshengquan, Do you mean that you never see the (-)-strand C calls or just not always? I usually see a pattern like this:
with a command like yours. To debug that particular position, could you produce a plot from IGV (or a similar browser) at that position with the input modBAM and modification coloring turned on? You may also run
which will extract only the reads aligning to the negative strand at that position. I bet the genome browser shot will help a lot. |
Hello @Wshengquan, It is possible that you have reads covering the position on the negative strand but for one reason or another they don't have modification calls at that position. My suggestion is to look at one of these positions where you don't see a pair of (+)-strand and (-)-strand modification calls on IGV (or |
Hi,I used this command to extract methylation information:
modkit pileup ${mod_bam} ${bedmethyl_cpg} --cpg --ref ${ref} --no-filtering
However, I found that the CpG methylation information in the result file did not appear in the form of positive and negative chain pairs. I then went back to the bam file to see if I didn't have enough data and didn't have enough reads to map to this location. Take this location for example:
The resulting file revealed only one reads with methylation information and it was on the positive chain. But when I looked at the bam file, there were 26 reads in this location with both positive and negative chains, and each one carried labels with methylation information: MM and ML.
Why did this happen
Thanks a lot for your help
The text was updated successfully, but these errors were encountered: