Alignment using bwa-mem2
1
0
Entering edit mode
3.3 years ago
priya.bmg ▴ 60

Hello

I need help in aligning the sequence with reference using bwa-mem2. I used the following code:

bwa-mem2 mem -t 8 gch38.fa DE98NGSUKBD117612_1_1.fq DE98NGSUKBD117612_1_2.fq > d3_align.sam 

I got the following error:

ERROR! Unable to open the file: gch38.fa.bwt.2bit.64

There is no gch38.fa.bwt.2bit.64 file. I have the following the reference indexes:

gch38.fa  gch38.fa.0123  gch38.fa.amb  gch38.fa.ann  gch38.fa.pac

What is the gch38.fa.bwt.2bit.64 file?

Thank you

Priya

alignment bwa-mem2 • 8.0k views
ADD COMMENT
0
Entering edit mode

Did you re-make your own indexes? bwa-mem indexes are not compatible with bwa-mem2.

ADD REPLY
0
Entering edit mode

This is the command used to build indexes:

 bwa-mem2 index gch38.fa
ADD REPLY
0
Entering edit mode

If you have no 2bit.64 files then your index was not properly made. It is not enough just to run commands. You should also look at the logs/error files that are generated as a part of the process.

ADD REPLY
0
Entering edit mode

I am using bwa-mem2/2.2.1-foss-2018b to build reference indexes.Is this version has bug?.

ADD REPLY
1
Entering edit mode

Unlikely. Probably you job got killed due to memory (or whatever) shortage.

ADD REPLY
0
Entering edit mode

Yes the job got killed. Thanks. I am running in server and still the process got killed.

ADD REPLY
0
Entering edit mode

How much memory is available?

ADD REPLY
0
Entering edit mode

How much memory is available?

ADD REPLY
0
Entering edit mode

1 TB of memory

ADD REPLY
1
Entering edit mode
3.3 years ago
ATpoint 85k

Should be enough. Be sure that if you are using a job scheduler you actually allocated this memory (in SLURM that would be the --mem argument).

ADD COMMENT
0
Entering edit mode

Thank you, I have specified the memory in slurm script and running it again

ADD REPLY

Login before adding your answer.

Traffic: 2401 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6