-
Notifications
You must be signed in to change notification settings - Fork 50
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
minimap2 alignment step fails because of samtools sort #145
Comments
Hi @trum994, it is quite likely that the workflow has exceeded its memory limit for the alignment step. Can you confirm that you're using the latest version as we've made several recent improvements to the memory directives and performance generally. |
I'm getting a similar error with the gencode hg38 reference. I'm using the current "master" version of the pipeline.
|
I am also having workflows fail with this error. I could complete the workflow with the same settings for 2 of 3 samples, but one keeps failing and it is not even a large file (8 GB cram). I have 64 GB memory available and have explicitly allocated 60 GB to run this workflow, but in the final report, the process bam_ingress:minimap2_alignment only has 16 GB allocated.
|
I was able to run this workflow today after restarting the computer, which emptied my swap. Before, htop showed the swap at 6 GB (of 8 GB total). Not sure what was causing the swap to fill up, only EPI2ME was running and after successful workflow completion the swap emptied again. |
Thanks all for these reports. We have been investigating ways to curtail
the memory usage of minimap for this step and will have a patch release out
next week to try and alleviate the problems you've been having with the
alignment step.
…On Fri, 15 Mar 2024, 12:36 LisaHagenau, ***@***.***> wrote:
I was able to run this workflow today after restarting the computer, which
emptied my swap. Before, htop showed the swap at 6 GB (of 8 GB total). Not
sure what was causing the swap to fill up, only EPI2ME was running and
after successful workflow completion the swap emptied again.
—
Reply to this email directly, view it on GitHub
<#145 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIN6OTD2KI3FVWMPIJEZXTYYLTLXAVCNFSM6AAAAABDMZM7IGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJZGU3TIMRQGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
@LisaHagenau @stfacc @trum994 we have recently released several updates to the workflow, could you please check if you still come across the same problem? |
Ask away!
I'm using this workflow on our HPC via Singularity. The input bam is a Promethion run mini bams merged via samtools merge into a single bam (140GB). Is this a missing header issue or a RAM issue or something else?
This is the output I get:
The text was updated successfully, but these errors were encountered: