Hisat2 exited with value 137
Dear all, I have some rat fastq PE data. When I used hisat2 with --very-sensitive option for alignment, it exited with value 137. I understand that is a memory issue. Does anyone know how to bypass this. I should use '--very-sensitive' parameter. Thanks a lot.
• 941 views
•
link
updated
by
ATpoint
•
written
by
linjc.xmu •
•
written
by
linjc.xmu •
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
hisat2 Error 137
written by Forough •
-
I need help with bowtie2 to map reads different length
written by DByter •
-
hisat2 :Killed (ERR): hisat2-align exited with value 137
written by iamsmor •
-
bowtie2 shell script
written by amitpande74 •
-
Error while using hisat2 (hisat2-align exited with value 137)
written by szabo.marton •
-
Library Types in TopHat and Hisat2
written by Sammy •
-
any idea why hisat2 is usurping all my RAM and threads
written by shripathiacademics •
-
output unmapped file in STAR alignment
written by linjc.xmu •
-
hisat2 run error
written by XBria
-
error in bowtie 2
written by mra8187 •
Get more memory or use a machine with more memory, sorry to be blunt, but that's what it is. You cannot magically create more memory unless you run on a cluster and the reason was that you did not allocate enough memory via the scheduler.