-
Notifications
You must be signed in to change notification settings - Fork 190
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
error in metaWRAP binning command #14
Comments
It looks like the samtools sort function is running out of memory. By default, it tries to allocate 768MB of memory for every core used, so if you run metaWRAP with --threads 48 but only have 24GB of RAM, for example, it would cause this error. How many threads are you using and how much RAM to you have? The other issue here is that one of your read pairs seems to be mismatched, which may or may not be giving you the error. You can use another fastq repair program or just use the metaWRAP's read_qc module, now that it is fixed in metawrap v=0.7.7. The read_qc module should remove any mismatched reads. |
You also asked: This is interesting. Were you able to sort your bam file as well? As of now, it is not possible to provide your own bam file, however you are welcome to hack into the bash code in |
Can I lower the number of threads ? And that way lower the memory needed?
I used Sam tools to build and sort bam files, no problem at all...
Em 02/03/2018 7:04 da tarde, "Gherman V. Uritskiy" <[email protected]>
escreveu:
… You also asked:
"Other question is, is it possible to use a bam file, previously produced
to do the metawrap binning command? I'm trying to do the analyses on a 24
GB computer and it seems to go out of memory, but I was able to produce a
bam file in the same pc using bam..."
This is interesting. Were you able to sort your bam file as well? As of
now, it is not possible to provide your own bam file, however you are
welcome to hack into the bash code in metaWRAP/bin/metawrap-modules/
binning.sh on lines ~170-180. Let me know if you find a more memory
efficient solution.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#14 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AQAOmT_NGKIMih9y2yWrKbwrpBs9COy1ks5taZekgaJpZM4SZP4f>
.
|
Yeah, you could re-run the module with |
Let me know if you find a work-around. Worst-case scenario, you could just run the binning functions yourself, and then proceed to the bin_refinement. Feel free to skim the binning module code for an example how to run each binner. |
I have this error message after the metaWRAP binning command
The text was updated successfully, but these errors were encountered: