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

Running nextNEOpi on big WGS data #82

Open
mantczakaus opened this issue Oct 18, 2024 · 2 comments
Open

Running nextNEOpi on big WGS data #82

mantczakaus opened this issue Oct 18, 2024 · 2 comments

Comments

@mantczakaus
Copy link

Hi,
I was wondering if you had any recommendations for running nextNEOpi on WGS data where one fq.gz file is over 100GB. nextNEOpi has issues with BWA, MarkDuplicates and ReadBackedPhasing. BWA can take even 18-20h; MarkDuplicates 10-15h and ReadBackedPhasing over 20h. For MarkDuplicates I already modified the code to include sort with sambamba instead of samtools because I read it would be faster. I am attaching my process.config and params.config files.
Best wishes,
Magda
params.config.txt
process.config.txt

@riederd
Copy link
Member

riederd commented Oct 18, 2024

In case you are running the pipeline on a HPC cluster or a machine with many cores you could try to increase the scatter count which might help in some places.

e.g. params.config:

scatter_count = "80"

@mantczakaus
Copy link
Author

Thanks! Unfortunately, the tasks that take a long time (the three I mentioned) are not parallelised at all so setting the scatter_count to sth higher does not help. Also, because of subdivision-mode of BALANCING_WITHOUT_INTERVAL_SUBDIVISION_WITH_OVERFLOW that is set in gatk SplitIntervals, I end up with 25 intervals only either way.

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

2 participants