-
Notifications
You must be signed in to change notification settings - Fork 159
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
After basecallling with dorado, nanopolish was unable to recognize methylation information #1140
Comments
Is the data new R10 data? |
Yes, the data is new R10 data |
nanopolish doesn't support r10 data yet. You can try f5c which is an optimised re-implementation of the index, call-methylation and eventalign modules in nanopolish that also supports r10 and rna004. |
Could you please open an issue on the f5c repo? I will answer there. What is the mapper you are using - MInimap2? If MInimap2 aligns well for Guppy and not DOrado - Might be something with Dorado - are you using the correct model? |
Thank you very much for your help! |
Could you open an issue with this log at https://github.com/hasindu2008/f5c/issues as this more relevant there now. |
Dear all,
In the Quickstart-calling methylation with nanopolish section of the nanopolish usage instructions, guppy basecaller is used to identify the base signal of reads. I replaced guppy with ont's newly recommended basecalling tool, dorado. The rest of the steps remained the same, but the methylation information was significantly less than with guppy.Is it because dorado and nanopolish are not compatible?
Why does this happenI examined my process log and found that while the number of reads was still high when using the nanopolish index and minimap2, the number of reads decreased significantly when using nanopolish call-methylation.
Thank you,
ShengquanWang
The text was updated successfully, but these errors were encountered: