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

Nanopolish call-methylation Processing Speed #1113

Open
ghost opened this issue Sep 24, 2023 · 2 comments
Open

Nanopolish call-methylation Processing Speed #1113

ghost opened this issue Sep 24, 2023 · 2 comments

Comments

@ghost
Copy link

ghost commented Sep 24, 2023

Hello, I'm using nanopolish call-methylation on an Ontario long read data with an average read depth of 35. I'm using 40 processors with 4 GB of memory per processor. I'm using the standard parameters (-t, -r, -b, -g). The job has been running for 12 days, and it has only completed processing chromosomes 1-4 and 10-22 so far. I'm wondering if there are ways to speed up the process, or if this long processing time is expected for this tool?

@hasindu2008
Copy link
Contributor

Likely to be the fast5 IO bottleneck
You may try https://github.com/hasindu2008/f5c/ with the --iop option to spawn parallel processes for IO. F5c should give same output as nanopolish.

To go even more faster, the best solution is to convert your fast5 to blow5 using slow5tools and then run nanopolish or f5c on it. Instructions are at https://hasindu2008.github.io/slow5tools/workflows.html

.

@ghost
Copy link
Author

ghost commented Sep 25, 2023

Thank you for the quick and helpful response. I will try your suggestions. I am wondering if it is possible to use intervals (one Chr per job) when running the Nanopolish call-methylation and the calculate_methylation_frequency.py, and at the end concatenate the methylation_frequency.tsv files from each chromosome into a single file?

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

1 participant