Question: Rainbow assembly- segmentation fault?
gravatar for phair.nikki
3.0 years ago by
phair.nikki0 wrote:

Hello, I am reletively new to bioinformatics and I'm hoping someone will be able to answer my question.

I am trying to use Rainbow to assemble RADseq (short paired-end) reads and eventually call for SNPs. However, I get exit status 139 and the error file says: "/var/spool/PBS/mom_priv/jobs/13307.launch.hpc.SC: line 15: 5705 Segmentation fault rainbow merge -a -i cat.rbdiv.out -o cat.rbasm.out -N 500"

This appears to be a problem with the merging step of rainbow. I get this error with both trimmed and raw reads, but other people are using rainbow on our HPC without any problems so I'm assuming it has something to do with my data...

My script:

module load app/rainbow
rainbow cluster -1 forward -2 reverse > cat.rbcluster.out 2> log
rainbow div -i cat.rbcluster.out -o cat.rbdiv.out
rainbow merge -a -i cat.rbdiv.out -o cat.rbasm.out -N 500

Has anyone seen this error or have any suggestions on how to fix this?

Thanks in advance

next-gen assembly • 1.0k views
ADD COMMENTlink modified 4 weeks ago by chris.bird0 • written 3.0 years ago by phair.nikki0

Looks like you are using PBS scheduler. Are you assigning adequate memory for this job (assuming the command you are using for rainbow are correct)?

ADD REPLYlink written 3.0 years ago by genomax73k

My experience is Torque / PBS would explicit say if memory was insufficient. But why are you looking at /var/spool/PBS/mom_priv? What are the messages from stdout and stderr (which, if memory servers me right, you set with #PBS -o and #PBS -e)?

ADD REPLYlink written 3.0 years ago by h.mon27k

Today, when I was running the Rainbow on the cluster I noticed the similar issue. I have assigned 600 GB memory still it fails ("segmentation fault"). Now I am suspecting whether Rainbow requires few TBs of RAM at "merge" step.

ADD REPLYlink written 23 months ago by bioinfo740
gravatar for chris.bird
4 weeks ago by
chris.bird0 wrote:

This happened to me because my input file was formatted incorrectly.

ADD COMMENTlink written 4 weeks ago by chris.bird0
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1721 users visited in the last hour